WO2004034213A2

WO2004034213A2 - Localized network authentication and security using tamper-resistant keys

Info

Publication number: WO2004034213A2
Application number: PCT/US2003/031930
Authority: WO
Inventors: Anthony C. Fascenda
Original assignee: Koolspan
Priority date: 2002-10-08
Filing date: 2003-10-08
Publication date: 2004-04-22
Also published as: AU2003282497A8; WO2004034214A2; AU2003277308A8; WO2004034213A3; US20040068653A1; AU2003277308A1; WO2004034214A3; WO2004034205A3; AU2003282497A1; AU2003282495A1; WO2004034205A2; AU2003282495A8; US7607015B2

Abstract

The invention provides a secure Wi-Fi communications method and system (1100). In an embodiment of the invention, unique physical keys, or tokens, are installed at an access point and each client device of the network. Each key comprises a unique serial number and a common network send cryptographic key and a common network receive cryptographic key used only during the authentication phase by all components on the LAN (1100). Each client key further includes a secret cryptographic key unique to each client device (1115). During authentication, two random numbers are generated per communications session and are known by both sides of the wireless channel.

Description

LOCALIZED NETWORK AUTHENTICATION AND SECURITY USING TAMPER-RESISTANT KEYS

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] TJhis present application claims priority to United States Provisional

Patent Application No. 60/416,583 filed on October 8, 2002; United States

Provisional Patent Application No. 60/422,474 filed October 31, 2002; and United

States Provisional Patent Application No. 60/447,921 filed June 13, 2003. The contents of these three provisionals are incorporated herein by reference in their entirety.

BACKGROUND OF THE INVENTION

1. Field of Invention

[0002] The present invention relates to wireless networking, and more particularly, to an authentication and secure communication system for a Wi-Fi (IEEE 802.11) network.

2. Description of Related Art

[0003] A Wireless Local Area Network (WLAN) is generally implemented to provide local connectivity between a wired network and a mobile computing device. In a typical wireless network, all of the computing devices within the network broadcast their information to one another using radio frequency (JRF) communications. WLANs are based on the Institute of Electrical and Electronic Engineers (JEEEE) 802.11 standard, which designates a wireless-Ethernet specification using a variety of modulation techniques at frequencies generally in the 2.4 gigahertz (GHz) and 5 GHz license-free frequency bands. [0004] The IEEE 802.11 standard ("Wi-Fi"), the disclosure of which is incorporated herein in its entirety by reference, enables wireless communications with throughput rates up to 54 JMbps. Wi-Fi (for "wireless fidelity") is essentially a seal of approval certifying that a manufacturer's product is compliant with IEEE 802.11. For example, equipment carrying the "Wi-Fi" logo is certified to be interoperable with other Wi-Fi certified equipment. There are Wi-Fi compatible PC cards that operate in peer-to-peer mode, but Wi-Fi usually incorporates at least one access point, or edge device. Most access points have an integrated Ethernet controller to connect to an existing wired-Ethernet network. A Wi-Fi wireless transceiver connects users via the access point to the rest of the LAN. The majority of Wi-Fi wireless transceivers available are in Personal Computer Memory Card International Association (PCMCIA) card form, particularly for laptop, palmtop, and other portable computers, however Wi-Fi transceivers can be implemented through an Industry Standard Architecture (ISA) slot or Peripheral Component Interconnect (PCI) slot in a desktop computer, a Universal Serial Bus (USB), or can be fully integrated within a handheld device.

[0005] Fig. 1 illustrates a typical conventional Wi-Fi network 100.

Particularly, Wi-Fi network 100 comprises a number (N) of computing devices 110A-N and an access point 120. Each computing device 110 comprises a Wi-Fi transceiver (not shown) such as a Wi-Fi enabled network interface card (NIC) to communicate with the access point via an JRF communications link 115. The access point 120 comprises a Wi-Fi transceiver (not shown) to communicate with a wired network via an JRF communications link 125.

[0006] Authentication and security features offered by Wi-Fi products to date have been implemented via Wired Equivalency Protocol (WEP). With WEP enabled, an access point will not admit anyone onto the LAN without the proper WEP settings. The WEP settings are used primarily for wireless security, but they also form the basis for authentication in that without these settings known to and used by the user, the user cannot connect through the access point. WEP comes in 40-bit or 128-bit forms. The 40-bit version is actually a 40-bit key plus a 24 bit Initialization Vector ("IV"), whereas the 128-bit version is really a 104-bit plus the 24-bit IV. WEP utilizes a RC4 stream cipher. This stream cipher works by using the WEP key and the JJTV to seed a pseudo-random number generator ("PJRNG"), which generates a keystream equal in length to the text it is encrypting plus the IV. The text and keystream are XOR'd together to produce the encrypted data. Prepended to the encrypted data is the IV so that the receiving side can seed its PJRNG to XOR the encrypted text with the same keystream to recover the original text.

[0007] Unfortunately, the mere presence of the plain text IV prepended to the encrypted text enables one to easily attack WEP. In a WEP attack, since the JJTV is known, i.e., transmitted as plain text, and the first byte of the encrypted text is known, the first byte of the keystream can be immediately derived. Since a standard WEP key has a first byte that is constrained to values between three (3) and seven (7), and the second byte must be OxFF, all that is necessary is a large sample of data to quickly, e.g., less than 15 minutes, recover the original key. Since the JUV is only 24-bits, there can only be approximately 17 million distinct values. In a typical system, the IV repeats often over a twenty-four (24) hour period. Exploiting this repetition and the weak JJVs makes it very easy to crack WEP. [0008] To counter this problem, a number of solutions have emerged that attempt to fix the problem by developing external fixes to the issues of authentication and security. The typical fix involves a "VPN-like" solution. The solution takes the form of software added to the client-side that encrypts/decrypts data outside of the Wi-Fi card, typically on the user's PC. On the network side of the access point, a server performs the similar function of encryption/decryption. A secure tunnel is formed between the client and the server using the access point only as a conduit between the two ends. Unfortunately, this does not prevent unauthorized users from associating with or using the LAN as the WEP keys can still be easily compromised.

