PRIVATE APPLICATION CLIPBOARD

• US 20120066691A1
• Filed: 09/14/2010
• Published: 03/15/2012
• Est. Priority Date: 09/14/2010
• Status: Abandoned Application

• Current Assignee: Appsense Incorporated
• Original Assignee: Appsense Incorporated
• Inventors: BRANTON, PAUL KEITH
• Application Number:
  US12/881,819
• Publication Number:
  US 20120066691A1
• Time in Patent Office: Days
• US Class Current: 719/312
• CPC Class Codes: G06F 21/6209 to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: G06F 2221/2149 Restricted operating environment
• CPC Class Codes: G06F 9/543 User-generated data transfer, e.g. clipboards, dynamic data exchange [DDE], object linking and embedding [OLE]

Abstract

In one embodiment, a non-transitory processor-readable medium stores code representing instructions that when executed cause a processor operating in an operating system environment that includes a clipboard function that stores information at a first memory location, to receive, from an application, a first request to store content. The code further represents instructions to store, at a second memory location, a content portion indicated by the first request, and receive, from a trusted application, a second request to retrieve the content portion. The code further represents instructions to send, to the trusted application, the content portion.

Claims

1. A non-transitory processor-readable medium storing code representing instructions that when executed cause a processor operating in an operating system environment that includes a clipboard function that stores information at a first memory location, to:

receive, from an application, a first request to store content;

store, at a second memory location, a content portion indicated by the first request;

receive, from a trusted application, a second request to retrieve the content portion; and

send, to the trusted application, the content portion.

2. The non-transitory processor-readable medium of claim 1, wherein the trusted application is a first trusted application and the application is a second trusted application.

3. The non-transitory processor-readable medium of claim 1, wherein the trusted application is a first instance of the trusted application and the application is a second instance of the trusted application.

4. The non-transitory processor-readable medium of claim 1, wherein the application and the trusted application are the same application.

5. A method, comprising:

receiving, from a trusted application, a request to store a content portion;

determining whether the content portion is deferred;

if the content portion is not deferred;

storing, at a memory location, the content portion; and

providing, to a default content storage function, a restricted data message; and

if the content portion is deferred, providing, to the default content storage function, an indicator that the content portion is deferred.

6. The method of claim 5, wherein the trusted application is a first trusted application, further comprising:

receiving, from a second trusted application, a request for the content portion; and

if the content portion is not deferred;

accessing, from the memory location, the content portion; and

providing the content portion to the second trusted application.

7. The method of claim 5, wherein the content portion includes at least one of:

text content;

graphical content;

audio content;

video content; and

content of a custom type.

8. The method of claim 5, wherein each instance of the trusted application is associated with its own distinct memory location.

9. A method, comprising:

receiving, from a trusted application, a request for an indicated content portion, the request being associated with a first memory location;

if the indicated content portion is deferred;

retrieving, from a predetermined application, the indicated content portion; and

storing, at a second memory location, the indicated content portion;

retrieving, from the second memory location, the indicated content portion;

storing, at the first memory location, the indicated content portion; and

providing, to the trusted application, the indicated content portion.

10. The method of claim 9, further comprising:

storing, after the retrieving from the second memory location, a restricted data message at the second memory location.

11. The method of claim 9, wherein the request is a first request, further comprising:

receiving, from an application, a second request for the indicated content portion; and

providing, to the application, a restricted data message.