Computer systems intercommunicate via computer networks. For example, a first computer system frequently communicates with a second computer system over a computer network to obtain information. The computer network may include many different communication media. In one example, the computer network is an Ethernet local area network (“LAN”). In another example, the computer network is a wireless LAN. Information stored on the first computer system is often sensitive such that access to the information must be restricted. Accordingly, the first computer system often requires that the second computer system be authenticated before allowing the second computer system to access the information. Access to the computer network may also be restricted, requiring any computer system wishing to join the computer network to be authenticated before communicating with other devices on the network.
Authentication typically utilizes an identification protocol that requires a computer system to identify itself with authority to access a restricted computer system. In one example, a first computer system may require a “password” from the second computer system to enable authentication. However, in situations where the communication between the first and second computer systems is monitored by a third computer system, the password may be obtained by the third computer system, allowing unauthorized access by the third computer system to the first computer system. Identification protocols that provide authentication without transmission of a secret password, known as a ‘key’, are therefore utilized. A zero-knowledge identification protocol (“ZKIP”) is one example of a protocol that provides authentication without transmitting the key, thereby preventing the key from being stolen and misused.
Typically, in a computer network that uses authentication, there is only one authenticator that stores keys used to authenticate requests from other computer systems. The use of a single authenticator, however, may result in access problems when the computer system running the authenticator fails, or where communications to the authenticator fail, for example. Where the authentication is for important data or services, failure of the authenticator may prevent access to the data or services. Further, the use of a single authenticator also causes congestion within the computer network as all authentication traffic is directed to a single location.
Where a computer network is highly scalable and dynamic it is important to authenticate each computer system as it attempts to access the computer network. A digital mobile telephone network is one example of a dynamic computer network. The digital mobile telephone network consists of multiple base stations that are networked together, each base station providing one or more cells for the digital telephone network. Each mobile telephone handset connects to, and disconnects from, these cells as the handset changes location. It is therefore important that any authentication process used within the cell network be as fast and efficient as possible. Typically, to meet speed requirements for a digital mobile telephone network, the authentication process is simplified, thereby making it less reliable and less secure, making the mobile telephone network highly susceptible to snooping by third parties.
U.S. Pat. No. 4,748,668, titled Method, Apparatus and Article for Identification and Signature, is incorporated herein by reference.
In one aspect, a method provides non-centralized zero knowledge authentication within a dynamic computer network. The dynamic computer network includes two or more authentication agents that interact with prover agents within computers wishing to gain access to the computer network. Using a zero-knowledge authentication protocol, the prover is either authenticated, or not, without communication of a secret.
In another aspect, a software product (firmware, for example) is distributed with a hardware device to provide non-centralized zero-knowledge authentication. In one example, the hardware device is a router connected to a network. The router communicates with a prover agent within a mobile computer (e.g., a laptop computer system or a mobile telephone handset) that seeks access to the network. Once the prover agent is authenticated and authorized, the router permits the mobile computer to access part of or the entire network.
In one aspect, methods are provided for authentication of identity or group membership. One such method involves zero-knowledge authentication. An authentication dialog between a verifying agent (“verifier”) and an agent to be verified (“prover”) is conducted without revealing information about a secret (“secret”) that is used to prove identity (or group membership without actually disclosing prover's identity). Authentication is achieved when verifier asks prover I-times (I>0) to perform an action that can only be reliably performed by an entity that knows a secret. Prover answers verifier with results of action. If prover does not answer correctly, authentication is invalid. This challenge-response-validation iteration is repeated I-times to establish a sufficient level of probability that prover answered with knowledge of secret. One advantage of zero-knowledge authentication is inability for an eavesdropper to learn secret and steal means to prove identity to verifier. Another advantage is inability for verifier to later masquerade as a prover to a third-party.
In another aspect, methods are provided to allow for greater probability of correctly authenticating prover with fewer challenge-response-validation iterations. One such method allows prover to have a set, greater than two, of possible answers, as is provided by Fiat-Shamir protocol. For example, a prover that answers verifier correctly with a member of set {0, 1, 2, 3} has a 25% chance of being incorrectly authenticated with one challenge-response-validation iteration. Following Fiat-Shamir protocol, prover will answer verifier with one of two possible answers {0, 1} and thereby require two challenge-response-validation iterations to achieve the same level of authentication probability.
In another aspect, an authenticator agent require a prover agent to repeat an authentication protocol until a specified confidence level that a prover agent is correctly authenticated has been satisfied. For example, a confidence level of 99% may require 10 iterations, where a confidence level of 99.9999% may require 20 iterations.
In another aspect, a method of protecting a host from unauthorized client access over a network includes the steps of: creating a prover agent application on the client; creating a verifier agent application on the host; and creating a trusted source application to generate and publish encrypted values of a secret and product of first and second large prime numbers. The encrypted values are read for the secret and product, by the provider and verifier from the trusted source. The secret is decrypted, by the prover and verifier, and the product is decrypted, by the prover and verifier. A plurality of verification dialog is performed between the prover and verifier, wherein the prover demonstrates knowledge of the secret and product without exposing the values of the secret and product. The client is denied access when the prover fails to demonstrate knowledge of the secret and product, and granted access when the client succeeds in demonstrating knowledge of the secret and product.
In another aspect, methods are provided to validate agents without unique indicia. One such method allows agents to validate based on indicia that they are within a category of agents who have knowledge of secret common to all authentic agents. An advantage of using non-unique indicia is elimination of overhead required to generate, maintain, and validate unique indicia
In another aspect, methods are provided to publish secret used to authenticate agents. One such method allows a trusted source to periodically update and publish the secret and product of two large prime numbers (“product”). The frequency of updates is less than the predicted length of time a malicious party could factor product or guess secret. Trusted source generates, encrypts, and publishes secret and product. Prover and verifier read encrypted values for secret and product, from trusted source, and use previous values of secret and product to decrypt new values for secret and product. Prover and verifier now have all information required to perform authentication processes.
One advantage of using methods described above is elimination of steps required to derive keys to encrypt and decrypt messages.
Values for s″ and n″ may become compromised by a malicious party that is able to factor or guess values. Therefore, the delay in step 28 terminates before values are likely to be compromised and process 10 is restarted at step 20 where a new s′ is generated.
At this point, prover and verifier agents have data required to perform authentication. Because values for s″ and n″ published by trusted source periodically change, updated values for s″ and n″ will be retrieved. Step 42 is a delay based on a specific length of time or may be triggered at the start of an authentication process (e.g., a zero-knowledge identification protocol). After the delay in step 42, method 30 continues with step 36 and the agent will again contact the trusted source and read new values for s″ and n″.
In step 82, process 50 continues with processing appropriate for authenticated process 48 (prover) and process 50 terminates. In step 76, process 50 (verifier) continues processing as appropriate for non-authentic agents, and process 50 terminates.
Zero-knowledge identification protocol 46,
LAN 504 is shown connected to a wireless LAN device 512 that provides wireless connectivity to mobile computers 514 and 516. LAN 504 also illustratively connects to computer system 518 that includes authentication agent 520 (verifier). Before mobile computer 514 connects to LAN 504, it is first authenticated using zero-knowledge identification protocol 46 as shown in
Trusted source 106,
Computer system 530 illustratively connects to LAN 502 and includes authentication agent 532 (prover). Computer systems 534 and 536 also connect to LAN 502; computer system 534 includes a prover agent 538 and computer system 536 includes a prover agent 540. Prover agent 538 interacts with authentication agent 532 to authenticate computer system 534 for access to LAN 502. Similarly, prover agent 540 interacts with authentication agent 532 to authenticate computer system 536 for access to LAN 502.
Authentication agents 520 and 532 operate independently to authenticate mobile computers 514, 516 and desktop computers 534, 536 for access to LANs 504 and 502, respectively. Optionally, once a computer (e.g., computers 534, 536 and mobile computers 514 and 516) is authenticated and remains connected within system 500, it may operate to authenticate other computers (i.e., may operate as an authentication agent). Further, once authenticated and connected within system 500, the computer may operate to interact with other computers seeking authentication, enabling communication between the other computers and an authentication agent.
For example, and with reference to
In one example, a computer network includes multiple base stations that operate to provide a mobile telephone network. Each base station contains an authentication agent. Each mobile handset includes a prover agent that connects to the mobile telephone network. Before the mobile handset is allowed to use any services of the mobile telephone network, the authentication agent in the base station selected by the mobile handset interacts with the prover agent in the mobile handset. If the authentication agent is satisfied that the prover knows the secret, it becomes authenticated and authorized to use the mobile telephone network. By using a ZKIP, the secret is never transmitted to or from the mobile handset, and therefore not susceptible to malicious snooping.
This application claims priority to U.S. application No. 60/418,889, filed Oct. 16, 2002, which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4748668 | Shamir et al. | May 1988 | A |
4926479 | Goldwasser et al. | May 1990 | A |
4956863 | Goss | Sep 1990 | A |
4969189 | Ohta et al. | Nov 1990 | A |
5136642 | Kawamura et al. | Aug 1992 | A |
5140634 | Guillou et al. | Aug 1992 | A |
5146500 | Maurer | Sep 1992 | A |
5245657 | Sakurai | Sep 1993 | A |
5581615 | Stern | Dec 1996 | A |
5600725 | Rueppel et al. | Feb 1997 | A |
5606617 | Brands | Feb 1997 | A |
5666419 | Yamamoto et al. | Sep 1997 | A |
5987138 | Gilbert et al. | Nov 1999 | A |
6011848 | Kanda et al. | Jan 2000 | A |
6044463 | Kanda et al. | Mar 2000 | A |
6069647 | Sullivan et al. | May 2000 | A |
6076163 | Hoffstein et al. | Jun 2000 | A |
6122742 | Young et al. | Sep 2000 | A |
6154841 | Oishi | Nov 2000 | A |
6189098 | Kaliski, Jr. | Feb 2001 | B1 |
6263446 | Kausik et al. | Jul 2001 | B1 |
6282295 | Young et al. | Aug 2001 | B1 |
6298441 | Handelman et al. | Oct 2001 | B1 |
6327659 | Boroditsky et al. | Dec 2001 | B2 |
6389136 | Young et al. | May 2002 | B1 |
6389536 | Nakatsuyama | May 2002 | B1 |
6411715 | Liskov et al. | Jun 2002 | B1 |
6567916 | Terao et al. | May 2003 | B1 |
6651167 | Terao et al. | Nov 2003 | B1 |
6889322 | Levy | May 2005 | B1 |
6937728 | Abe et al. | Aug 2005 | B1 |
6950948 | Neff | Sep 2005 | B2 |
6952476 | Mao | Oct 2005 | B1 |
6978372 | Jakobsson | Dec 2005 | B1 |
7003541 | Furukawa et al. | Feb 2006 | B2 |
7007301 | Crosbie et al. | Feb 2006 | B2 |
7028338 | Norris et al. | Apr 2006 | B1 |
7031470 | Bar-On | Apr 2006 | B1 |
7047408 | Boyko et al. | May 2006 | B1 |
7058808 | Zolotorev et al. | Jun 2006 | B1 |
7058968 | Rowland et al. | Jun 2006 | B2 |
7062490 | Adya et al. | Jun 2006 | B2 |
7085936 | Moran | Aug 2006 | B1 |
7089323 | Theimer et al. | Aug 2006 | B2 |
7096499 | Munson | Aug 2006 | B2 |
7165181 | Brickell | Jan 2007 | B2 |
7181768 | Ghosh et al. | Feb 2007 | B1 |
7184547 | Girault et al. | Feb 2007 | B1 |
7219239 | Njemanze et al. | May 2007 | B1 |
7222362 | Canetti et al. | May 2007 | B1 |
7260716 | Srivastava | Aug 2007 | B1 |
7305705 | Shelest et al. | Dec 2007 | B2 |
7308097 | Hoffstein et al. | Dec 2007 | B2 |
7313701 | Frankel et al. | Dec 2007 | B2 |
7370358 | Ghanea-Hercock | May 2008 | B2 |
7373499 | MacKenzie et al. | May 2008 | B2 |
7415614 | Guillou | Aug 2008 | B2 |
7543139 | Camenisch et al. | Jun 2009 | B2 |
7747857 | Ramzan et al. | Jun 2010 | B2 |
20010034837 | Kausik et al. | Oct 2001 | A1 |
20010038696 | Frankel et al. | Nov 2001 | A1 |
20010042049 | Zucker et al. | Nov 2001 | A1 |
20010044895 | Hada | Nov 2001 | A1 |
20020007457 | Neff | Jan 2002 | A1 |
20020136401 | Hoffstein et al. | Sep 2002 | A1 |
20020188605 | Adya et al. | Dec 2002 | A1 |
20030065692 | Furukawa et al. | Apr 2003 | A1 |
20030115464 | Nyang et al. | Jun 2003 | A1 |
20030120929 | Hoffstein et al. | Jun 2003 | A1 |
20030158960 | Engberg | Aug 2003 | A1 |
20030172284 | Kittler | Sep 2003 | A1 |
20030177352 | Camenisch et al. | Sep 2003 | A1 |
20030182559 | Curry et al. | Sep 2003 | A1 |
20030196106 | Erfani et al. | Oct 2003 | A1 |
20040006650 | Theimer et al. | Jan 2004 | A1 |
20040008845 | Le et al. | Jan 2004 | A1 |
20040015719 | Lee et al. | Jan 2004 | A1 |
20040028221 | Seysen | Feb 2004 | A1 |
20040054885 | Bartram et al. | Mar 2004 | A1 |
20040103281 | Brickell | May 2004 | A1 |
20040123141 | Yadav | Jun 2004 | A1 |
20040133781 | Guillou | Jul 2004 | A1 |
20040177252 | Vallee et al. | Sep 2004 | A1 |
20050069135 | Brickell | Mar 2005 | A1 |
20050265550 | Tuyls et al. | Dec 2005 | A1 |
20070113077 | Brickell | May 2007 | A1 |
Number | Date | Country | |
---|---|---|---|
20040123156 A1 | Jun 2004 | US |
Number | Date | Country | |
---|---|---|---|
60418889 | Oct 2002 | US |