APPLICATION WRAPPING FOR APPLICATION MANAGEMENT FRAMEWORK

• US 20140109072A1
• Filed: 10/16/2013
• Published: 04/17/2014
• Est. Priority Date: 10/16/2012
• Status: Active Application

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Inventors: Lang, Zhongmin, Barton, Gary, Walker, James Robert, Aravindakshan, Vipin
• Application Number:
  US14/055,038
• Publication Number:
  US 20140109072A1
• Time in Patent Office: Days
• US Class Current: 717/168
• CPC Class Codes: G06F 21/33 using certificates
• CPC Class Codes: G06F 21/53 by executing in a restricted environment, e.g. sandbox or secure virtual machine
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: G06F 8/52 Binary to binary
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/72 Code refactoring
• CPC Class Codes: G06F 8/76 Adapting program code to run in a different environment; Porting
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
• CPC Class Codes: G06F 9/45516 Runtime code conversion or optimisation

Abstract

A stub for a proxy of an operating system (OS) application program interface (API) call may be generated. Policy enforcement logic may be inserted into the stub for the proxy of the OS API call. Code of an application may be parsed to identify one or more calls corresponding to the OS API call. The one or more calls corresponding to the OS API call may be replaced with a reference to the stub for the proxy of the OS API call.

Claims

1. A method, comprising:

generating, by at least one processor of a computing platform, a stub for a proxy of an operating system (OS) application program interface (API) call;

inserting, by the at least one processor, policy enforcement logic into the stub for the proxy of the OS API call;

parsing, by the at least one processor, code of an application to identify one or more calls corresponding to the OS API call; and

replacing, by the at least one processor, the one or more calls corresponding to the OS API call with a reference to the stub for the proxy of the OS API call.

2. The method of claim 1, wherein the OS API call comprises a call to a method of the OS API, wherein the proxy for the OS API call comprises a call corresponding to the method of the OS API, and wherein the policy enforcement logic comprises one or more conditions for determining whether the call corresponding to the method of the OS API should be invoked.

3. The method of claim 2, wherein the stub for the proxy of the OS API call comprises a return type corresponding to a return type of the OS API call and one or more parameters corresponding to parameters of the OS API call, the method comprising:

invoking, by the application, the reference to the stub for the proxy of the OS API call, wherein invoking the reference to the stub for the proxy of the OS API call includes receiving, from the application, a value for each of the one or more parameters corresponding to parameters of the OS API call; and

executing, by a device running the OS and the application, the policy enforcement logic to determine whether the call corresponding to the method of the OS API should be invoked.

4. The method of claim 3, comprising:

responsive to determining that the call corresponding to the method of the OS API should be invoked, invoking the call corresponding to the method of the OS API, wherein invoking the call corresponding to the method of the OS API includes;

passing, to the method of the OS API, the value for each of the one or more parameters corresponding to parameters of the OS API call; and

receiving, from the method of the OS API, a value of the return type of the OS API call; and

returning, by the proxy of the OS API call and to the application, the value of the return type of the OS API call.

5. The method of claim 3, comprising:

responsive to determining that the call corresponding to the method of the OS API should not be invoked;

failing to invoke the call corresponding to the method of the OS API;

failing to pass, to the method of the OS API, the value for each of the one or more parameters corresponding to parameters of the OS API call; and

returning, by the proxy of the OS API call and to the application, a predetermined value of the return type of the OS API call.

6. The method of claim 1, wherein the OS API call comprises a call to a class of the OS API, and wherein the proxy for the OS API call comprises a call to a class that extends the class of the OS API.

7. The method of claim 6, comprising:

invoking, by the application, the reference to the stub for the proxy of the OS API call; and

instantiating an instance of the class that extends the class of the OS API, wherein the class that extends the OS API comprises an instance of the class of the OS API and the policy enforcement logic.

8. The method of claim 7, wherein the policy enforcement logic comprises one or more conditions for determining whether a call to a method of the instance of the class of the OS API should be invoked, the method comprising executing, by a device running the OS and the application, the policy enforcement logic to determine whether the call to the method of the instance of the class of the OS API should be invoked.

9. The method of claim 8, comprising responsive to determining that the call to the method of the instance of the class of the OS API should be invoked, invoking the method of the instance of the class of the OS API.

10. The method of claim 8, comprising responsive to determining that the call to the method of the instance of the class of the OS API should not be invoked, failing to invoke the method of the instance of the class of the OS API.

11. The method of claim 1, comprising merging at least a portion of the code of the application and code comprising the policy enforcement logic into a common file.

12. The method of claim 1, wherein parsing the code of the application to identify the one or more calls corresponding to the OS API call comprises parsing bytecode of the application to identify one or more portions of the bytecode of the application that correspond to the OS API call.

13. The method of claim 12, wherein the bytecode of the application is configured for execution by a process virtual machine run on the OS.

14. The method of claim 1, wherein the policy enforcement logic comprises one or more calls to a policy enforcement class comprising one or more methods for determining whether a call by the application to the OS API should be invoked.

15. The method of claim 14, wherein the one or more methods for determining whether the call by the application to the OS API should be invoked include at least one method for determining whether a call by the application to the OS API for cutting, copying, or pasting data to or from a clipboard of the OS should be invoked.

16. The method of claim 14, wherein the one or more methods for determining whether the call by the application to the OS API should be invoked include at least one method for determining whether a call by the application to the OS API for browsing to a specified uniform resource locator (URL) should be invoked.

17. The method of claim 14, wherein the one or more methods for determining whether the call by the application to the OS API should be invoked include at least one method for determining whether a call by the application to the OS API for geographical location information accessible to the OS, camera data accessible to the OS, or microphone data accessible to the OS should be invoked.

18. The method of claim 14, wherein the one or more methods for determining whether the call by the application to the OS API should be invoked include at least one method for determining whether a call by the application to the OS API for composing an email message or a short messaging service (SMS) message should be invoked.

19. A system, comprising:

at least one processor; and

a memory storing instructions that, when executed by the at least one processor, cause the system to;

generate a stub for a proxy of an operating system (OS) application program interface (API) call;

insert policy enforcement logic into the stub for the proxy of the OS API call;

parse code of an application to identify one or more calls corresponding to the OS API call; and

replace the one or more calls corresponding to the OS API call with a reference to the stub for the proxy of the OS API call.

20. One or more non-transitory computer-readable media having instructions stored thereon, that when executed by one or more computers, cause the one or more computers to:

generate a stub for a proxy of an operating system (OS) application program interface (API) call;

insert policy enforcement logic into the stub for the proxy of the OS API call;

parse code of an application to identify one or more calls corresponding to the OS API call; and

replace the one or more calls corresponding to the OS API call with a reference to the stub for the proxy of the OS API call.