[0009] To solve the above problem, others have developed network appliances that force all access points to be directly connected to an appliance box, which is typically a rack-mounted box that performs a specific bunch of functions on the network. For example, an appliance box is a router or an Ethernet switch, or a web-server or virtual private network (VPN) gateway box. Boxes like

BlueSocket's WG-1000 Wireless Gateway™ provide a separate authentication security server that segregates wireless traffic from the rest of the network. In a sense, a separate LAN is provided, to which all of the access points must connect and then their traffic is directed into their gateway before it is allowed to go onto the LAN.

[0010] Of particular interest is the Port Based Network Access Control JJDBEE

802. lx solution, which is being adopted by numerous parties and has built-in support in Windows JJXP™. IEEE 802. lx is a LAN-based specification that has been modified for use in wireless networks. Particularly, a separate authentication server is used to authenticate users who attempt to connect onto the LAN. When a user, i.e., client, first associates with the access point, the access point forwards the authentication request to the authentication server, which in turn then communicates back through the access point to the client. This back-and-forth process using the access point as a proxy continues until an authentication algorithm is mutually agreed and a successful authentication takes place. 802. lx unfortunately does not specify the authentication method nor does it provide any 'hand-off of information between two access points. Thus, in actual practice two fully-compliant 802. lx- enabled access points may not handle a user the same way on the same network. To use 802. lx technology, legacy access points are generally replaced with new units that support 802. lx.

[0011] There are many others that are developing complementary solutions for Wi-Fi networks. Most, however, offer complex solutions geared towards large- scale networks with 200 or more users. These systems are vendor-specific, expensive, complex to install, require ongoing IT support and maintenance, and may not work with legacy Wi-Fi equipment. SUMMARY OF THE INVENTION

[0012] The present invention overcomes these and other deficiencies of the related art by providing a secure Wi-Fi communications method and system employing a combination of physical keys, or tokens, that attach to existing computing devices and wireless access points. These keys are typically connected via a USB port, although other types of connections, e.g., Ethernet, PC-Card, serial, parallel, and the like may be employed. [0013] The heart of the present invention is a three-factor authentication process. First, each component of the Wi-Fi network employs a physical key. For example, a client key is used to enable wireless connections on a user's computing device. An access point key ("AP key") is used to activate at the access point the secure Wi-Fi functions described herein. Moreover, a master key is provided to enable and administer secure authentication and communications on the network. Each key comprises a serial number, which is forever unique, and must be unlocked using a personal identification number (PIN) known only to the owner, i.e., user, of the key. This PIN can be changed by the owner at any time.

[0014] Second, each physical key comprises a common network send

("JNKS") and a common network receive ("JNKR") cryptographic key used only during the authentication phase by all components on the LAN. Each physical key further includes a unique secret cryptographic key used in the second step of the authentication process. There is no mathematical relationship between key serial numbers and either the network send or network receive cryptographic keys, and the unique secret cryptographic key. The authentication process results in two random numbers that are known by both sides of the wireless channel and are uniquely generated per communications session. For example, when a client connects to an access point, the authentication process results in two unique random numbers being generated (one on each side of the connection). Only the random numbers are sent across the wireless channel and in each case these numbers are encrypted. [0015] Third, a transposed cryptographic key is used to encrypt all communications across the wireless channel between client and access point on behalf of the user. The transposed cryptographic key is preferably a 32-byte (256- bit) key generated using the random numbers generated during authentication and the client's secret cryptographic key. Using the serial number of the client's physical key, the access point knows the client's secret cryptographic key. Thus, both sides of the wireless channel know the secret key without it ever being transmitted between the two. The two random numbers are used to scramble the secret cryptographic key to generate a transposed version, which is finally used by both sides for secure data transmission after authentication. [0016] An advantage of the invention is that both an authentication and security solution is implemented in the access point itself and no additional network appliances or server software are required. Another advantage of the invention is that it can be retro-fitted via software upgrades to existing access points. [0017] Another advantage of the invention is that the secure communications and authentication steps are difficult to hack by an interloper. Particularly, because the use of network send and receive cryptographic keys is very minimal, only two packets per session and per user are ever encrypted with these keys. By contrast, the same cryptographic key is used on every packet for every user in normal Wi-Fi operation implementing WEP. Further, the WEP security algorithm must broadcast a 24-bit Initialization Vector (IV) to seed the decryption process. The IV contains many weak keys, which leads to very rapid hacking of WEP encryption transmissions regardless of key length. The present invention uses no such Initialization Vector.

[0018] Another advantage of the invention is that it allows unique identification of each user, provides positive authentication without the use of back- end servers, and enables transparent roaming. Moreover, the present bi-directional authentication process is not just for identifying the user to the network, but also for the user to make sure that she/he is connecting to the desired network and not just a network that 'looks like' the network to which he's trying to connect. [0019] Another advantage of the invention is its implementation of physical keys, thereby pre-storing secret cryptographic keys in both the client and access point, reduces the prior time and costs to deploy secured Wi-Fi networks, and simplifies network operations. Moreover, the use of physical keys allows the storage of network keys for multiple networks allowing a user the luxury of using a single consistent authentication device for any network to which that user has permission. The physical keys also provide a platform independent of the computing devices on which other applications can be developed that work in conjunction with the similar keys on the AP devices of other networks. [0020] The foregoing, and other features and advantages of the invention, will be apparent from the following, more particular description of the preferred embodiments of the invention, the accompanying drawings, and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] For a more complete understanding of the present invention, the objects and advantages thereof, reference is now made to the following descriptions taken in connection with the accompanying drawings in which: [0022] Fig. 1 illustrates a conventional Wi-Fi network;

[0023] Fig. 2 illustrates a secure Wi-Fi communication system according to an embodiment of the invention;

[0024] Fig. 3 illustrates a key management system according to an embodiment of the invention;

[0025] Fig. 4 illustrates a master key management process according to an embodiment of the invention;

