Pre-authenticated communication within a secure computer network

FIELD OF THE INVENTION

[0001] The invention generally relates to the field of secure network communications. The invention relates more specifically to a method for pre-authenticating communications between a client and a middleware server in a network.

BACKGROUND OF THE INVENTION

[0002] Recently, technology has been developed that allows for wireless devices, such as personal digital assistants (PDAs), cell phones, and two-way pagers, to access computer networks; computer networks are no longer physically limited to a hard-wired environment. In the past, database or systems administrators for a computer network have been forced to work within the physical confines of a secure office computer network at a company or other organization. Access to a computer network through a wireless device allows the administrator to monitor and manage the computers within the network remotely. If the administrator does not happen to be physically near in the event of a crisis, then wireless access translates directly into a quicker response to problems and less downtime. This is extremely valuable to companies, such as banks, auction houses, brokerage firms, etc., which must keep their systems running uninterrupted in order to prevent a loss of revenue.

[0003] Thus, wireless devices provide an excellent solution to many old problems in systems and database administration, but they also introduce a new problem: how can communications within a network that includes wireless devices be kept secure? For a system or database to be administrated or managed remotely, communications within the network must be kept secure at all times and in all places to avoid a leak of confidential information. The difficulties of keeping a computer network secure are increased dramatically when wireless communications are allowed between computers within the network.

[0004] In the present state of the art in wireless communications, information is transmitted to and from a wireless device by electromagnetic radiation that will inevitably travel through public spaces. It is not desirable, and in some cases it may be a violation of law, for a company to allow public access to the information kept in its computer network. In addition, data must be transferred between a server inside, and a server outside a company's Intranet before it can be broadcast to a wireless device. Each connection must be secure to prevent unauthorized access to a secure computer network. Since private or confidential information may be kept in a computer within a secure computer network, it is extremely important that all communications within a network are secure.

[0005] Wireless devices present additional challenges to securing a computer network since they usually have fewer computing resources (e.g., processing power, memory, and bandwidth) available than do non-portable or handheld devices. Previous methods for securing a computer network have relied on algorithms that require a very fast processor or a long time to complete. Other methods have relied on a large amount of memory. The security methods used with non-wireless devices are not useful for securing a wireless device.

[0006] Currently, one of the most widely used methods for securing a computer network is with public key (also called “asymmetric”) encryption. The use of public key encryption, in which a secret key is securely exchanged between a client and a server using a public key, is so prevalent that most current versions of Web browsers, such as NETSCAPE NAVIGATOR or MICROSOFT INTERNET EXPLORER, come preinstalled with “Certificates” for the most often visited “Certificate Authorities” on the Web.

[0007] Public key encryption is not well adapted for use within a computer network that includes wireless devices. Public key encryption is slow and difficult to implement in hardware. Public key encryption algorithms may run 10,000 times slower than a comparable private key (or “symmetric”) encryption algorithm. Even in the future, when wireless devices are built with the computational resources today available only for desktop computers, public key encryption methods would be undesirable. In part because of their wide use there are many known ways for circumventing public key encryption.

[0008] One serious vulnerability in the public key encryption method exists in a step of requesting and transferring a private key from an internal server to a client within a network. This vulnerability can be exploited by “hijacking” a private key request from the client to the internal server. The request is hijacked by an “impostor” server, a server that acts in place of the internal server intended for communication with the client. The impostor server sends its own private key back to the client, and subsequent communication between the client and the impostor server is carried out with that private key—the client has no way of knowing that the impostor server is not the internal server it had intended for communication, and all information transferred to the impostor server is available for inspection by the impostor server's owner, usually a competing or hostile company that has specifically targeted the client will engage in this kind of attack. Use of a public key encryption method, in this case, would make all of the confidential information transferred within the computer network directly available to that competitor.

BRIEF SUMMARY OF THE INVENTION

[0009] The present invention is a method for secure network communication between a client and an internal server. The method involves the use of a middleware server, which allows ill-performing and potentially insecure communications protocols to be off-loaded onto a more powerful machine running in a more secure environment, e.g., within a company's Intranet. There are three basic steps in the method: (1) using a middleware server for processing public key encrypted messages sent between the client and the internal server; (2) using the client and the internal server for processing private key encrypted messages sent between the client and the internal server; and (3) using the middleware server, relaying private key encrypted messages sent between the client and the internal server. The security of the method can be further improved in by adding the step of pre-authenticating the client with a server key by securely copying the server key from the middleware server to the client.

[0010] No particular private key encryption is necessary for the method of the present invention, and in different embodiments of the invention different private key (or symmetric) encryption algorithms may be used. Accordingly, an additional step of using algorithm identification information to specify a private key encryption algorithm used for processing private key encrypted messages sent between the client and the internal server may be implemented.

[0011] Connections requested by a client may not always be established. In an embodiment, the present invention also provides an optional step of using the middleware server to notify the client when a connection between the client and the internal server is not completed.

[0012] In an embodiment, a method for secure network communication between a client and an internal server using a middleware server, might be implemented with a set of steps that may include, but is not limited to the following set of steps. The steps do not necessarily have to be executed in the order specified below, and could be executed in a different order.

