Efficient storage and transfer of iOS binary files

• US 9,959,100 B2
• Filed: 12/28/2015
• Issued: 05/01/2018
• Est. Priority Date: 08/12/2015
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Straub, Christian David
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Franco, Christopher J
• Application Number:
  US14/979,828
• Publication Number:
  US 20170046134A1
• Time in Patent Office: 855 Days
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/31 Programming languages or programming paradigms
• CPC Class Codes: G06F 8/34 Graphical or visual programming
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements
• CPC Class Codes: H04L 67/00 Network arrangements or protocols for supporting network services or applications user-to-user messaging H04L51/00; network arrangements, protocols or services for supporting real-time applications in data packet communications networks H04L65/00
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A system builds an application. The system receives, by a build server, from an application development server, metadata information of the application and a build request to build the application. The system generates binaries of the application by overlaying the metadata information on binaries of a pre-compiled application. The system then signs the binaries of the application to generate signed binaries of the application, and sends, to the application development server, a corresponding signature and one or more files modified by the signing of the binaries of the application. In one embodiment, the build server stores, on a storage appliance, the corresponding signature, the one or more files modified by the signing of the binaries of the application, and the metadata information of the application.

Claims

1. A method for building an application, the method comprising:

receiving, by a build server, from an application development server, declarative metadata information of the application and a build request to build the application;

generating binaries of the application by overlaying the declarative metadata information on unsigned binaries of a pre-compiled application, the overlaying comprising adding or substituting the declarative metadata information as deltas in the unsigned binaries;

signing the unsigned binaries of the application to generate signed binaries of the application and one or more modified files; and

sending, to the application development server, a corresponding signature and the one or more files modified by the signing of the unsigned binaries of the application;

wherein the build server stores on a storage appliance, to be obtained by an edge server in response to a request from a mobile device to download the application, the corresponding signature, the one or more files modified by the signing of the unsigned binaries of the application, and the declarative metadata information;

wherein the corresponding signature is compared to a resulting signature based on the signed binaries to verify the authenticity of the application.

2. The method of claim 1, wherein the build server, the application server and the edge server are different servers.

3. The method of claim 1, wherein the edge server obtains the corresponding signature, the one or more files modified by the signing of the application, and the metadata information of the application, after receiving a request from a mobile device to download the application.

4. The method of claim 3, wherein the edge server regenerates the signed binaries of the application by combining the one or more files modified by the signing of the application, the metadata information of the application, and the binaries of the pre-compiled application.

5. The method of claim 4, wherein the edge server verifies authenticity of the application by hashing the signed binaries of the application and comparing a resulting signature with the corresponding signature.

6. The method of claim 4, wherein the edge server provides the signed binaries of the application to the mobile device that requested to download the application.

7. The method of claim 6, wherein the mobile device verifies authenticity of the application by hashing the signed binaries of the application and comparing a resulting signature with the corresponding signature.

8. A non-transitory computer readable medium having instructions stored thereon that, when executed by a processor, cause the processor to build an application, the building comprising:

receiving, by a build server, from an application development server, declarative metadata information of the application and a build request to build the application;

generating binaries of the application by overlaying the declarative metadata information on unsigned binaries of a pre-compiled application, the overlaying comprising adding or substituting the declarative metadata information as deltas in the unsigned binaries;

signing the unsigned binaries of the application to generate signed binaries of the application and one or more modified files; and

sending, to the application development server, a corresponding signature and the one or more files modified by the signing of the unsigned binaries of the application;

wherein the build server stores on a storage appliance, to be obtained by an edge server in response to a request from a mobile device to download the application, the corresponding signature, the one or more files modified by the signing of the unsigned binaries of the application, and the declarative metadata information;

wherein the corresponding signature is compared to a resulting signature based on the signed binaries to verify the authenticity of the application.

9. The computer readable medium of claim 8, wherein the build server, the application development server and the edge server are different servers.

10. The computer readable medium of claim 8, wherein the edge server regenerates the signed binaries of the application by combining the one or more files modified by the signing of the application, the metadata information of the application, and the binaries of the pre-compiled application.

11. The computer readable medium of claim 10, wherein the edge server verifies authenticity of the application by hashing the signed binaries of the application and comparing a resulting signature with the corresponding signature.

12. The computer readable medium of claim 10, wherein the edge server provides the signed binaries of the application to the mobile device that requested to download the application.

13. The computer readable medium of claim 12, wherein the mobile device verifies authenticity of the application by hashing the signed binaries of the application and comparing a resulting signature with the corresponding signature.

14. The computer readable medium of claim 8, wherein the binaries of the pre-compiled application are unsigned binaries generated by Xcode.

15. A system for building an application, the system comprising:

a processor coupled to a storage device that stores instructions that, when executed by the processor, implement modules comprising;

a receiving module that receives, by a build server, from an application development server, declarative metadata information of the application and a build request to build the application;

a generating module that generates binaries of the application by overlaying the declarative metadata information on unsigned binaries of a pre-compiled application, the overlaying comprising adding or substituting the declarative metadata information as deltas in the unsigned binaries;

a signing module that signs the unsigned binaries of the application to generate signed binaries of the application and one or more modified files; and

a sending module that sends, to the application development server, a corresponding signature and the one or more files modified by the signing of the unsigned binaries of the application;

wherein the build server stores on a storage appliance, to be obtained by an edge server in response to a request from a mobile device to download the application, the corresponding signature, the one or more files modified by the signing of the unsigned binaries of the application, and the declarative metadata information;

wherein the corresponding signature is compared to a resulting signature based on the signed binaries to verify the authenticity of the application.

16. The system of claim 15, wherein the build server, the application server and the edge server are different servers.

17. The system of claim 15, wherein the edge server regenerates the signed binaries of the application by combining the one or more files modified by the signing of the application, the metadata information of the application, and the binaries of the pre-compiled application.

18. The system of claim 17, wherein the edge server verifies authenticity of the application by hashing the signed binaries of the application and comparing a resulting signature with the corresponding signature.

19. The system of claim 17, wherein the edge server provides the signed binaries of the application to the mobile device that requested to download the application.

20. The system of claim 19, wherein the mobile device verifies authenticity of the application by hashing the signed binaries of the application and comparing a resulting signature with the corresponding signature.