[0026] Fig. 5 illustrates a process for generating a key database according to an embodiment of the invention;

[0027] Fig. 6 illustrates a process for managing an access point key according to an embodiment of the invention;

[0028] Fig. 7 illustrates a process for uploading a client key database file to an access point according to an embodiment of the invention; [0029] Fig. 8 illustrates an authentication system implemented at an access point according to an embodiment of the invention

[0030] Fig. 9A illustrates exchange of authentication frames in a secure Wi-

Fi network according to an embodiment of the invention;

[0031] Figs. 9B-C illustrate an exemplary format of the authentication frames exchanged in the embodiment of Fig. 9 A;

[0032] Fig. 10 illustrates a client device authentication process according to an embodiment of the invention; and

[0033] Fig. 11 illustrates a client device authentication process according to an alternative embodiment of the invention; and [0034] Fig. 12A-E illustrate an example 16-bit key scrambling process for deriving an encryption/decryption key according to an embodiment of the invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0035] Preferred embodiments of the present invention and their advantages may be understood by referring to Figs. 2-12, wherein like reference numerals refer to like elements, and are described in the context of a Wi-Fi network. Nevertheless, the present invention is applicable to both wired or wireless communication networks in general. For example, the present invention enables secure end-to-end access between a client and any computer residing on a network backbone. Often there may not be a wireless component anywhere in such a situation. [0036] The present invention enhances and safeguards Wi-Fi networks by implementing a secure, local, edge method and system (the implementation of which is herein referred to as communicating in a "secure" mode) employing a combination of software routines and physical keys in the form of easy-to-use adapters that attach to existing computing devices and wireless access points via an available USB port. These physical keys are secure, tamper-resistant physical tokens. "Edge" refers to authentication of client devices taking place at the edge or outer boundary of the network, i.e., at the access point, rather than centralized inside the network using a server. As the following will describe in enabling detail, client computing devices are authenticated and data security is provided across wireless links using secret cryptographic keys, which are pre-stored in the physical keys installed at both the client's computing device and the access point. According to an embodiment of the invention, special access point software ("AP software") is provided in the wireless access points and NIC drivers are provided in the client devices to realize the functions described herein and to ensure delivery of standard Wi-Fi functionality as well as compatibility with all Wi-Fi certified products currently installed on a Wi-Fi network.

[0037] Fig. 2 illustrates a secure Wi-Fi network 200 according to an embodiment of the invention. Wi-Fi network 200 comprises a number N of computing devices 210A-N communicating with one another via a wireless access point 220. The access point 220 comprises a Wi-Fi transceiver (not shown) to communicate with a wired network (not shown). Although each computing device 210 is shown as a laptop, other Wi-Fi enabled computing devices such as, but not limited to personal digital assistants (PDAs), desktops, and workstations can be employed within network 200. Moreover, one of ordinary skill in the art recognizes that more than one wireless access point 220 may be implemented within network 200. All computing devices 210A-N can act as clients of network 200. However, at least one computing device such as computing device 210A is reserved as a host computer for administering the inventive features through residing administrative software (not shown) when necessary. In an alternative embodiment, the host computer can be another machine on the wired-side of the network. A master key 230 is installed into an available USB port (not shown) at host computing device 210A during administration and management of the network 200. To facilitate authentication and secure communications, a unique client key 240A-N is installed into an available USB port (not shown) at each computing device 210A-N. Likewise, an access point key ("AP key") 250 is installed into an available USB port (not shown) at access point 220.

[0038] It is important to note that the physical keys described herein are implemented via USB ports. One of ordinary skill in the art recognizes that the master key 230, client keys 240A-N, and AP key 250 can be alternatively implemented by other conventional or foreseeable connection configurations such as, but not limited to PC cards installed via a PCI or ISA slot; a physical token connected via a serial, parallel, or other preferred type of port; an Ethernet card; or a wireless smart card. In yet another implementation, the AP key 250 can be incorporated directly into the internal hardware of the access point 220, thereby alleviating the need for an external physical AP key.

[0039] The master key 230, client keys 240A-N, and AP key 250 overlap in functionality. Particularly, each physical key comprises an embedded tamper- resistant subscriber identity module (SIM) token 232, 242A-N, or 252, respectively, unique to each key. In an embodiment of the invention, a Cryptoflex USB-enabled SIM chip is employed as the SIM token. Nevertheless, other conventional or foreseeable SJTMs may be substituted. The AP key 250 differs slightly from both the master key 230 and the client keys 240 A-N in that it preferably employs a device USB connector rather than a standard USB connector. Generally, a device USB connector is different from a standard USB connector only in physical layout. Yet, they each carry the same signal wires to provide a USB interface to the USB- enabled SJDVI chip, which typically communicates over a simplex data line at approximately 9600 bits-per-second. Importantly, each physical key has a unique serial number stored permanently and electronically inside the SIM by the manufacturer to provide positive identification. Each SIM comprises a random number generator.

[0040] Each client key 240 is used to authenticate and provide secure connections at a corresponding computing device 210. Once the special NIC driver software is installed for a JNIC, the computing device 210 examines whether a Wi-Fi network exists and if found, attempts to associate with that network. If the network is enabled to operate in secure mode, all of the currently configured wireless settings of the computing device 210 are switched to secure mode and the login process is completely automated as further described. If the network is not secure mode enabled, the computing device 210 attempts to connect to it using standard Wi-Fi parameters. The smart NIC driver replaces a standard driver associated via a standard wireless NIC card, thereby providing the software necessary to manage communications with the client key 240. This driver authenticates data packets and performs encryption/decryption functions during secure mode communications. [0041] Like the master key 230, the AP key 250 is first initialized so that it can be recognized by the administrative software and by the AP software as an AP key. The AP key 250 is used to activate functionality in access point 220. In an embodiment of the invention, the access point 220 does not function without the AP key 250 installed. Removal of the AP key 250 causes all associated network connections to be immediately broken and further wireless access through the access point 220 is not possible until the AP key 250 is reinserted. In an alternative embodiment, the access point 220 defaults to standard mode if the AP key 250 is not inserted. If the AP key 250 is inserted, for instance, the access point 220 facilitates the secure mode for properly enabled users, but also provides limited standard Wi-Fi communications for users not properly enabled to use the secure mode. If more than one access point is present within the network, each access point has its own unique AP key.