[0013] The method begins by using the middleware server to generate a server key. The server key is then stored in memory on the middleware server. The memory used for storing the server key might be a hard disk, floppy disk, read only memory (ROM), random access memory (RAM), or some other form of memory designed to store digital information. The client is then pre-authenticated by securely copying the server key from the middleware server to the client, and by storing the server key in memory on the client. Subsequent communications between the client and the middleware server are carried out using the server key to encrypt and decrypt the communications.

[0014] The second set of steps includes using the client to generate location information for identifying the location of the internal server. After generation of the location information, which might be an Internet Protocol (IP) address or host name, the client continues by encrypting the location information using the server key stored in memory on the client to produce server key encrypted location information. The server key encrypted location information is sent from the client to the middleware server. The middleware server decrypts the server key encrypted location information using the server key stored in memory on the middleware server to produce the (original) location information generated by the client.

[0015] A significant advantage to the present invention is achieved in the next step, in which the middleware server is used to perform the public key encryption (or “handshaking”) necessary for secure communication with the internal server. The processing of public key messages sent between the middleware server and the internal server in this step saves the computing resources of the client from being spent on such public key encryption.

[0016] After performing public key encryption, the middleware server requests a connection with the internal server specified by the location information. The internal server generates a session key, and continues the method by sending the session key to the middleware server. Having received the session key, the middleware server proceeds by encrypting the session key using the server key stored in memory on the middleware server to produce a server key encrypted session key, which is sent from the middleware server to the client.

[0017] Upon receipt of the server key encrypted session key, the client takes the step of decrypting the server key encrypted session key using the server key stored in memory on the client to produce the (original) session key. The client then continues by creating connection information for a connection between the client and the internal server. Using the session key, the client then encrypts the connection information in order to produce session key encrypted connection information, and sends the session key encrypted connection information to the middleware server.

[0018] The middleware server receives the session key encrypted connection information, and proceeds by relaying session key encrypted connection information to the internal server. The internal server decrypts the session key encrypted connection information using the session key that it generated, and may then proceed by completing a connection between the client and the internal server with the connection information. Once the connection has been completed, the middleware server may be used to patch the connection through to the client from the internal server.

[0019] The security of the method may be further improved by forcing the client to connect to the middleware server on a predetermined port, which might not be a “well-known” port, as would be used for typical non-secured network communication.

[0020] In another embodiment of the present invention, the private key (or symmetric) encryption algorithm used to produce the session key (and to encrypt and decrypt communications between the client and the internal server) is specified by using the internal server to generate an algorithm identification. The algorithm identification might be in any data format that would allow for a particular encryption algorithm within a finite set of such algorithms to be identified uniquely. In an embodiment, the set of symmetric encryption algorithms might include DES, DESX, AES, 3DES, Blowfish, or IDEA. Other symmetric encryption algorithms might be chosen to be included with the set based on the kinds of computing resources available and on other factors, as is known to one of ordinary skill in the art.

[0021] After selecting an algorithm, and producing an algorithm identification, the method proceeds with the step of sending the algorithm identification from the internal server to the middleware server. Before sending the algorithm identification to client, the middleware server encrypts the algorithm identification using the server key stored in memory on the middleware server to produce server key encrypted algorithm identification. Upon receipt at the client, the server key encrypted algorithm identification is decrypted, producing the (original) algorithm identification. The encryption algorithm that is to be used with the session key is identified with the algorithm identification. When more than one encryption algorithm is used and identified according to this method, the difficulty of cracking an encrypted messages increases greatly: when the messages are encrypted using different algorithms, the message contents may not be “guessed” as easily by comparison (i.e., the messages are not as susceptible to cryptanalysis because both the algorithm and the key space varies).

[0022] In order to further secure the computer network using the method of the present invention, an optional set of steps including a “pinging” or periodic polling may be implemented. The pinging may be performed in either direction within the network, i.e., in the present invention, a ping might be sent from the client to the middleware server, from the middleware server to the client, from the middleware server to the internal server, or from the internal server to the middleware server. Connections that remain idle for longer than a predetermined length of time might be dropped. This feature makes certain cryptanalytic attacks on the computer network more difficult, since some attacks may require passive listening on the client side in order to gain unauthorized access to the network.

[0023] In an embodiment of the present invention, the public key encryption is carried out using the Secure Sockets Shell (SSH). SSH establishes a single TCP/IP connection from the client to the server. The communications through the connection are encrypted (using an asymmetric encryption algorithm). Both the client and the server identity may be authenticated (or pre-authenticated as in the present invention) using SSH. The communications may also be compressed. In other embodiments of the present invention, a different protocol, such as SSL or TSL might be used for these steps of the method, and, as would be recognized by one of ordinary skill in the art, it is not necessary to the present invention that SSH be used with these steps in the method.

