Methods for identifying the guarantor of an application

• US 9,071,437 B2
• Filed: 05/21/2013
• Issued: 06/30/2015
• Est. Priority Date: 05/13/2008
• Status: Expired due to Fees

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Veritrix, Inc.
• Inventors: Headley, Paul
• Primary Examiner(s): MOORTHY, ARAVIND K
• Application Number:
  US13/899,382
• Publication Number:
  US 20130254546A1
• Time in Patent Office: 770 Days
• Field of Search: 713/176, 713/155, 713/156, 713/161, 713/168, 726/4
• US Class Current: 1/1
• 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/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0861 using biometrical features, e.g. fingerprint, retina-scan cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 9/32 including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
• CPC Class Codes: H04L 9/3231 Biological data, e.g. fingerprint, voice or retina network architectures or network communication protocols for supporting authentication of entities using biometrical features in a packet data network H04L63/0861
• CPC Class Codes: H04L 9/3247 involving digital signatures

Abstract

Third-party applications for platforms are linked to identified individuals that guarantee the security of the applications. The linkage is achieved by acquiring one or more biometric records of the individual guarantor, storing those records as a signature in a database, assigning a unique identifier to the signature, and embedding that unique identifier in the executable file of the application. The signature of the guarantor can be compared to other stored signatures of other guarantors to check for individuals posing under multiple aliases. The signature of a guarantor linked to a malicious application can be flagged so that a subsequent application guaranteed by the same individual can be disapproved.

Claims

1. A method for providing an application for a platform, the method comprising:

receiving an executable file by a first computing system;

embedding an identifier of a signature of a guarantor into the executable file, the signature of the guarantor comprising at least one biometric record; and

making the executable file available for use.

2. The method of claim 1 wherein the platform comprises a mobile operating system.

3. The method of claim 1 wherein the platform comprises a website.

4. The method of claim 1 further comprising generating the signature of the guarantor.

5. The method of claim 4 wherein generating the signature of the guarantor includes storing a biometric record of the guarantor as one record of the signature.

6. The method of claim 5 wherein generating the signature of the guarantor includes storing a video of the guarantor.

7. The method of claim 5 wherein generating the signature of the guarantor includes storing a digital representation of a nucleic acid sequence derived from the guarantor.

8. The method of claim 1 further comprising approving the executable file.

9. The method of claim 8 wherein approving the executable file includes comparing a record of the signature of the guarantor against previously stored records of signatures.

10. The method of claim 1 further comprising signing the executable file without using the signature.

11. The method of claim 1 wherein making the executable file available includes posting the executable file for downloading.

12. The method of claim 1 wherein making the executable file available includes posting the executable file for use as a service.

13. The method of claim 1 further comprising determining the identifier before embedding the identifier, wherein determining the identifier consists of assigning a numeric or alphanumeric string to be the identifier, where the numeric or alphanumeric string is not derived from biometric information.

14. A method comprising:

receiving an executable file by a first computing system;

generating a signature of a guarantor of the executable file by storing a biometric record as at least one record of the signature of the guarantor; and

matching a record of the signature to a record of another signature stored in a database.

15. The method of claim 14 wherein generating the signature of the guarantor includes storing a video of the guarantor.

16. The method of claim 14 wherein generating the signature of the guarantor includes storing a digital representation of a nucleic acid sequence derived from the guarantor.

17. The method of claim 14 wherein the executable file comprises an application image.

18. The method of claim 14 wherein the record that is matched comprises the biometric record.