[0042] The master key 230, while identical in physical design to the client keys 240A-N and the AP key 250, performs additional functionality. Particularly, the master key 230 is used by an administrator to manage a key database (not shown), which will be described in detail below, and the set of client keys 240A-N and AP key 250. The master key 230 is required to operate the administrative software and is used to initialize all client and AP keys. As described below, the master key 230 is initialized after receipt from the manufacturer to identify itself electronically to the administrative software as a master key. Preferably, there is one master key 230 per network 200, although duplicate master keys can be cloned for backup. When installed into a host computer running the administrative software, the master key 230 enables either the creation of or unlocking of the key database. As an optional extra security measure, the master key 230 must be unlocked with an appropriate PIN stored inside the key to become active. If the master key 230 is lost, access to this database and hence maintenance of the network 200 is irretrievably lost.

[0043] Fig. 3 illustrates a key management system 300 according to an embodiment of the invention. Particularly, the key management system 300 comprises the host computing device 210A, the master key 230, and a key database 310. The master key 230 comprises a serial number, a master key network cryptographic send key ("JJMJJKS"), a master key network cryptographic receive key ("JMKR"), a master key cryptographic secret key ("JMKJODS"), and a PIN number. As will be described, MKS, MJKR, and MK_IDS, example values of which are presented in hexadecimal form in the figure, are created upon initialization of the master key. JMK_IDS has no mathematical relationship to the master key serial number. Use of the cryptographic keys will be described in further detail below. As previously mentioned, the PIN number is used to unlock the master key 230, i.e., to access the data stored on SJTM 232, and hence to access the key database 310. The key database 310, which is securely stored within a memory device of host computer 210A, comprises individual records of every client key 240A-N and AP key 250 initialized for use within network 200. Each individual client key record comprises a serial number of the corresponding client key and information such as name of person or computing device that the client key belongs to, location, company department, and any other administrative fields deemed necessary. Each individual client key record is stored in encrypted form using the JMK DS. Key database 310 is referenced by the serial number of the corresponding master key 310 and further comprises the identification of all active AP keys 250 on the network 200 and any pertinent administrative information.

[0044] All encryption/decryption tasks described herein are preferably performed using an Advanced Encryption Standard (AES) algorithm, the implementation of which is apparent to one of ordinary skill in the art. Nonetheless, alternative cryptographic algorithms may be employed, the identification and implementation of which are also apparent to one of ordinary skill in the art. [0045] Fig. 4 illustrates a master key management process 400 according to an embodiment of the invention for initializing the master key 230 and administering the key database 310. The administrative software is first installed (step 410) onto host computing device 210A from a CD-ROM or other suitable storage medium. Upon execution (step 415), the administrative software determines (step 420) whether a master key 230 is inserted into an available USB port. If no master key 230 is present, the administrator is directed to insert (step 425) a master key. Once a master key 230 is inserted, it is analyzed to determine (step 430) whether the master key 230 has been previously and properly initialized, or is currently blank, i.e., MKS, MJKR, and MKJODS have not been created and stored within SIM 232. If the master key 230 is blank, it is first unlocked (step 432) with entry of a correct transport PIN or code. For example, a new master key 230 may be delivered with a transport code that an administrator must correctly enter to gain access to the SIM 232. After unlocking the master key 230, the administrator may replace the transport code with a secret code or PIN selected by the administrator for securing the card. Thus, nobody else can utilize the master key 230 without knowing the secret code. [0046] The administrative software creates (step 435) a JMKJ-DS using a random number generator within the SJDVI 232. MKJDS has no mathematical relationship to the master key serial number. Secret network cryptographic keys JMKS and MKR, which are respectively the send and receive network cryptographic keys common to all users on the network, are then generated (step 440). For example, the administrative software instructs the SIM 232 to generate three random numbers that become the MKS, MKR, and MKJDS. MKJDS, MKS, and MKR, in addition to any administrative information, are then installed (step 445) into SJTM 232 of the master key 230. In an embodiment of the invention, MKS, MKR, and MK_IDS are 256-bit random numbers generated by SIM 232. The administrator is requested (step 450) to enter a correct PIN to lock the master key 230, thereby completing initialization. The administrator is now allowed to create (step 455) a new key database 310 and have it associated with the master key 230 through the master key serial number.

[0047] If the master key 230 inserted is not blank, i.e., it has already been properly initialized for either the current network 200 or another secure mode enabled network, the administrator is requested (step 460) to enter the correct PIN to unlock the master key 230 and gain access to the key database 310. Upon the entry of a correct PIN, the serial number from the master key is retrieved (step 465) to identify and open (step 470) the appropriate key database 310 stored on host computer 210A. Individual client records within the key database 310 are decrypted with JMKJQDS as necessary and key management (step 475), i.e., management of client keys 240A-N and/or AP key 250, is enabled.