[0024] Another embodiment of the present invention relies on the 3DES encryption algorithm as its symmetric encryption algorithm, using 3DES to generate the session key (although the algorithm may also be varied, as described above). The 3DES algorithm is a modification of the older Data Encryption Standard (DES) algorithm. The DES has a key length of 56 bits, which is often expressed as a 64-bit number, with the extra eighth bits being used for parity. From the key, 16 subkeys are derived, which are used in 16 separate rounds of the algorithm. The 3DES encryption algorithm is substantially similar to the DES algorithm, but is applied in three separate rounds, with a new 56-bit key in each round. The 3DES encryption algorithm is thought to be unbreakable (i.e., not vulnerable to cryptanalysis) for the foreseeable future, even taking into account future advances in computing resources.

[0025] In order to implement the method of the present invention within a computer network that includes wireless devices, it may be necessary to perform some additional manipulations to the data transferred between wireless devices and other computers within the network. In particular, communications to and from a wireless device may be short because of bandwidth considerations, even as short as a single key stroke. According to an embodiment of the present invention, short communications are “padded” with zeros before encryption and the padding of zeros is removed after decryption. This additional step may be necessary for the method of the present invention to be used with certain encryption algorithms that require a minimum block size.

[0026] An important advantage of the present invention is that it is not limited to use with a computer network that includes wireless devices. The present invention is well adapted for use in securing a computer network that includes wireless devices because it lessens the burden on the computing resources of a client, but it is not necessary to the present invention that the client be a wireless device. The client could be any computer within a computer network. In particular, the client might be a computer that has fewer computing resources than other computers within the computer network, but is not a wireless device. As would be recognized by one of ordinary skill in the art, there is nothing about the method of the present invention that requires the use of a wireless device within the computer network, and the present invention might be implemented for use within a network that includes other types of clients with limited computing resources, such as a computer network of Internet appliances or game consoles.

BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The foregoing and other objects, advantages, and features of the present invention will be apparent from the following detailed description and the accompanying drawings, in which:

[0028]FIG. 1 is a block diagram of the overall structure of a secure computer network in accordance with an embodiment of the present invention;

[0029]FIG. 2 is a block diagram of a client side within a secure computer network in accordance with an embodiment of the present invention;

[0030]FIG. 3 is a block diagram of a Virtual Private Network (VPN) client side within a secure computer network in accordance with an embodiment of the present invention;

[0031]FIG. 4 is a flowchart that illustrates a first part of the control flow of steps performed in securing communications between a wireless device and a middleware server in accordance with an embodiment of the present invention;

[0032]FIG. 5 is a flowchart that illustrates a second part of the control flow of steps performed in securing communications between a wireless device and a middleware server in accordance with an embodiment of the present invention;

[0033]FIG. 6 is a flowchart that illustrates a third part of the control flow of steps performed in securing communications between a wireless device and a middleware server in accordance with an embodiment of the present invention; and

[0034]FIG. 7 is a block diagram of how the control flow of steps is performed on the computers within the secure computer network in an embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

[0035] While the present invention is susceptible to various modifications and alternative forms, certain preferred embodiments are shown by way of example in the drawings and will be described in detail herein. It should be understood, however, that the description is not intended to limit the invention to the particular forms described; on the contrary, the description is intended to cover all modifications, alternatives, and equivalents falling within the spirit and scope of the invention defined by the appended claims.

[0036] It is relatively simple for a company to maintain a secure network (or “Intranet”) within its office if that network does not connect to any computers outside the office. In particular, most computer network security problems would be eliminated if the Intranet of a company did not connect to the Internet, or to other outside, non-secure network. Nevertheless, most businesses consider a connection to the Internet to be indispensable because of the efficiencies created in communication with customers and clients through electronic mail and the World Wide Web. Even greater efficiencies are available when network connections are extended to wireless devices, although wireless devices present a special challenge because of the limited computing resources that are available on most wireless devices. In the present invention, the middleware server, which is located within the secured company Intranet, is used to perform the most resource intensive operations of the method, effectively freeing up the computing resources of the clients to perform other functions, such as systems or database administration.

[0037] The present invention is used for securing communications within a computer network that includes a plurality of clients connected to an Intranet through a non-secure network such as the Internet. In FIG. 1, the overall structure of a secure computer network is shown schematically. In general, data transferred within the secure computer network is transmitted and received through the Internet <b>130</b> (or a VPN Tunnel <b>140</b> within the Internet <b>130</b>) between a client side <b>120</b> (or a VPN client side <b>110</b>) and an Intranet <b>160</b>. FIG. 2 shows an embodiment of a typical client side <b>120</b>, and FIG. 3 shows an embodiment of a typical VPN client side <b>110</b>.

[0038] Communications begin at the client side <b>120</b> with a client <b>250</b>, which is a wireless device, such as a PDA, cell phone, or two-way pager in an embodiment of the present invention. At the most basic level, data within the secure computer network is transferred from a client <b>250</b> in FIG. 2 to a router <b>185</b>, mainframe <b>180</b>, public switch <b>175</b>, or internal server <b>170</b> in FIG. 1. This transfer is accomplished through the use of the plurality of computers that comprise the secure computer network as shown in FIGS. 1, 2, and <b>3</b>. For the secure computer network to be completely secure, data must be encrypted, and the connection must be protected every time two of the computers within the system transfer data.

