Dynamic executable

• US 20060265446A1
• Filed: 04/14/2005
• Published: 11/23/2006
• Est. Priority Date: 04/14/2004
• Status: Active Grant

• Current Assignee: Channel IP BV
• Original Assignee: Ipass Incorporated (Pareteum Corp.)
• Inventors: Elgressy, Moshe, Bob, Kenneth
• Granted Patent: US 7,836,121 B2
• Time in Patent Office: Days
• US Class Current: 709/200
• CPC Class Codes: G06F 21/445 by mutual authentication, e.g. between devices or programs

Abstract

A system to identify and/or authenticate an entity includes a. client-side executable and an associated server-side executable, each of which may be dynamically generated. The server-side executable may be executed on a server to generate a first result. The client-side executable may be executed on an entity to generate a second result. The first result and the second result are compared to identify and/or to authenticate the entity.

Claims

1. A system comprising:

a server-side executable to execute on a server to generate a first result;

a client-side executable to execute on an entity to generate a second result, the client-side executable being associated with the server-side executable, and to execute a subset of instructions from the server; and

an authenticator to compare the first result and the second result to verify an identity of the entity.

2. The system of claim 1 wherein the server includes the authenticator.

3. The system of claim 1 wherein the server and the authenticator are separate.

4. The system of claim 1 further comprising a server-side database accessible by the server-side executable, wherein the server-side database includes entity information used by the server-side executable in generating the first result.

5. The system of claim 4 wherein the server-side executable is to collect the entity information from the database.

6. The system of claim 5 wherein the server-side executable is to process the collected entity information from the database to generate the first result.

7. The system of claim 1 wherein the client-side executable is to collect entity information.

8. The system of claim 7 wherein the collected information is selected from a group including hardware-related information and software-related information associated with the entity.

9. The system of claim 7 wherein the second result includes a fixed-length value generated from the collected information.

10. The system of claim 7 wherein the client-side executable is to process the collected entity information to generate the second result.

11. The system of claim 1 wherein the authenticator includes a time limit expiration to render the entity as not identified if the second result is not received by the authenticator during a limited time frame.

12. The system of claim 1 wherein the client side executable includes one-way function executable software.

13. The system of claim 1 wherein the client-side executable includes at least one dynamically generated instruction.

14. The system of claim 1 wherein the server-side executable includes at least one dynamically generated instruction.

15. The system of claim 1 wherein the client-side executable includes at least one previously generated instruction and the server-side executable includes at least one previously generated instruction.

16. The system of claim 15 wherein the at least one previously generated instruction includes a dynamic selection from a plurality of previously generated instructions on the server.

17. The system of claim 1 wherein the entity includes a device, wherein the device has an associated authentication score to be added towards a threshold level.

18. The system of claim 17 wherein the authentication score is higher for associated devices that are less likely to be exchanged or adjusted.

19. The system of claim 1 wherein the entity includes a plurality of components, each component having a level of identification strength.

20. A method comprising:

dynamically generating a client-side executable and a corresponding server-side executable;

executing the server-side executable on a server to generate a first result;

executing the client-side executable on an entity to generate a second result; and

comparing the first result and the second result to verify an identity of the entity.

21. The method of claim 20 further comprising collecting information, selected from a group including a dynamic information type of the entity, a dynamic information order of the entity and a dynamic amount of information of the entity, for the client-side executable.

22. The method of claim 20 further comprising collecting information in the entity by the client-side executable;

and generating a fixed-length value from the information collected.

23. The method of claim 20 further comprising collecting information about the entity by the client-side executable;

and processing the information collected to generate the second result, wherein the client-side executable includes at least one dynamic encryption instruction.

24. The method of claim 20 further comprising collecting information about the entity by the client-side executable and obfuscating the information collected.

25. The method of claim 20 further comprising collecting, from a server database, entity information for the server-side executable.

26. The method of claim 20 wherein the server includes an authenticator to compare the first result and the second result.

27. The method of claim 26 further comprising imposing a time limit on receipt of the second result by the authenticator, wherein upon expiration of the time limit, the entity is considered as not authenticated.

28. The method of claim 20 further comprising generating a plurality of instructions on the server;

and dynamically selecting a subset of the plurality of instructions as the client-side executable.

29. The method of claim 20 wherein the client-side executable and the server-side executable each include a dynamic sending instruction to send the first result and the second result, respectively.

30. The method of claim 20 wherein the entity includes a plurality of components, each component having a level of identification strength.

31. The method of claim 20 wherein the entity includes a device, wherein the device has an associated authentication score to be added towards a threshold level.

32. The method of claim 31 wherein the authentication score is higher for associated devices that are less likely to be exchanged or adjusted.

33. The method of claim 31 further comprising:

collecting information from a server database, wherein the information collected includes a corresponding image of the device; and

adding the authentication score towards a threshold level to verify the entity.

34. The method of claim 33 further comprising:

updating a hardware signature used to validate the entity to include a signature associated with a new component to the entity, when the threshold level is met.

35. The method of claim 33 further comprising refusing access to the entity when the threshold level is not met.

36. The method of claim 33 further comprising denying authentication to the entity upon detection of an unauthorized device or of unauthorized software.

37. A machine-readable medium storing a sequence of instructions that, when executed by a computer, cause the computer to perform the method of claim 20.

38. A system comprising:

means for dynamically generating a client-side executable and a corresponding server-side executable;

means for executing the server-side executable on a server to generate a first result and for executing the client-side executable on an entity to generate a second result; and

means for comparing the first result and the second result to verify an identity of the entity.