[0048] hi an embodiment of the invention, removal of the master key 230 while the administrative software executes automatically closes the key database 310, thereby rendering the client records not viewable, and disabling all administrative and key management functions. Later insertion of a master key with the administrative software still executing again enables the administrative and key management functions. If execution of the administrative software terminates with the master key 230 inserted, the key database 310 is automatically and securely closed. [0049] Fig. 5 illustrates a process 500 for generating a key database 310 according to an embodiment of the invention. Host computing device 210A must have a minimum of two free USB ports, one for the master key 230 and one for each sequential client key 240 added to the key database 310. A properly initialized master key 230 is first inserted (step 510) into host computing device 210A. To gain access to the data stored within the master key 230, and hence the key database 310 on host computer 210A, a correct PIN associated with the master key 230 must be entered (step 515) by an administrator to activate the key. The administrative software then retrieves (step 520) JMK_IDS and the master key serial number. The master key serial number is used to identify and open (step 525) the corresponding key database 310. A client key 240 is inserted (step 530) into the host computer 210A and the administrative software retrieves (step 535) the serial number associated with that client key. The administrative software determines (step 540) if the client key 240 has been previously initialized by identifying whether a corresponding client record exists within the key database 310. If so, the administrative software allows the administrator to view the administrative information associated with the client key 240 by decrypting (step 545) the corresponding key record with MK_IDS. If the client key 240 has not been initialized, cryptographic keys J KS and MKR stored within the master key 230 are copied (step 550) to SJJM 242. JMKS and MKR become the client's cryptographic network send (JNKS) and receive (JNKR) keys respectively, i.e., JMKS is identical to JNKS and JMKR is identical to JNKR. A client key cryptographic secret key ("CK_1DS") is then generated (step 555) having no mathematical relationship to the client key serial number. For example, SJEMJ 232 is instructed to generate a new 256- bit random number for each new client key 240. A simple SIM command will cause the SIM 232 to generate the number that can be read from the SIM 232 into the host computer 210A and then transferred to the client key 240. A client key record is created (step 560) comprising administrative information pertaining to the user or computing device associated with the client key 240, the serial number of the client key 240, and CK JDS encrypted (step 565) with MK JDS. This client key record is then stored (step 570) in the key database 310. The administrator then has the option of initializing another client key (step 575), wherein steps 530-570 are repeated for each additional client key 240.

[0050] Key management of the AP key 250 is performed according to the process 600 illustrated in Fig. 6. Host computing device 210A must have a minimum of two free USB ports, one for the master key 230 and one for the AP key 250. Upon execution (step 610) of an appropriate AP key management subroutine within the administrative software, the administrator is requested (step 615) to insert an AP key 250 into an available USB port. Upon insertion of an AP key, the subroutine checks (step 620) whether the inserted AP key is blank, i.e., not initialized, or is an existing key belonging to network 200 or another secure mode enabled Wi-Fi network. If the AP key 250 is blank, the administrator is required (step 625) to enter a correct PIN to unlock the key. Of course, failure to enter the correct PIN in a certain number of attempts may optionally disable key management functions for a set period of time. Once unlocked, the administrator enters (step 630) the desired administration parameters appropriate to the access point 220 such as network identification, location, access point identification, etc. This information is stored within key database 310 and SUM 252 of the AP key 250. JNKS and JNKR are then installed (step 635) into SIM 252 by copying the values of JMKR and MKS respectively. An access point cryptographic secret key ("AP_JTDS") is then created (step 640) from a random 256-bit number generated by SJDVI 232 and installed in the AP key 250. APJ-DS is encrypted with the MK_IDS and subsequently stored with the AP serial number as an access point record in the key database 310. [0051] It is important to note that the JNKS of the AP key 250 must match the NKR of the client keys 240A-N. Likewise, the NKR of the AP key 250 must match the JNKS of the client keys 240A-N. Thus, when the master key 230 is used to initialize an AP key 250, the JMKS is written into the AP key 250 as its JNKR. The JMKR is written into the AP key 250 as the JNKS. In other words, JMKS and JMKR are flipped in the AP key 250. Moreover, when the master key is used to initialize a client key 240, the JMKS is written into the client key 240 as JNKS (not flipped) and the MKR is written as the JNKR. When the AP key 250 and client keys 240 A-N are used communicate, the AP's JNKR key is identical to the client's JNKS key and the AP's JNKS key is identical to the client's NKR key. Thus, a matched pair of cryptographic keys exists between each pair of endpoints. In an alternative embodiment of the invention, JNKS and JNKR of the client key 240 is flipped with respect to MKS and MKR, and JNKS and NKR of the AP key 250 is not. [0052] If the AP key 250 has been previously initialized, it is determined

(step 645) whether the inserted AP key is associated with the current network 200 or another Wi-Fi network. If AP key 250 is associated with the current network 200 then the parameters of the key excluding any cryptography keys, which are maintained in secret, may be displayed (step 650). For security protection, an administrator can never view or modify any of the cryptographic keys in either the master key 230, client keys 240A-N, or AP key 250. If the inserted AP key is associated with another network, the appropriate parameters of the key may be displayed (step 655). In an embodiment of the invention, one AP key 250 may be associated with a plurality of different secure mode enabled Wi-Fi networks. For example, if the AP key 250 is determined to be associated with another network, the administrator is queried (step 660) as to whether it is desired to have the AP key 250 associated with the present network 200. If so, then the administrator is requested (step 625) to enter a correct PJDSf to unlock the AP key. Once unlocked, steps 630- 640 are repeated for that AP key.