[0039] Wireless devices present a special challenge. For the computer network of FIG. 1 to be made secure, data must be prevented from being intercepted or captured as it is transferred by radio frequency to and from a wireless device through spaces that may be public. FIG. 2 shows a client side <b>120</b>, including a plurality of wireless device clients <b>250</b>, in greater detail. Before broadcast between a client <b>250</b> in FIG. 2 and a wireless base station <b>220</b> the data is compressed and parsed into packets designed for low bandwidth wireless broadcast. After broadcast, the data is recollected and decompressed before any decryption is performed.

[0040] While wireless communications are described herein by way of example as radio frequency communications, it should be understood that the invention is not limited to radio frequency electromagnetic radiation as a mode of wireless communication. Such wireless communication may utilize other frequencies of electromagnetic radiation such as x-ray, ultraviolet, visible, infrared or microwave. Wireless communication might also rely on other forms of transport such as statistical fluctuations in the average density of matter like acoustic or seismic waves. Even dynamically varying chemical potentials or thermal gradients might be harnessed as a mode for wireless communication.

[0041] The computer network shown in FIG. 2 is typical of wireless computer networks that allow for a wireless device to connect to an internal server <b>170</b> in FIG. 1 through the Internet <b>130</b>. Wireless base stations are labeled <b>220</b> in FIG. 2. A wireless base station might be part of a wireless network architecture such as MOBITEX or MOTIENT that uses digital packet-switching methods such as the Global System for Mobile Communication (GSM), Time Division Multiple Access (TDMA), or Code-Division Multiple Access (CDMA). In another embodiment, the wireless network architecture might be circuit-switched. A wireless base station <b>220</b> is connected through a physical cable <b>230</b> to a wireless proxy server <b>210</b>. In transfer between a wireless base station <b>220</b> and a wireless proxy server <b>210</b> (or between a wireless base station <b>220</b> and a middleware server <b>100</b> in FIG. 1), data might be encrypted with a second encryption method using both public and private keys (as described below), for example, using a low-layer security protocol such as the Secure Socket Shell (SSH) in addition to other encryption implemented within the system.

[0042] The computer network shown in FIG. 2 is used to provide wireless access to a wide geographical region. In an embodiment, there is a plurality of wireless base stations <b>220</b> in FIG. 2, each providing wireless access to a different geographical region (also known as a cell). Each wireless base station <b>220</b> is connected to a wireless proxy server <b>210</b>. The wireless proxy server <b>210</b> that is connected to the wireless base stations <b>220</b> is also connected to the Internet <b>130</b>, but the wireless proxy server <b>210</b> might also be connected to another network, such as a Metropolitan Area Local Area Network (MLAN), Wide Area Local Area Network (WLAN), or other network not in the control of the secure computer network owner. Data transferred from a wireless device client <b>250</b> to the Internet <b>130</b> through a wireless proxy server <b>210</b> is also converted from standard wireless protocols and languages such as WAP, WDP, and WML into protocols and languages that can be used with the Internet such as TCP/IP, FTP, HTTP, and HTML.

[0043] The Intranet <b>160</b> in FIG. 1 is an embodiment of a computer network that might be implemented within the office headquarters of a company to allow communications between company personnel. Data transferred through the Internet <b>140</b> to a middleware server <b>100</b> inside the Intranet <b>160</b> passes through a firewall <b>150</b> implemented within an Intranet <b>160</b>. The firewall allows Internet <b>130</b> access only through predetermined ports. In another embodiment, the firewall <b>150</b> restricts the Internet IP addresses that may access the middleware server <b>100</b>, or the internal server <b>170</b> within the Intranet <b>160</b> to the IP addresses of the wireless proxy server <b>210</b> in FIG. 2. This step limits access to clients <b>250</b> connected to the secure computer network through a particular wireless proxy server <b>210</b> that is known to be secure.

[0044] Alternatively, the firewall might restrict the IP addresses that may access a server within the Intranet <b>130</b> to the IP addresses of each client <b>250</b> connected to the secure computer network, allowing an even greater degree of control over access to the secure computer network. In yet another embodiment, the secure computer network is further secured through the use of a firewall and a bastion host server in a screened subnet firewall (or “DMZ”) configuration, with one firewall <b>150</b> between the Internet <b>130</b> and the middleware server <b>100</b>; the middleware server <b>100</b> acts as the bastion host server. In the DMZ configuration, the network outside the Intranet <b>160</b> sees only the IP address or host name of the middleware server <b>100</b>, and the network inside the Intranet <b>160</b> only sees the IP address or hostname of the firewall <b>150</b>. All communications are forced through the middleware server <b>100</b>. As would be recognized by one of ordinary skill in the art, in this embodiment three separate computers must be successfully hacked before the Intranet <b>160</b> could be accessed from the Internet <b>130</b>.