[0053] Fig. 7 illustrates a process 700 implemented by the administrative software to upload a client key database file to an access point 220 according to an embodiment of the invention. Particularly, only information from the client records of key database 310 are uploaded to the access point 220. Process 700 requires that master key 230 is installed into host computer 210A and AP key 250 is installed into access point 220. Particularly, an administrator selects (step 710) via the administrative software an access point displayed from a list of all access points employed on the network 200. The selected access point, e.g., access point 220, is then authenticated (step 715) by implementing the authentication process described in the following paragraphs. Using the serial number of the access point 220, the AP_IDS is retrieved (step 720) from the key database 310. Importantly, the AP key 250 for that network has only one AP_IDS, which is stored in SIM 252 and also in the key database 310. A client key database file comprising the serial numbers and CKJJDS of all registered client keys 240A-N is built (step 725). No information pertaining to the AP key 250 is included in the client key database file, i.e., transferred between the access point 220 and the host computer 210A. The client key database file is encrypted (step 730) using AP_JDS stored within the key database 310 and then transferred (step 735) to the access point 220 where it is decrypted using the AP_JJTDS stored within SJEM 252. In an embodiment of the invention, the access point 220 maintains the client key database file in non-volatile memory. As will be further described in greater detail, any time a client device 210 attempts to authenticate with the access point 220, the client device 210 presents the serial number corresponding to its client key 240. Using this client key serial number, the access point 220 retrieves the corresponding CK_IDS cryptographic key from the client key database file stored within the access point 220. [0054] In an embodiment of the invention, each CKJDDS is encrypted in host computer 210A with AP_JDDS prior to uploading to the access point 220. The client key database file within the access point 220 is a collection of client records. Each client record comprises the plain text serial number and the encrypted CKJODS associated with the corresponding client key 240. To use the CK_JEDS of the client key 240 when communicating with the client device 210, the access point 220 pulls the corresponding record and then decrypts the encrypted CK_IDS with AP_IDS. [0055] The nerve center of the system is the AP software executing at access point 220. The AP software facilitates the authentication of a client computing device 210 attempting to access network 200. Fig. 8 illustrates an authentication system 800 implemented by the AP software at the access point 220 according to an embodiment of the invention. Particularly, authentication system 800 comprises a network interface card 810, a low-level interrupt 820, an authorized clients MAC table 830, an unauthorized client table 840, and a "do not allow" table 850. NIC 810 facilitates communications between the access point 220 and the client devices 210A-N. The authorized clients JMJAC table 830 comprises the JMAC address of all client devices 210, which are presently authorized to communicate on the network 200. The unauthorized client table 840 comprises the JMAC address of all client devices 210 pending authentication. The "do not allow" table 850 comprises the MAC address of all devices that have failed authentication. The low-level interrupt 820 is employed to place any unknown media access control (JMAC) address received from a client device 210 in the unauthorized client table 840. [0056] The client device authentication process is now described with reference to Figs. 9-10. Particularly, Fig. 9 A illustrates the exchange of authentication frames between the client device 210 with a properly configured client key 240 installed and the access point 220 with a properly configured AP key 250 installed during the second step of authentication. Figs. 9B-C illustrate an exemplary format and contents of these authentication frames. Fig. 10 illustrates an authentication process 1000 implemented by the access point 220 and the client device 210.

[0057] Referring to Fig. 9 A, the access point 220 and the client device 210 via respective NICs 810 and 910 communicate with each other on a Wi-Fi channel 920. During the implementation of the authentication process 1000, two authentication frames 922 and 924 are exchanged via Wi-Fi channel 920. In the present embodiment, the network send/receive cryptographic keys are flipped between the access point 220 and the client device 210. In other words, the network send cryptographic key of the access point 220 is identical to the network receive cryptographic key of the client device 210, i.e., JJNKRi = NKS₂ and JNKR₂ = JNKS The subscript designates which device the physical key resides in, e.g., "2" designates client device 210 and "1" designates access point 220. Example values of these parameters along with the serial numbers, random numbers, and secret cryptographic keys APJODS and CK_IDS are presented in the figure to better illustrated the authentication process. It is important to note that JNJKR and JNKS are private cryptographic keys stored in the physical keys 230, 240A-N, and 250. In an alternative embodiment of the invention, other types of cryptographic keys such as public/private cryptographic keys maybe employed, the implementation of which is apparent to one of ordinary skill in the art.

[0058] The format of the authentication frames follow a standard 802.11 authentication framing format, the implementation of which is apparent to one of ordinary skill in the art. As depicted in Figs. 9JB-9C, each frame comprises an authentication algorithm number preferably set to an integer number undefined in the 802.11 specifications, e.g., "3", thereby designated that the authentication process 1000 is to be implemented. Moreover, each frame further comprises an authentication transaction sequence number that is incremented at each stage in the process; a status code that is set to "0" if the stage is successful; and a challenge text field ("challenge") that comprises the particular authentication parameters. Optionally, a cyclic redundancy check (CRC) can be appended to each message to insure the data integrity of each frame. Once in the secure mode, the access point 220 or the client device 210 will not accept an authentication frame designating an authentication algorithm number other than "3".

[0059] Referring to Fig. 10, upon entering the communication range of a wireless Wi-Fi network, client device 210 sends (step 1010) the authentication frame 922 to the access point 220. The challenge of authentication frame 922 comprises the serial number of the client key 240 corresponding to the client device 210 attempting authentication and a first random number (Rl) generated by SJTM 242 of the client key 240. The challenge is encrypted with CK_IDS₂, which is stored within SJJLM 242 of the client key 240. Upon reception of authentication frame 922, the client key serial number allows the access point 220 to retrieve (step 1015) the secret cryptographic key CK_IDS₂ stored within the client key database file and associated with the client key 240 attempting authentication. The access point 220 then decrypts the challenge text with the CK_IDS₂ (step 1020) to obtain the random number Rl generated by the client key 240. If the decryption process yields a null (empty) string, the access point 220 knows the client device 210 is not a trusted device and therefore places (step 1025) the MAC Address of the client device 210 in the "Do Not Allow" table 850. If the decryption process does not yield a 'null' or empty string, then the access point 220 knows that the client device 210 is a trusted component and places (step 1030) the JMAC address of the client device 210 in the "Authorized Users Table" 830.

[0060] One of the quirks of the decryption process is that the process returns either a decrypted string or a null string. A null string is a telltale indicator that the encrypted data could not be decrypted. Thus, if the decrypted result is not a null string, it can be safely assumed that the encryption key matches the decryption key. [0061] The access point 220 forms an authentication response frame 924 featuring a second challenge comprising a second random number JR2 generated (step 1035) by the SIM 252 of the AP key 250, which is encrypted (step 1040) with the same CKJDS₂ associated with the client device 210. This second challenge within authentication frame 924 is sent to client device 210.

[0062] The client device 210 receives and decrypts (step 1045) the second challenge of authentication frame 924 using CK_JEDS stored with SIM 242 to obtain decrypted JR2. If the decryption process yields an empty string, the client device 210 aborts (step 1050) further communications with the access point 220. If the decryption process does not yield a 'null' or empty string, then the client device 210 is assured (step 1055) that it is talking to a trusted component. In other words, a properly decrypted R2 indicates to the client device 210 that the access point 220 knows its secret key and therefore is a trusted component. Both sides now know Rl and JR2 and therefore must Jknow the CK_JDS.

[0063] Although not required, as an added safety measure, frames 922 and

924 are each encrypted with the common network cryptographic keys, e.g., frame 922 with the client's JNKS key and frame 924 with the access point's JNKS key. Decryption is performed at each end with the respective JNKR key. [0064] Fig. 11 illustrates an authentication process 1100 according to an alternative embodiment of the invention. Particularly, upon entering the communication range of a wireless Wi-Fi network, client device 210 sends (step 1110) sends a first challenge to the access point 220. This challenge comprises the serial number of the client key 240 corresponding to the client device 210 attempting authentication and a first random number (Rl) generated by SJDVI 242 of the client key 240. The challenge is encrypted with NKS₂, which is stored within SJDVI 242 of the client key 240.

[0065] Upon reception of the first challenge, the access point 220 decrypts

(step 1115) the challenge with JNKR_l5 which is stored within SJDVI 252 of the AP key 250 to extract the client key serial number and the first random number,. The extracted client key serial number allows the access point 220 to retrieve (step 1120) the secret cryptographic key CK_JDDS₂ stored within the client key database file and associated with the client key 240 attempting authentication. The access point 220 then obtains (step 1125) a second random number (JR2) generated in the SJDVI 252 of the AP key 250. The first random number Rl is encrypted with CK_J-DS₂ obtained from the client key database file. Encrypted Rl is not referred to as Rle. The access point forms a second challenge comprising Rle and R2. This second challenge is then encrypted with NKS₁ and sent (step 1130) to client device 210. [0066] The client device 210 receives and decrypts the second challenge of authentication frame 924 using JNKRi to obtain Rle and R2. Rle is then decrypted (step 1135) with CK_JJTDS₂ from SDVI 242. The client device 210 then compares (step 1140) Rl as originally sent with the Rle received to identify if they match. If they don't match, the client device 210 aborts (step 1145) further communications with the access point 220. If a match is found, i.e., Rle equals Rl, the client device 210 knows the access point 220 is a trusted component.

[0067] The client device 210 responds to the access point 220 with a final challenge. This challenge comprises the second random number JR2 encrypted at the access point 220 with the CK_JJTDS₂. Encrypted JR2 is now referred to as R2e. The client device 210 sends (step 1150) the third challenge encrypted with JNKS₂ to the access point 220. The access point 220 decrypts (step 1155) the third challenge with JNJKRi and then R2e with CK_IDS₂. The access point 220 then compares (step 1160) R2 as originally sent with the decrypted R2e received to identify if they match. If the random numbers do not match, the access point 220 knows the client device 210 is not a trusted device and therefore places (step 1165) the JMAC Address of the client device 210 in the "Do Not Allow" table 850. If R2e equals R2, the access point 220 knows that the client device 210 is a trusted component and places (step 1170) the JMAC address of the client device 210 in the "Authorized Users Table" 830.

[0068] In a related embodiment, the random numbers Rl and R2 are first encrypted with CK_JJDS₂ at the side of the connection where these numbers are generated. For example, the first challenge can comprise Rle instead of Rl, which would then be returned in decrypted form to the client device 210 in the second challenge. Moreover, the second challenge can comprise JR2e instead of R2, which would then be returned in decrypted form to the access point 220 in the third challenge. The selection of the side that first encrypts these random numbers with CK_IDS₂ is not important as long as a comparison is enabled between the random number as originally sent and the corresponding random number received in the subsequent challenge. Thus, enabling each side to determine whether the other side of the connection is employing an identical CKJDDS, and is therefore a trusted component.

[0069] Subsequent secure secret communications are implemented by a two- step encryption/decryption process according to an embodiment of the invention. First, there is the secret cryptographic key, e.g., JMKJDS, CK_JDDS, or AP_JDS, stored in each of the master key 230, the client keys 230A-N, and the AP key 250. Each secret cryptographic key is initially generated randomly from and stored in the respective SJDVI token within the corresponding physical key. These secret cryptographic keys are never used directly to encrypt/decrypt communications, but are used as a starting point for a transposition process, which is described below, based on the two random numbers Rl and R2 generated during the authentication process.

[0070] In an embodiment of the invention, each secret cryptographic key is a

256-bit cryptographic key. Each of the bits are transposed according to a process using the first random number as the starting point and the second random number as the "skip" counter for stepping ahead to the next bit position to be transposed. The process results in a unique transposition of an original key that can be replicated exactly on each side of the communications link without any cryptographic key actually being transmitted. Since the access point 220 knows the secret cryptographic keys of each of the potentially connecting users, e.g., client devices 210A-N, the secret cryptographic key of the authenticated client device 210 can be used in conjunction with the two 'just-now-generated' random numbers to derive a 'new, one-time' cryptographic key for encrypting/decrypting data. Note that during the authentication process, the client key serial number is used as the identifier for the access point to obtain the client's secret cryptographic key, i.e., CKJODS, from the client key database file. As there is no mathematical relationship between client key serial number and the CK_JDS, it is impossible to derive a calculated method of obtaining this secret cryptographic key.

[0071] Referring to Figs. 12A-E, a 16-bit example of the transposition process is illustrated according to an embodiment of the invention. Using the two previously generated random numbers Rl and R2, we would take these two numbers MODULUS 16 and obtain the following two "new" numbers:

[0072] The random numbers are converted modulus the key length. The first random number Rl is used as an initial pointer into the table. Thus, if the first random (10754) number modulus is equal to (2), the 2nd bit is placed into the first bit position of the new key as shown in Fig. 12 A. This 2nd bit position becomes the "pointer." The second random number is a skip counter used as an offset from the pointer. For example, if the second random modulus is equal to three (3), then the pointer moves three positions and picks up the value of the 4th bit in the table. The value of the 4th bit is placed in the 2nd bit position of the new key as shown in Fig. 12B. The process would repeat for each of the remaining bit positions. For example the value of the 7th, 10th, and 13th bits become the 3rd, 4th, and 5th bit positions of the new key as shown in Figs. 12C-E. If the pointer lands on a bit-position previously used, it would increment by one position until an unused position is found. After all 16-bits have been transposed according to the two random numbers, the "new key" is used to encrypt/decrypt transmissions across the link. [0073] In sum, no cryptographic keys of any type are ever transmitted between network devices. Only the serial number of the client's physical key is ever transmitted from the client side and even then, it is encrypted with the network cryptographic keys. No initialization vector (IV) is utilized and there are no restrictions on the key bytes used as in WEP. The two random numbers are generated uniquely for each end of the link by the link participants and last only for the current session. Each client/AP pair will have a unique pair of random numbers, which are always encrypted when sent. The CK_JDS of each client device key 240 is used in conjunction with the two random numbers to further generate a special transposition cryptographic key that is again unique for both participants for that session. As this special cryptographic key used for data transmissions (after authentication) is always a random transposition of the CKJDDS cryptographic keys, extraction of the key is made extremely difficult because each client for each session uses in effect a totally different cryptographic key. All cryptographic keys for authentication are maintained in a secure database at the host computer and portions of this database are securely transferred to each access point allowing the access point to retrieve the user's secret key based on his serial number. [0074] Other embodiments and uses of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. Although the invention has been particularly shown and described with reference to several preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

CLAIMS I claim:

1. A method of authenticating computing devices on a communications network comprising the steps of: receiving a first challenge from a computing device, wherein said first challenge comprises an encrypted first random number and a unique identifier associated with said computing device; obtaining a first secret cryptographic key associated with said unique identifier; generating a second random number; decrypting said first random number with said first secret cryptographic key; encrypting said second random number with said first secret cryptographic key; and transmitting a second challenge to said computing device, wherein said second challenge comprises said encrypted said second random number.

2. The method of claim 1, wherein said unique identifier is a serial number of a physical token installed at said computing device.

3. The method of claim 2, wherein said step of obtaining a first secret cryptographic key comprises the step of retrieving a pre-stored record associated with said serial number, wherein said record comprises said first secret cryptographic key.

4. The method of claim 3, wherein said step of obtaining a first secret cryptographic key comprises the step of receiving a key database file comprising a number of records, wherein each record is associated with a unique physical token and comprises a unique secret cryptographic key and a unique serial number.

5. The method of claim 4, wherein said unique secret cryptographic key is created from a random number generated at initialization of said token.

6. The method of claim 1, further comprising the steps of: decrypting said first challenge with a network receive cryptographic key; and encrypting said second challenge with a network send cryptographic key.

7. The method of claim 3, wherein said step of decrypting said encrypted first random number results in a first value, and further comprising the step of disallowing said computing device to communicate with other computing devices on said network if said first value is a null value.

8. The method of claim 7, wherein allowing said computing device to communicate with other computing devices on said network if said first value is not a null value.

9. The method of claim 7, further comprising the step of decrypting said second challenge with a network receive cryptographic key.

10. The method of claim 8, further comprising the step of decrypting said encrypted second random number with a second secret cryptographic key.

11. The method of claim 10, wherein said second secret cryptographic key is stored within said physical token.

12. A method of deriving a new encryption key for a communication session comprising the steps of claim 1, and the step of transposing said first secret cryptographic key into said new encryption key, wherein said step of transposing comprises the steps of: calculating a modulus N of the first random number to obtain a result n; calculating a modulus N of the second random number to obtain a result m; equating the first bit of said new encryption key to the n-th bit of said secret cryptographic key; and equating the second bit of said new encryption key to the (n+m)th bit of said secret cryptographic key.

13. A communications system comprising: a number of computing devices, and at least one authentication device, wherein each client device or authentication device includes a unique tamper-resistant physical token comprising a random number generator, a unique secret cryptographic key, and and a unique serial number.

14. The system of claim 13, wherein each client device or authentication device further includes a wireless communications transceiver to communicate on a wireless network.

15. The system of claim 14, wherein said wireless network is Wi-Fi network.

16. The system of claim 15, wherein said authentication device is an access point.

17. The system of claim 13, wherein each tamper-resistant physical token is installed via a USB interface.

18. The system of claim 16, wherein said access point includes a database file comprising said serial numbers and secret cryptographic keys associated with said tokens.

19. A method of authenticating computing devices on a communications network comprising the steps of: receiving a first challenge from a computing device, wherein said first challenge comprises a first random number and a unique identifier associated with said computing device; obtaining a first secret cryptographic key associated with said unique identifier; generating a second random number; encrypting said first random number with said first secret cryptographic key; and transmitting a second challenge to said computing device, wherein said second challenge comprises said encrypted first random number and said second random number.

20. The method of claim 19, wherein said unique identifier is a serial number of a physical token installed at said computing device.

21. The method of claim 20, wherein said step of obtaining a first secret cryptographic key comprises the step of retrieving a pre-stored record associated with said serial number, wherein said record comprises said first secret cryptographic key.

22. The method of claim 21, wherein said step of obtaining a first secret cryptographic key comprises the step of receiving a key database file comprising a number of records, wherein each record is associated with a unique physical token and comprises a unique secret cryptographic key and a unique serial number.

23. The method of claim 22, wherein said unique secret cryptographic key is created from a random number generated at initialization of said token.

24. The method of claim 19, further comprising the steps of: decrypting said first challenge with a network receive cryptographic key; and encrypting said second challenge with a network send cryptographic key.

25. The method of claim 21, further comprising the steps of: receiving a third challenge from said computing device, wherein said third challenge comprises said second random number encrypted with a second secret cryptographic key; decrypting said encrypted second random number with said first secret cryptographic key; and comparing said decrypted second random number to said second random number to determine if a match exists.

26. The method of claim 25, wherein if a match exists between said decrypted second random number and said second random number, allowing said computing device to communicate with other computing devices on said network, otherwise if a match does not exist, disallowing said computing device to communicate with other computing devices on said network.

27. The method of claim 25, further comprising the step of decrypting said third challenge with a network receive cryptographic key.

8. The method of claim 25, wherein said second secret cryptographic key is stored within said physical token.