[0045] A computer network may be further secured by implementing a virtual private network (VPN). As shown in FIG. 1, a VPN client side <b>110</b> can also communicate, through a VPN Tunnel <b>140</b> within the Internet <b>130</b>, with the Intranet <b>160</b>. FIG. 3 shows a block diagram of a typical VPN client side <b>110</b>. The VPN is implemented by limiting access to every computer or computer network intervening a wireless base station <b>220</b> in FIG. 3 and the Intranet <b>160</b> in FIG. 1. The main differences in the structure of a typical client side <b>120</b> as shown in FIG. 2 and a VPN client side <b>110</b> as shown in FIG. 3 are the VPN-controlled wireless proxy server <b>300</b> in FIG. 3 and the VPN Tunnel <b>140</b>. A wireless base station <b>220</b> connects to a VPN-controlled wireless proxy server <b>300</b> rather than a standard wireless proxy server (<b>210</b> in FIG. 2). The VPN-controlled wireless proxy server <b>300</b> might then connect to only certain VPN-controlled servers and routers that are part of the Internet <b>130</b>. The plurality of VPN-controlled Internet servers and routers between a VPN-controlled proxy server <b>300</b> and a firewall <b>150</b> in FIG. 1 is known as a VPN Tunnel <b>140</b>, and is shown in FIGS. 1 and 3. The VPN does not allow users outside the secure computer network to have any access to data transferred within the secure computer network; they cannot inspect data within the secure computer network and they cannot find out from whence data is transmitted or received; they cannot see the data at all.

[0046] A method for using the middleware server <b>100</b> to secure a computer network, which may include wireless devices, is shown in FIGS. 4, 5, and <b>6</b>. The steps shown in FIGS. 4, 5, and <b>6</b> are implemented with software loaded onto computers within the secure computer network. Table 1 below show how the principal Java SSH classes are modified in order to complete the method of the present invention. Note that it is not necessary that the present invention be implemented with the Java programming language, or with the SSH protocol. Table 1 is provided as an illustration of one embodiment of the present invention, and one of ordinary skill in the art would know how to implement the method of the present invention on other operating systems, with other protocols, and in other programming languages. <tables id="TABLE-US-00001" num="1"><table frame="none" colsep="0" rowsep="0" pgwide="1"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="294PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 1</entry></row></thead><tbody valign="top"><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Principal Java SSH classes modified in an embodiment of the present invention</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="49PT" align="left" /><colspec colname="2" colwidth="49PT" align="left" /><colspec colname="3" colwidth="77PT" align="left" /><colspec colname="4" colwidth="119PT" align="left" /><tbody valign="top"><row><entry>CLASS NAME</entry><entry>COMPUTER</entry><entry>PURPOSE</entry><entry>MODIFICATIONS REQUIRED</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry>Ssb</entry><entry>Server within</entry><entry>Main class of the</entry><entry>Removal of references to client side;</entry></row><row><entry /><entry>Intranet</entry><entry>application</entry><entry>implementation of method using 3DES</entry></row><row><entry /><entry /><entry /><entry>server key</entry></row><row><entry>SshIO</entry><entry>Client</entry><entry>SSH 1.5 implementation</entry><entry>Change to relay data to client using</entry></row><row><entry /><entry /><entry /><entry>3DES, rather than displaying locally</entry></row><row><entry>SshPacket</entry><entry>Server within</entry><entry>SSH 1.5 packet layer</entry><entry>None</entry></row><row><entry /><entry>Intranet AND</entry><entry>protocol implementation</entry></row><row><entry /><entry>client</entry></row><row><entry>SshCrypto</entry><entry>Server within</entry><entry>Encrypt and decrypt</entry><entry>None</entry></row><row><entry /><entry>Intranet</entry><entry>implementation</entry></row><row><entry>Server</entry><entry>Server within</entry><entry>Listens for a connection</entry><entry>Modify to comply with requirements of</entry></row><row><entry /><entry>Intranet</entry><entry>from client and spawns</entry><entry>operating system</entry></row><row><entry /><entry /><entry>new threads, as required</entry></row><row><entry>SshTerm</entry><entry>Client</entry><entry>Terminal emulation</entry><entry>Modify to comply with requirements of</entry></row><row><entry /><entry /><entry>implementation (for</entry><entry>client operating system</entry></row><row><entry /><entry /><entry>connection to server)</entry></row><row><entry>Client</entry><entry>Client</entry><entry>Main class with</entry><entry>Modify to comply with requirements of</entry></row><row><entry /><entry /><entry>networking, 3DES</entry><entry>client operating system</entry></row><row><entry /><entry /><entry>decryption algorithm,</entry></row><row><entry /><entry /><entry>and interface</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0047] The start <b>400</b> of the control flow sequence for the method of secure network communication between a client <b>250</b> and an internal server <b>170</b> using a middleware server <b>100</b> is shown in FIG. 4. In the first step after start <b>400</b>, the middleware server <b>100</b> is used to generate a server key <b>405</b>. The server key is then stored <b>410</b> in memory on the middleware server <b>100</b>.

[0048] Pre-authentication in step <b>420</b> of the client <b>250</b> by preloading of the server key from the middleware server <b>100</b> onto the client <b>250</b> offers an important advantage of the present method. The server key is generated within the secure Intranet <b>160</b>, and securely copied from the middleware server <b>100</b> to the client <b>250</b>, using a secure copying means such as a floppy disk, direct cable, or file share within the Intranet <b>160</b>. This step of the method might be carried out at the beginning of a work day or work week in which the user of the client <b>250</b> intends to be away from the secure Intranet <b>160</b>, but connected to it through a non-secure network such as the Internet <b>130</b>. After secure copying to the client <b>250</b>, the client proceeds with the method by storing the server key in memory <b>430</b>. Subsequent communications between the client <b>250</b> and the middleware server <b>100</b> are carried out using the server key to encrypt and decrypt the communications.

[0049] The client <b>250</b> is now equipped to communicate securely with the middleware server <b>100</b>. Step <b>440</b> shows the first step the client <b>250</b> takes in establishing a connection with an internal server <b>170</b>. In step <b>440</b>, the client <b>250</b> is used to generate location information for identifying the location of the internal server <b>170</b> within the secure computer network. The location information might be an Internet Protocol (IP) address or host name associated with a particular IP address. The use of such a host name constitutes an additional security feature of the system. When the client knows only the host name rather than the IP address of an internal server <b>170</b>, it becomes more difficult for the client to gain unauthorized access to the internal server <b>170</b> through the network by requesting a connection with that IP address directly (without the connection being passed through the middleware server <b>100</b> or firewall <b>150</b>).

[0050] The next set of steps allows secure communication of the location information between the client <b>250</b> and the middleware server <b>100</b>, where the location information can be used to establish a connection. In step <b>450</b> the client <b>250</b> continues by encrypting the location information using the server key stored in memory on the client <b>250</b> to produce server key encrypted location information. The server key encrypted location information is sent in step <b>460</b> from the client to the middleware server.

[0051] Step <b>455</b> is optional; the connection between the client <b>250</b> and the middleware server <b>100</b> may be further secured in step <b>455</b> by predetermining what port the client <b>250</b> will connect with on the middleware server <b>100</b>. Connection requests for another port on the middleware server <b>100</b> might be denied immediately. By picking a port that is not “well-known” (e.g., well-known port 22 for SSH, 80 for HTTP, or 443 for HTTPS), the difficulty of “listening in on” a connection increases. Without knowing the predetermined port, an attacker might have to search through close to 50,000 separate ports before identifying the port being used for communication.

[0052] Step <b>470</b> is required for recovering the encoded information sent between the client <b>250</b> and the middleware server <b>100</b>. Having received the server key encrypted location information in step <b>460</b>, the middleware server <b>100</b> decrypts in step <b>470</b> the server key encrypted location information using the server key stored in memory on the middleware server <b>100</b> to produce the (original) location information, which was generated by the client <b>250</b> in step <b>440</b>.

[0053] At this point the middleware server <b>100</b> is ready to begin facilitating a connection between the client <b>250</b> and an internal server <b>170</b> within the Intranet <b>160</b>. The present invention achieves a tremendous advantage in the next step <b>480</b>, in which the middleware server is used to perform the public key encryption (or “handshaking”) necessary for secure communication with the internal server. The processing of public key encryption algorithms is a computing resource intensive operation. Off-loading this processing onto the middleware server <b>100</b>, which is located within the more secure Intranet <b>160</b>, makes the present invention faster and more secure than previous methods of securing a computer network that included resource limited clients <b>250</b>, such as wireless devices.

[0054] With the location information for an internal server <b>170</b>, the middleware server <b>100</b> can request in step <b>485</b> a connection with the internal server <b>170</b> specified by the location information. Upon receipt of such a request, the internal server <b>170</b> generates in step <b>500</b> (shown in FIG. 5) a session key, and sends the session key to the middleware server <b>100</b> in step <b>510</b>. The circle labeled A in step <b>490</b> connects the steps of FIG. 4 to the next set of steps in FIG. 5.

[0055] The session key generated in step <b>500</b> is generated using a private key encryption algorithm, which may be selected from a set of such algorithms, as described above in the BRIEF SUMMARY OF THE INVENTION. When the private key encryption algorithm is selected from a set of algorithms, it is necessary for the session key sent to be accompanied by algorithm identification, so that an intended user of the session key will know what private key encryption algorithm the session key is meant to be used. Steps <b>505</b> and <b>520</b> show the optional generating and sending of this algorithm identification along with the session key from the internal server <b>170</b> to the middleware server <b>100</b>.

[0056] Before sending the session key (or algorithm identification) outside the Intranet <b>160</b>, the middleware server <b>100</b> needs to secure this information. If an attacker could obtain either, the security of the system would be substantially compromised, although no confidential information would be directly lost. To further secure the computer network, the middleware server <b>100</b> proceeds in step <b>530</b> (and <b>540</b>) by encrypting the session key (and the algorithm identification) using the server key stored in memory on the middleware server <b>100</b> to produce a server key encrypted session key, which is sent from the middleware server <b>100</b> to the client <b>250</b>. Computers on the Internet <b>130</b> that have not been pre-authenticated with the client <b>250</b> in step <b>420</b> will not be able to access the session key (or algorithm identification), even though the packets containing this information will be transferred through publicly accessible computers on the Internet <b>130</b>.

[0057] The pre-authentication of the client <b>250</b> in step <b>420</b> allows the client, upon receipt of the server key encrypted session key, to take the step <b>570</b> (and <b>580</b>) of decrypting the server key encrypted session key (and algorithm identification) using the server key stored in memory on the client <b>250</b> to produce the (original) session key (and algorithm identification). Having obtained the session key, and optionally the identification of the algorithm to be used with the session key, the client <b>250</b> may now communicate securely with the internal server <b>170</b> through the Internet <b>130</b> without the help of the middleware server <b>100</b>. The middleware server <b>100</b> is now not necessary for communications between the client <b>250</b> and the internal server <b>170</b> to be kept secure (although the middleware server <b>100</b> may still be used for security at a higher level, or for other functions within the secure computer network). The circle labeled B <b>590</b> in FIG. 5 connects the steps of FIG. 5 to the next set of steps in FIG. 6.

[0058] The client <b>250</b> is ready now to establish a secure session with the internal server <b>170</b>, and in step <b>600</b> (shown in FIG. 6) the client <b>250</b> generates connection information for a connection between the client and the internal server. Using the session key (and the algorithm identification) in step <b>620</b> (and step <b>610</b>), the client <b>250</b> encrypts the connection information in order to produce session key encrypted connection information, and sends the session key encrypted connection information to the middleware server <b>100</b>.

[0059] An embodiment of the connection information and location information is shown in Table 2. The embodiment shown in Table 2 has been implemented for XML based communication format between the client and the server. The information is hard-coded, in this XML based embodiment, to include the character length of the columns and the number of rows (30 and 17, respectively). This is done to comply with the specific requirements set by the operating system running on the client, which might be, for example, Windows CE. By hard-coding these values into the message request for connection, the connection that is established will produce output that will fit onto the screen of the client, which might be a wireless device such as a PDA, cell phone, or two-way pager. In other embodiments of the present invention, the operating system running on the client may do formatting without a need for formatting information to be hard-coded into the connection and location information. <tables id="TABLE-US-00002" num="2"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 2</entry></row></thead><tbody valign="top"><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>XML Embodiment of Location and Connection Information</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="105PT" align="left" /><colspec colname="2" colwidth="112PT" align="left" /><tbody valign="top"><row><entry>LOCATION INFORMATION</entry><entry>CONNECTION INFORMATION</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>&lt;?xml version=\“1.0\”?&gt;</entry><entry>&lt; xml version=\“1.0\”?&gt;</entry></row><row><entry>  &lt;pa</entry><entry>  &lt;pa</entry></row><row><entry>  host=‘cluster.interaccess com’</entry><entry>  username=‘demo’</entry></row><row><entry>  port=‘22’</entry><entry>  password=‘demonstration’</entry></row><row><entry>  preferredCipher==‘3des’ /&gt;</entry><entry>  rows=‘17’ &gt;</entry></row><row><entry /><entry>  columns=‘30’ /&gt;</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0060] Although the middleware server <b>100</b> must receive the session key encrypted connection information, it does not decrypt and re-encrypt the connection information, rather it acts only to relay in step <b>630</b> the session key encrypted connection information onto the internal server <b>170</b>. The internal server <b>170</b> decrypts in step <b>640</b> the session key encrypted connection information using the session key that it generated (in step <b>500</b>), and may then complete a connection between the client <b>250</b> and the internal server <b>170</b> with the connection information in step <b>650</b>. Once the connection has been completed in step <b>650</b>, the middleware server <b>100</b> is used to patch the connection through in step <b>660</b> to the client <b>250</b> from the internal server <b>170</b>.

[0061] Once the connection has been completed and patched through, the additional step <b>670</b> of pinging between the client <b>250</b> and middleware server <b>100</b>, and between the middleware server <b>100</b> and the internal server <b>170</b> may be performed. The pinging may be done in either direction, e.g., for the middleware server to the client or from the client to the middleware server.

[0062] As is known to those of ordinary skill in the art, the description of the steps in the method of the present invention shown in FIGS. 4, 5, and <b>6</b> can be carried out readily by implementing the method in software on the clients <b>250</b>, middleware server <b>100</b>, and the internal server <b>170</b>. The method presented is in fact more specific than is necessary for obtaining some of the more important advantages of the present invention. In particular, the middleware server <b>100</b> may do the processing of public key encryption for clients <b>250</b> using methods other than that presented in the foregoing. For example, additional steps might be necessary to meet the requirements of certain proprietary operating systems in a computer network. Such additional steps should not be construed to be outside the scope of the present invention, since such steps are generally known to those of ordinary skill in the art as necessary for implementing a method in software on a computer network.

[0063] The combination of structure and function that allows for important advantages of the present invention to be obtained is shown schematically in FIG. 7. The network environment of the client <b>250</b>, middleware server <b>100</b>, and internal server <b>170</b> are not shown in FIG. 7 because the environment is not necessary to the function of the present invention.

[0064] It is important to note at this point that the use of the internal server <b>170</b> in the foregoing description of the method of the present invention is not intended to restrict the method to the use of an internal server <b>170</b> specifically. The internal server <b>170</b> is simply used as an example of a computer within a network, such as that shown in FIG. 1, that is connected to the middleware server <b>100</b>. The internal server <b>170</b> as shown in FIG. 7, and as described in the foregoing, might be any computer within a network, for example, a router <b>185</b>, mainframe <b>180</b>, or public switch <b>175</b> (as shown in FIG. 1).

[0065] The method of the present invention, as presented above, requires the use of a middleware server <b>100</b>, which allows ill-performing and potentially insecure communications protocols to be off-loaded onto a more powerful machine running in a more secure environment, e.g., within a company's Intranet (<b>160</b> in FIG. 1). The three most basic steps of the method are: (step <b>480</b>) using a middleware server <b>100</b> for processing public key encrypted messages sent between the client and the internal server; (step <b>730</b>) using the client and the internal server for processing private key encrypted messages sent between the client and the internal server; and (step <b>630</b>) using the middleware server, relaying private key encrypted messages sent between the client and the internal server. The basic step <b>730</b> includes both encryption and decryption of communications made within the network using a private key, such as the session key, and thus constitutes a combination of several steps of the method shown in FIGS. 4, 5, and <b>6</b>.

[0066] The processing of public key encryption in step <b>480</b> might be performed in either direction of communication, i.e., in messages sent from the internal server <b>170</b> to the client <b>250</b>, or from the client <b>250</b> to the internal server <b>170</b>. It is important to note, however, that middleware server <b>100</b> is not simply a repository for a public key. In the method of the present invention, the step <b>480</b> performed by the middleware server <b>100</b> does not require a database or other type of storage device to hold public keys for the client <b>250</b> or internal server <b>170</b>.

[0067] Even more importantly, the processing of public key encryption shown as step <b>480</b> in FIG. 7 does not require for private key encrypted information, which is encrypted in steps <b>730</b> in FIG. 7. There is no need for private key communications to be decrypted and re-encrypted on the middleware server <b>100</b>. Such decryption and re-encryption on the middleware server <b>100</b> would present an opportunity for an attack on the system by gaining control over the middleware server <b>100</b>. The danger of such an attack is alleviated in the present invention because, according to the method of the present invention, communications between the client <b>250</b> and the internal server <b>170</b> would not be available for inspection, even if an attacker gained control of the middleware server <b>100</b> in the middle of a connection. The present invention thus overcomes the problem of “hijacking” discussed in the BACKGROUND OF THE INVENTION, above.

[0068] Although it is not absolutely necessary for keeping the computer network secure, the additional step <b>420</b> of pre-authenticating the client with the server key <b>720</b> by generating the server key on the middleware server <b>100</b> in step <b>405</b>, and by securely copying the server key <b>720</b> from the middleware server <b>100</b> to the client <b>250</b> in step <b>420</b> gains a great advantage in securing the computer network.

[0069] In an embodiment of the present invention, the method shown in FIGS. <b>4</b>-<b>7</b> is implemented with the Java programming language. But as is known to those of ordinary skill in the art, the middleware server <b>100</b> and clients <b>250</b> may have software implemented with other programming languages, and the software may be run on any platform or operating system. It is within the scope of the present invention for the method to be implemented even on the hardware level, in an assembly language specific to a device within a computer network that needs to be secured. The method of the present invention might be implemented directly in the hardware of one or more computers within the network.

[0070] The encryption method shown in FIGS. <b>4</b>-<b>7</b> is performed, in an embodiment, on TCP/IP packets using the 3DES symmetric encryption algorithm. The embodiment of the encryption method shown in FIGS. <b>4</b>-<b>7</b> can also be combined with other protocols and encryption methods, for example, by using the middleware server <b>100</b> to proxy connections established with the SSH 1.5 or 2.0 protocol.

[0071] An important advantage of the present invention is that the algorithm chosen for use in encrypting the communications between a middleware server <b>100</b> and a client <b>250</b> (as shown in the embodiment of the method of FIGS. <b>4</b>-<b>7</b>) can be any encryption algorithm. In an embodiment, it is the 3DES symmetric algorithm; in other embodiments, it may use the Blowfish, DESX, or IDEA algorithm. The choice of algorithm can be made with the computing resources of one particular embodiment of the secure computer network in mind, so that the algorithm can be tailored to the specific strengths and weaknesses of the hardware for that embodiment. Similarly, the protocol used for communication between the middleware server <b>100</b> and another server outside the Intranet <b>160</b> could be any protocol, such as SSL, SFTP, or SSH. Furthermore, the embodiment of the method shown in FIGS. <b>4</b>-<b>7</b> will not interfere with other security methods implemented directly on a client <b>250</b>.

[0072] It should be understood that various changes and modifications to the presently preferred embodiments described herein would be apparent to those skilled in the art. Such changes and modifications may be made without departing from the spirit and scope of the present invention and without diminishing its attendant advantages.