CA2438357A1 - System and method for secure remote access - Google Patents
System and method for secure remote access Download PDFInfo
- Publication number
- CA2438357A1 CA2438357A1 CA002438357A CA2438357A CA2438357A1 CA 2438357 A1 CA2438357 A1 CA 2438357A1 CA 002438357 A CA002438357 A CA 002438357A CA 2438357 A CA2438357 A CA 2438357A CA 2438357 A1 CA2438357 A1 CA 2438357A1
- Authority
- CA
- Canada
- Prior art keywords
- client
- server
- information package
- public key
- session
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 title claims abstract description 46
- 238000004590 computer program Methods 0.000 claims description 19
- 230000008520 organization Effects 0.000 description 16
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000013024 troubleshooting Methods 0.000 description 2
- 230000002457 bidirectional effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001010 compromised effect Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000003745 diagnosis Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/44—Program or device authentication
- G06F21/445—Program or device authentication by mutual authentication, e.g. between devices or programs
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
- H04L63/061—Network architectures or network communication protocols for network security for supporting key management in a packet data network for key exchange, e.g. in peer-to-peer networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
Abstract
Disclosed is a method of directing a client to establish a secure connection with a server across a public network, the server and the client having exchanged a Server Authentication Public Key, a Client Authentication Public Key, and a Remote Service Unique Identifier (RSUID) during a registration process. The method includes the steps of: transmitting to the server a client information package having the RSUID and a client challenge information package encrypted with the Server Authentication Public Key, receiving from the server a server information package having the RSUID and a server challenge information package and a portion of the received client challenge information encrypted with the Client Authentication Public Key, using the Client Authentication Private Key to decrypt and verify the server challenge information package, and, transmitting to the server an encrypted portion of the received client challenge information.
Description
SYSTEM AND METHOD FOR SECURE REMOTE ACCESS
FIELD OF THE INVENTION
(0001] The present invention relates generally to a system and method for establishing a secure connection between a server and a client over a public network and specifically to a method for providing secure remote access to the client by the server.
BACKGROUND
FIELD OF THE INVENTION
(0001] The present invention relates generally to a system and method for establishing a secure connection between a server and a client over a public network and specifically to a method for providing secure remote access to the client by the server.
BACKGROUND
[0002] Refernng to Figure 1, a system for a remote software product environment is illustrated generally by numeral 100. The system 100 includes a customer system 102 and a service organization system 104. The customer system 102 includes a software product lOb and a service client 108. The service organization 104 includes a service gateway 110 and a session end point 112. The service client 108 is coupled with the service gateway 110 via a network 114. Typically, the network 114 is a public network, such as the Internet.
Optionally, one or both of the service client 108 and the service gateway 110 are connected to the network 114 via a firewal1116.
Optionally, one or both of the service client 108 and the service gateway 110 are connected to the network 114 via a firewal1116.
[0003) Servicing a remote software product has many challenges, including transferring diagnostic data from the customer system 102 to the organization system 104, transfernng software product updates from to the organization system 104 to the customer system 102, and remote troubleshooting for problem diagnosis.
[0004] Transfernng diagnostic data from the customers system 102 to the organization system 104 is an issue since diagnostic data often contains sensitive information.
Typically, a File Transfer Protocol (FTP) is used for transferring files, even though it is inconvenient for the customers and insecure for both the customers and the service organization.
Typically, a File Transfer Protocol (FTP) is used for transferring files, even though it is inconvenient for the customers and insecure for both the customers and the service organization.
[0005] Transferring software product updates, such as fixpaks and service releases to customer system 102 from the organization system 104 is an issue since the organization system 104 providing the latest software product update should be authenticated to ensure that a malicious server is not providing malicious software instead of the expected software product update.
Typically, certificates issued by a trusted third party are used for authenticating the organization system 104.
Typically, certificates issued by a trusted third party are used for authenticating the organization system 104.
[0006] Yet further, the need for remote troubleshooting between the customer system 102 and the organization system 104 provides several issues. For example, telephone support is typically provided by many organizations. Telephone conversations can easily lead to lost information and many errors are difficult to communicate over the telephone. Alternately, some customers will allow a telnet connection into their customer system 102, which is very insecure.
[0007] Today, there is no convenient and secure facility that can alleviate these challenges. As software and hardware products become more complex, the need for convenient and a secure remote service facility is becoming more and more critical. In fact, such a solution is already desperately required. As a result, it is an abject of the present invention to obviate or mitigate at least some of the above mentioned disadvantages.
SUMMARY
SUMMARY
(0008] In accordance with an aspect of the present invention there is provided a method of directing a client to establish a secure connection with a server across a public network, the server and the client having exchanged a Server Authentication Public Key, a Client Authentication Public Key, and a Remote Service Unique Identifier (RSUID) during a registration process, the method including: transmitting to the server a client information package having the RSUID and a client challenge information package encrypted with the Server Authentication Public Key, receiving from the server a server information package having the RSUID and a server challenge information package and a portion of the received client challenge information encrypted with the Client Authentication Public Key, using the Client Authentication Private Key to decrypt and verify the server challenge information package, and, transmitting to the server an encrypted portion of the received client challenge information.
[0009] In accordance with another aspect of the invention, there is provided a computer program product having a computer readable medium tangibly embodying computer executable code for directing a client to establish a secure connection with a server across a public network, the server and the client having exchanged a Server Authentication Public Key, a Client Authentication Public Key, and a Remote Service Unique Identifier (RSUID) during a registration process, the computer program product including code for directing the client to:
transmit to the server a client information package having the RSUID and a client challenge information package encrypted with the Server Authentication Public Key, receive from the server a server information package having the RSUID and a server challenge information package and a portion of the received client challenge information encrypted with the Client Authentication Public Key, use the Client Authentication Private Key to decrypt and verify the server challenge information package, and, transmit to the server an encrypted portion of the received client challenge information.
transmit to the server a client information package having the RSUID and a client challenge information package encrypted with the Server Authentication Public Key, receive from the server a server information package having the RSUID and a server challenge information package and a portion of the received client challenge information encrypted with the Client Authentication Public Key, use the Client Authentication Private Key to decrypt and verify the server challenge information package, and, transmit to the server an encrypted portion of the received client challenge information.
[0010] In accordance with yet another aspect of the invention, there is provided a method for directing a server to establish a secure connection with a client across a public network, the server and the client having exchanged a Server Authentication Public Key, a Client Authentication Public Key, and a Remote Service Unique Identifier (RSUID) during a registration process, the method including: receiving from the client a client information package having the RSUID and a client challenge information package encrypted with the Server Authentication Public Key, using the RSUID to retrieve an associated Server Authentication Private Key, using the Server Authentication Private Key to decrypt and verify the client challenge information package, and, transmitting to the client a server information package having the RSUID and a server challenge information package encrypted with the Client Authentication Public Key.
(0011] In accordance with yet another aspect of the invention, there is provided a computer program product having a computer readable medium tangibly embodying computer executable code for directing a server to establish a secure connection with a client across a public network, the server and the client having exchanged a Server Authentication Public Key, a Client Authentication Public Key, and a Remote Service Unique Identifier (RSUID) during a registration process, the computer program product including code for directing the server to:
receive from the client a client information package having the RSUID and a client challenge information package encrypted with the Server Authentication Public Key, use the RSUID to retrieve an associated Server Authentication Private Key, use the Server Authentication Private Key to decrypt and verify the client challenge information package, and, transmit to the client a server information package having the RSUID and a server challenge information package encrypted with the Client Authentication Public Key.
BRIEF DESCRIPTION OF THE DRAWINGS
receive from the client a client information package having the RSUID and a client challenge information package encrypted with the Server Authentication Public Key, use the RSUID to retrieve an associated Server Authentication Private Key, use the Server Authentication Private Key to decrypt and verify the client challenge information package, and, transmit to the client a server information package having the RSUID and a server challenge information package encrypted with the Client Authentication Public Key.
BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The embodiments of the present invention will be explained by way of the following drawings, in which:
Figure 1 is block diagram of a remote software product environment (prior art);
Figure 2 is a flow chart illustrating the operation of a registration process in accordance with an embodiment of the invention; and Figures 3A and 3B are a flow chart illustrating the operation of establishing a secure session between a server and a client in accordance with an embodiment of the invention.
Figure 1 is block diagram of a remote software product environment (prior art);
Figure 2 is a flow chart illustrating the operation of a registration process in accordance with an embodiment of the invention; and Figures 3A and 3B are a flow chart illustrating the operation of establishing a secure session between a server and a client in accordance with an embodiment of the invention.
(0013] Similar references are used in different figures to denote similar components.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0014] The following detailed description of the embodiments of the present invention does not limit the implementation of the invention to any particular computer programming language.
The present invention may be implemented in any computer programming language provided that the Operating System (OS) provides the facilities that may support the requirements of the present invention. A preferred embodiment is implemented in the C or C++
computer programming language (or other computer programming languages in conjunction with C/C++).
Any limitations presented would be a result of a particular type of operating system, computer system, or computer programming language and would not be a limitation of the present invention.
The present invention may be implemented in any computer programming language provided that the Operating System (OS) provides the facilities that may support the requirements of the present invention. A preferred embodiment is implemented in the C or C++
computer programming language (or other computer programming languages in conjunction with C/C++).
Any limitations presented would be a result of a particular type of operating system, computer system, or computer programming language and would not be a limitation of the present invention.
[0015] As previously described, many of the problems relating to servicing a remote software product stem from security related issues associated with communicating remotely through the Internet. These problems relate to connection establishment, authentication, and privacy.
[0016] Since it is often convenient to use the Internet to communicate between the customer system 102 and the organization system 104, the present embodiment of the invention uses an Internet connection for communicating between the two systems. However, any system that allows incoming connections to the Internet is at risk for Denial of Service (DOS) attacks or being compromised by hackers. As a result, most customers do not want a server that accepts connections on the Internet that could potentially expose their systems) to the raw Internet.
Most customers feel reasonably safe about initiating a connecting out to a server on the Internet.
Most customers feel reasonably safe about initiating a connecting out to a server on the Internet.
(0017] Further, the invention may have access to potentially damaging functionality or sensitive data. Thus, ensuring that only authorized remote service teams at the service organization 104 have access to the customer system 102 is critical. Likewise, ensuring that only authenticated service clients 108 at the customer system 104 can connect to the service gateway 110 is equally important.
[0018] Yet further, any sensitive data that flows over the public network should be encrypted to prevent a third party from eavesdropping.
[0019] In accordance with the above requirements, the invention enables the customer system 102 to establish a connection with the organization system 104 using a public network, such as the Internet. Further, the invention allows the customer system 102 to communicate with the organization system 104 in a secure manner, while authenticating the identity of the customer system 102 to the organization system 104 and vice versa. Details of the operation of the 1 S invention are described as follows.
[0020] Without an extremely high level of security, any remote service facility will put both the service organization system's company and its customers at risk. An initial handshake between the service clients 108 and service gateway 110 is performed for ensuring a high level of security and authentication.
[0021] Initially, a registration process is performed for registering a customer for remote service.
Referring to Figure 2, a flow chart illustrating the operation of the registration process is shown.
In step 202, the customer receives a Remote Service Unique Identifier (RSUID) that is used to differentiate the customer from other remote service customers. The RSUID need not be confidential and can be shared with the public. In step 204, the customer receives a confidential authentication public key, referred to hereinafter as the Server Authentication Public Key. The Server Authentication Public Key is the public key portion of a public/private key pair generated at the server. The Server Authentication Key is similar to a password in that it is used by the service client 108 for authenticating the service gateway 110. Thus, it is preferable that there is only one Server Authentication PubliclPrivate Key pair per service client 108.
In step 206, the customer generates a public/private key pair. The public key, referred to hereinafter as the Client Authentication Public Key, is provided to the server. Similarly to the Server Authentication Public Key, it is preferable that the Client Authentication Public Key remain unadvertised and confidential.
Referring to Figure 2, a flow chart illustrating the operation of the registration process is shown.
In step 202, the customer receives a Remote Service Unique Identifier (RSUID) that is used to differentiate the customer from other remote service customers. The RSUID need not be confidential and can be shared with the public. In step 204, the customer receives a confidential authentication public key, referred to hereinafter as the Server Authentication Public Key. The Server Authentication Public Key is the public key portion of a public/private key pair generated at the server. The Server Authentication Key is similar to a password in that it is used by the service client 108 for authenticating the service gateway 110. Thus, it is preferable that there is only one Server Authentication PubliclPrivate Key pair per service client 108.
In step 206, the customer generates a public/private key pair. The public key, referred to hereinafter as the Client Authentication Public Key, is provided to the server. Similarly to the Server Authentication Public Key, it is preferable that the Client Authentication Public Key remain unadvertised and confidential.
[0022] The operation described above is typically performed only at registration. However, the customer may request to reregister occasionally for a variety of reasons, such as for a suspected security breach. Thus, it can be seen that the registration process described with reference to Figure 2 will be performed relatively infrequently. As a result, this operation can be performed offline, or using encryption to transfer the data and certificates from a trusted third party to authenticate the customer and server.
[0023] Once the customer has registered with the server, a remote service session can be established. Referring to Figure 3, a flow chart illustrating the steps for establishing a remote session is shown. In step 302, the customer system initiates a connection. The service client 104 establishes a Transmission Control Protocol/ Internet Protocol (TCPIIP) connection, or session, to the service gateway. This is similar to having the customer use the telnet protocol to connect to a remote system through the Internet, although the following steps ensure a much higher level of security than a telnet connection.
(0024] In step 304, the service gateway 110 generates a Temporary Server Public/Private key pair. The Temporary Server Public Key is transmitted, unencrypted, to the service client 108 for use in initiating the session.
[0025] In step 306, the service client 104 encrypts a client challenge information package using the Server Authentication Public Key, received from the service client at step 204 of the registration operation. The client challenge information package includes the following components. A session counter identifying the number of times that a service session has been established for this particular Remote Service Unique Identifier. A Client Session Public Key that it wishes to use for this session. Alternately, instead of the Client Session Public Key, a previous session ID can be included. A word length value representing the length of a Server Challenge Word. Preferably, the length is between 64 and 256 bytes. The Server Challenge Word comprises a random number of randomly generated bytes of information, generated by the service client 108. A flag value, typically an integer, contains a set of flags, which request the type of session to establish, such as unidirectional, bidirectional, and the like. Optionally, the client challenge information package may include a session indicator for identifying the session lifetime.
[0026] In step 307, the service client 108 uses the Temporary Server Public Key to encrypt a client identification information package. Preferably, the client identification information package is independent of the software version of the software product 106.
Further, the client identification information package includes the Remote Service Unique Identifier and the encrypted client challenge information package.
Further, the client identification information package includes the Remote Service Unique Identifier and the encrypted client challenge information package.
(0027] In step 308, the service client 108 sends the client identification information package to the service gateway 110. In step 309, the service gateway 110 uses the Temporary Server Private Key to decrypt the client identification information package. The Remote Service Unique Identifier is used to look up a corresponding Server Authentication Private Key, which is used to attempt to decrypt the client challenge information package.
[0028] In step 310, it is determined whether the service gateway 110 can decrypt the client challenge information package. That is, if the service gateway 110 can interpret and verify the client challenge information package, the service client 108 will have been authenticated and the service gateway 110 proceeds to step 314. If the service gateway 110 cannot decrypt the client challenge information it proceeds to step 312.
[0029] In step 312, the service gateway 110 sends an error message to the service client 108 and immediately closes the connection. Closing the connection immediately is important to reduce the impact of Denial of Service attacks that are TCPlIP connection establishment related.
[0030] In step 314, the service gateway 110 uses the Client Authentication Public Key, received from the service client at step 206 of the registration operation, for encrypting a server challenge information package. The server challenge information package includes the following components. A number of times that a service session has been established for this Remote Unique Service Identifier. A Server Session Public Key that the service gateway wishes to use for the duration of the session. Alternately, instead of the Client Session Public Key, a previous session ID can be included. The Server Challenge Word is returned to prove that the service gateway could decrypt the client challenge information package. A confirmation flag value, typically an integer, that contains a set of flags confirming the type of session to establish. A
large, for example 256-byte, randomly generated Client Challenge Word and a session identification (ID). Optionally, the server challenge information package may include a session indicator for confirming the session lifetime.
large, for example 256-byte, randomly generated Client Challenge Word and a session identification (ID). Optionally, the server challenge information package may include a session indicator for confirming the session lifetime.
[0031] In step 316, the service gateway 110 uses the Client Session Public Key received from the service client 108 in the client identification information package to encrypt a server identification information package. If the client identification information package included a session ID instead of a Client Session Public Key, the Client Session Public Key associated with the session ID is used to encrypt the server identification information package. The server identification information package includes the Remote Service Unique Identifier and the server challenge information package. In step 318, the service gateway 110 sends the server 1 S identification information package to the service client 108.
[0032] In step 320, the service client 108 uses the Client Session Private Key to decrypt the server identification information package and the Client Authentication Private Key to attempt to decrypt the server challenge information package.
[0033] In step 322, it is determined whether the service client 108 can decrypt the server challenge information package. That is, if the service client 108 can interpret and verify the server challenge information package, the service gateway 110 will have been authenticated and the service client 108 proceeds to step 326. If the service client 108 cannot decrypt the server challenge information it proceeds to step 324.
[0034] In step 324, the service client 108 sends an error message to the service gateway 110 and immediately closes the connection. In step 326, the service client uses the Server Session Public Key received in the server challenge information package to encrypt the received Client Challenge Word and session ID. If the server challenge information includes a previous session ID instead of the Server Session Public Key, a Server Session Public Key associated with the previous session ID is used to encrypt the Client Challenge Word and current session ID. In step 328, the encrypted Client Challenge Word and session ID are transmitted to the service gateway 110 to prove that the service client 108 could decrypt the server challenge information package.
[0035] At this point, a remote, secure, authenticated and encrypted connection has been established between the service client 108 and the service gateway 110. The encryption for the connection is performed using the exchanged sessions keys for both sides, which were encrypted twice before they were transmitted.
[0036) Each newly established session can be uniquely identified by the Remote Service Unique Identifier and the Session ID. When a new session is created, the service gateway 110 sends a notification of the session to a default-session handling facility. The notification includes the Remote Service Unique Identifier, the Session ID, and a newly generated internal session password. The default session-handling facility may be one or more service analysts or it may be an automated service program.
(0037] A session may be transferred between session-handling facilities, where the session-handling facility is handled by a human, computer program, or other handling facility. Further, a session may be transferred between any number of session handling facilities, where the session can be handled by more than one session-handling facility at any given time.
Yet further, it is possible that any type of remote service capability or facility can use the secure service session.
Yet further, it is possible that any type of remote service capability or facility can use the secure service session.
[0038] If the session is prematurely broken due to a network error or the like, the session ID can be used to re-establish the connection. Thus, it is preferable that both sides store the session ID, the public key of the remote side and the private key for the local side for a session. A session can only be re-established from the customer's system.
[0039] A customer can register or un-register for remote service at any time, which provides another level of security. For customers who want even more security, they may choose to only register for remote service when a major problem occurs.
[0040] Although the method for creating a secure session described above is described as a single method, it is likely that in practice the method will be implemented as two dependent methods, running independently of each other. The first method comprises the client method, which attempts to validate and connect to a server. The second method comprises the server method, which attempts to validate and connect to a client. It is possible that an unauthenticated client may try to connect to the server, or that the client may try to connect to an unauthenticated server. However, only when an authenticated client tries to connect to an authenticated server will a secure session be established.
[0041] Though the above embodiments are described primarily with reference to a method aspect of the invention, the invention may be embodied in alternate forms. In an alternative aspect, there is provided a computer program product having a computer-readable medium tangibly embodying computer executable instructions for directing a computer system to implement any method as previously described above. It will be appreciated that the computer program product may be a floppy disk, hard disk or other medium for long term storage of the computer executable instructions.
[0042] In yet an alternative aspect, there is provided an article having a computer-readable signal-bearing medium, and having means in the medium for directing a computer system to implement any method as previously described above. It will be appreciated that a supplier of the compiler may upload the article to a network (such as the Internet) and users may download the article via the network to their respective computer systems.
[0043] It will be appreciated that variations of some elements are possible to adapt the invention for specific conditions or functions. The concepts of the present invention can be further extended to a variety of other applications that are clearly within the scope of this invention.
Having thus described the present invention with respect to a preferred embodiment as implemented, it will be apparent to those skilled in the art that many modifications and enhancements are possible to the present invention without departing from the basic concepts as described in the preferred embodiment of the present invention. Therefore, what is intended to be protected by way of letters patent should be limited only by the scope of the following claims.
Having thus described the present invention with respect to a preferred embodiment as implemented, it will be apparent to those skilled in the art that many modifications and enhancements are possible to the present invention without departing from the basic concepts as described in the preferred embodiment of the present invention. Therefore, what is intended to be protected by way of letters patent should be limited only by the scope of the following claims.
Claims (20)
The embodiments of the invention in which an exclusive property or privilege is claimed are defined as follows:
1. A method of directing a client to establish a secure connection with a server across a public network, the server and the client having exchanged a Server Authentication Public Key, a Client Authentication Public Key, and a Remote Service Unique Identifier (RSUID) during a registration process, the method comprising:
transmitting to the server a client information package having the RSUID and a client challenge information package encrypted with the Server Authentication Public Key;
receiving from the server a server information package having the RSUID and a server challenge information package and a portion of the received client challenge information encrypted with the Client Authentication Public Key;
using the Client Authentication Private Key to decrypt and verify the server challenge information package; and, transmitting to the server an encrypted portion of the received client challenge information.
transmitting to the server a client information package having the RSUID and a client challenge information package encrypted with the Server Authentication Public Key;
receiving from the server a server information package having the RSUID and a server challenge information package and a portion of the received client challenge information encrypted with the Client Authentication Public Key;
using the Client Authentication Private Key to decrypt and verify the server challenge information package; and, transmitting to the server an encrypted portion of the received client challenge information.
2. The method of claim 1, wherein the client information package is encrypted using a temporary public key assigned by the server.
3. The method of claim 1, wherein the server information package is decrypted using a Client Session Private Key.
4. The method of claim 1, wherein the client challenge information package further includes the Client Session Public Key.
5. The method of claim 1, wherein the client challenge information package further includes a previous session ID for enabling the server to select a Client Session Public Key associated with the previous session ID.
6. A computer program product having a computer readable medium tangibly embodying computer executable code for directing a client to establish a secure connection with a server across a public network, the server and the client having exchanged a Server Authentication Public Key, a Client Authentication Public Key, and a Remote Service Unique Identifier (RSUID) during a registration process, the computer program product comprising code for directing the client to:
transmit to the server a client information package having the RSUID and a client challenge information package encrypted with the Server Authentication Public Key;
receive from the server a server information package having the RSUID and a server challenge information package and a portion of the received client challenge information encrypted with the Client Authentication Public Key;
use the Client Authentication Private Key to decrypt and verify the server challenge information package; and, transmit to the server an encrypted portion of the received client challenge information.
transmit to the server a client information package having the RSUID and a client challenge information package encrypted with the Server Authentication Public Key;
receive from the server a server information package having the RSUID and a server challenge information package and a portion of the received client challenge information encrypted with the Client Authentication Public Key;
use the Client Authentication Private Key to decrypt and verify the server challenge information package; and, transmit to the server an encrypted portion of the received client challenge information.
7. The computer program product of claim 6, further including code for encrypting the client information package using a temporary public key assigned by the server.
8. The computer program product of claim 6, further including code for decrypting the server information package using a Client Session Private Key.
9 The computer program product of claim 6, wherein the client challenge information package further includes the Client Session Public Key.
10. The computer program product of claim 6, wherein the client challenge information package further includes a previous session ID for enabling the server to select a Client Session Public Key associated with the previous session ID.
11. A method for directing a server to establish a secure connection with a client across a public network, the server and the client having exchanged a Server Authentication Public Key, a Client Authentication Public Key, and a Remote Service Unique Identifier (RSUID) during a registration process, the method comprising:
receiving from the client a client information package having the RSUID and a client challenge information package encrypted with the Server Authentication Public Key;
using the RSUID to retrieve an associated Server Authentication Private Key;
using the Server Authentication Private Key to decrypt and verify the client challenge information package; and, transmitting to the client a server information package having the RSUID and a server challenge information package encrypted with the Client Authentication Public Key.
receiving from the client a client information package having the RSUID and a client challenge information package encrypted with the Server Authentication Public Key;
using the RSUID to retrieve an associated Server Authentication Private Key;
using the Server Authentication Private Key to decrypt and verify the client challenge information package; and, transmitting to the client a server information package having the RSUID and a server challenge information package encrypted with the Client Authentication Public Key.
12. The method of claim 11, wherein the client information package is decrypted at the server using a temporary private key.
13. The method of claim 11, wherein the server information package is encrypted using a Client Session Public Key.
14. The method of claim 11, wherein the server challenge information package further includes the Server Session Public Key.
15. The method of claim 11, wherein the server challenge information package further includes a previous session ID for enabling the client to select a Server Session Public Key associated with the previous session ID.
16. A computer program product having a computer readable medium tangibly embodying computer executable code for directing a server to establish a secure connection with a client across a public network, the server and the client having exchanged a Server Authentication Public Key, a Client Authentication Public Key, and a Remote Service Unique Identifier (RSUID) during a registration process, the computer program product comprising code for directing the server to:
receive from the client a client information package having the RSUID and a client challenge information package encrypted with the Server Authentication Public Key;
use the RSUID to retrieve an associated Server Authentication Private Key;
use the Server Authentication Private Key to decrypt and verify the client challenge information package; and, transmit to the client a server information package having the RSUID and a server challenge information package encrypted with the Client Authentication Public Key.
receive from the client a client information package having the RSUID and a client challenge information package encrypted with the Server Authentication Public Key;
use the RSUID to retrieve an associated Server Authentication Private Key;
use the Server Authentication Private Key to decrypt and verify the client challenge information package; and, transmit to the client a server information package having the RSUID and a server challenge information package encrypted with the Client Authentication Public Key.
17. The computer program product of claim 16, further including code for decrypting the client information package at the server using a temporary private key.
18. The computer program product of claim 16, further including code for encrypting the server information package using a Client Session Public Key.
19. The computer program product of claim 16, wherein the server challenge information package further includes the Server Session Public Key.
20. The computer program product of claim 16, wherein the server challenge information package further includes a previous session ID for enabling the client to select a Server Session Public Key associated with the previous session ID.
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA002438357A CA2438357A1 (en) | 2003-08-26 | 2003-08-26 | System and method for secure remote access |
US10/752,027 US7321971B2 (en) | 2003-08-26 | 2004-01-07 | System and method for secure remote access |
CN 200410032545 CN100568800C (en) | 2003-08-26 | 2004-04-08 | The system and method that is used for safety remote access |
PCT/EP2004/051675 WO2005020041A1 (en) | 2003-08-26 | 2004-07-30 | System and method for secure remote access |
TW93123112A TWI313996B (en) | 2003-08-26 | 2004-08-02 | System and method for secure remote access |
US11/861,740 US8904178B2 (en) | 2003-08-26 | 2007-09-26 | System and method for secure remote access |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA002438357A CA2438357A1 (en) | 2003-08-26 | 2003-08-26 | System and method for secure remote access |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2438357A1 true CA2438357A1 (en) | 2005-02-26 |
Family
ID=34200807
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002438357A Abandoned CA2438357A1 (en) | 2003-08-26 | 2003-08-26 | System and method for secure remote access |
Country Status (5)
Country | Link |
---|---|
US (2) | US7321971B2 (en) |
CN (1) | CN100568800C (en) |
CA (1) | CA2438357A1 (en) |
TW (1) | TWI313996B (en) |
WO (1) | WO2005020041A1 (en) |
Families Citing this family (42)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7370212B2 (en) | 2003-02-25 | 2008-05-06 | Microsoft Corporation | Issuing a publisher use license off-line in a digital rights management (DRM) system |
US7937759B2 (en) * | 2003-10-02 | 2011-05-03 | Auburn University | System and method for protecting communication devices from denial of service attacks |
US7774841B2 (en) * | 2003-10-02 | 2010-08-10 | Aubum University | System and method for protecting network resources from denial of service attacks |
GB0407388D0 (en) * | 2004-03-31 | 2004-05-05 | British Telecomm | Method and apparatus for communicating data between computer devices |
FR2869175B1 (en) * | 2004-04-16 | 2008-04-18 | Audiosmartcard Internat Sa Sa | METHOD FOR SECURING OPERATIONS ON A NETWORK AND ASSOCIATED DEVICES |
US8060923B2 (en) * | 2004-04-23 | 2011-11-15 | Microsoft Corporation | Trusted license removal in a content protection system or the like |
US7757294B1 (en) | 2004-08-27 | 2010-07-13 | Xilinx, Inc. | Method and system for maintaining the security of design information |
US7971072B1 (en) * | 2005-03-10 | 2011-06-28 | Xilinx, Inc. | Secure exchange of IP cores |
US7908480B2 (en) * | 2005-03-21 | 2011-03-15 | Cisco Technology, Inc. | Authenticating an endpoint using a STUN server |
US8438645B2 (en) * | 2005-04-27 | 2013-05-07 | Microsoft Corporation | Secure clock with grace periods |
US7636940B2 (en) * | 2005-04-12 | 2009-12-22 | Seiko Epson Corporation | Private key protection for secure servers |
US8725646B2 (en) | 2005-04-15 | 2014-05-13 | Microsoft Corporation | Output protection levels |
US20060265758A1 (en) | 2005-05-20 | 2006-11-23 | Microsoft Corporation | Extensible media rights |
US8220042B2 (en) | 2005-09-12 | 2012-07-10 | Microsoft Corporation | Creating secure interactive connections with remote resources |
US8938473B2 (en) * | 2006-02-23 | 2015-01-20 | Oracle America, Inc. | Secure windowing for labeled containers |
CN101047698B (en) * | 2006-03-29 | 2010-09-29 | 鸿富锦精密工业(深圳)有限公司 | Remote access protection system and method |
US20070254630A1 (en) * | 2006-04-24 | 2007-11-01 | Nokia Corporation | Methods, devices and modules for secure remote access to home networks |
US20080005115A1 (en) * | 2006-06-30 | 2008-01-03 | International Business Machines Corporation | Methods and apparatus for scoped role-based access control |
US20080077592A1 (en) * | 2006-09-27 | 2008-03-27 | Shane Brodie | method and apparatus for device authentication |
US8412947B2 (en) * | 2006-10-05 | 2013-04-02 | Ceelox Patents, LLC | System and method of secure encryption for electronic data transfer |
US7756116B2 (en) * | 2006-10-10 | 2010-07-13 | Cisco Technology, Inc. | Supplementary services using secure media |
US8285989B2 (en) * | 2006-12-18 | 2012-10-09 | Apple Inc. | Establishing a secured communication session |
US7937586B2 (en) * | 2007-06-29 | 2011-05-03 | Microsoft Corporation | Defending against denial of service attacks |
CN101170554B (en) * | 2007-09-04 | 2012-07-04 | 萨摩亚商·繁星科技有限公司 | Message safety transfer system |
US8806565B2 (en) | 2007-09-12 | 2014-08-12 | Microsoft Corporation | Secure network location awareness |
US8239549B2 (en) * | 2007-09-12 | 2012-08-07 | Microsoft Corporation | Dynamic host configuration protocol |
US8689013B2 (en) * | 2008-10-21 | 2014-04-01 | G. Wouter Habraken | Dual-interface key management |
US8204228B2 (en) * | 2008-12-09 | 2012-06-19 | Cisco Technology, Inc. | Group key management re-registration method |
US8370920B2 (en) * | 2009-10-28 | 2013-02-05 | Aunigma Network Security Corp. | System and method for providing unified transport and security protocols |
US20120030475A1 (en) * | 2010-08-02 | 2012-02-02 | Ma Felix Kuo-We | Machine-machine authentication method and human-machine authentication method for cloud computing |
US8595822B2 (en) * | 2011-12-29 | 2013-11-26 | Mcafee, Inc. | System and method for cloud based scanning for computer vulnerabilities in a network environment |
CN103701919A (en) * | 2013-12-31 | 2014-04-02 | 曙光云计算技术有限公司 | Remote login method and system |
FR3018371B1 (en) * | 2014-03-10 | 2016-05-06 | Commissariat Energie Atomique | REMOTE KEY DATA ENCRYPTION / ENCRYPTION METHOD AND SYSTEM AND PRIOR CHECK CHECK |
EP2937806A1 (en) * | 2014-04-22 | 2015-10-28 | ALSTOM Renewable Technologies | Method and system for securing electronic data exchange between an industrial programmable device and a portable programmable device |
US10021069B1 (en) | 2015-04-02 | 2018-07-10 | Aunigma Network Security Corp. | Real time dynamic client access control |
US10019718B2 (en) | 2015-05-12 | 2018-07-10 | Bank Of America Corporation | Customer-based associate interfaces |
WO2017004466A1 (en) * | 2015-06-30 | 2017-01-05 | Visa International Service Association | Confidential authentication and provisioning |
EP3888292A4 (en) * | 2018-11-29 | 2022-12-28 | Mocana Corporation | System and method for protection of multipart system applications using a cryptographically protected package, a package map and a package object store for decryption and verification at runtime on the target device platform |
WO2020117549A1 (en) | 2018-12-06 | 2020-06-11 | Mocana Corporation | System and method for zero touch provisioning of iot devices |
CN111130799B (en) * | 2019-12-25 | 2022-06-14 | 上海沄界信息科技有限公司 | Method and system for HTTPS protocol transmission based on TEE |
CN111934879B (en) * | 2020-07-08 | 2023-09-12 | 福建亿能达信息技术股份有限公司 | Encryption method, device, equipment and medium for data transmission of internal and external network system |
CN115174229B (en) * | 2022-07-08 | 2024-02-27 | 医利捷(上海)信息科技有限公司 | Service authentication method, system and electronic equipment |
Family Cites Families (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4578531A (en) * | 1982-06-09 | 1986-03-25 | At&T Bell Laboratories | Encryption system key distribution method and apparatus |
US4652698A (en) * | 1984-08-13 | 1987-03-24 | Ncr Corporation | Method and system for providing system security in a remote terminal environment |
GB9104909D0 (en) * | 1991-03-08 | 1991-04-24 | Int Computers Ltd | Access control in a distributed computer system |
US5535276A (en) * | 1994-11-09 | 1996-07-09 | Bell Atlantic Network Services, Inc. | Yaksha, an improved system and method for securing communications using split private key asymmetric cryptography |
US5636280A (en) * | 1994-10-31 | 1997-06-03 | Kelly; Tadhg | Dual key reflexive encryption security system |
KR100473536B1 (en) * | 1996-05-22 | 2005-05-16 | 마츠시타 덴끼 산교 가부시키가이샤 | An encryption apparatus for ensuring security in communication between devices and communication system |
US5784463A (en) * | 1996-12-04 | 1998-07-21 | V-One Corporation | Token distribution, registration, and dynamic configuration of user entitlement for an application level security system and method |
JP3864401B2 (en) * | 1997-04-23 | 2006-12-27 | ソニー株式会社 | Authentication system, electronic device, authentication method, and recording medium |
US6049877A (en) * | 1997-07-16 | 2000-04-11 | International Business Machines Corporation | Systems, methods and computer program products for authorizing common gateway interface application requests |
JPH11122239A (en) | 1997-10-16 | 1999-04-30 | Sony Corp | Information processor, information processing method and transmission medium |
US6098056A (en) * | 1997-11-24 | 2000-08-01 | International Business Machines Corporation | System and method for controlling access rights to and security of digital content in a distributed information system, e.g., Internet |
US6151676A (en) * | 1997-12-24 | 2000-11-21 | Philips Electronics North America Corporation | Administration and utilization of secret fresh random numbers in a networked environment |
US6230269B1 (en) * | 1998-03-04 | 2001-05-08 | Microsoft Corporation | Distributed authentication system and method |
US6233341B1 (en) * | 1998-05-19 | 2001-05-15 | Visto Corporation | System and method for installing and using a temporary certificate at a remote site |
US20020016922A1 (en) * | 2000-02-22 | 2002-02-07 | Richards Kenneth W. | Secure distributing services network system and method thereof |
US7024690B1 (en) * | 2000-04-28 | 2006-04-04 | 3Com Corporation | Protected mutual authentication over an unsecured wireless communication channel |
US7587368B2 (en) * | 2000-07-06 | 2009-09-08 | David Paul Felsher | Information record infrastructure, system and method |
GB0020370D0 (en) | 2000-08-18 | 2000-10-04 | Hewlett Packard Co | Trusted device |
JP4655345B2 (en) * | 2000-08-31 | 2011-03-23 | ソニー株式会社 | Information processing apparatus, information processing method, and program providing medium |
US20030021417A1 (en) * | 2000-10-20 | 2003-01-30 | Ognjen Vasic | Hidden link dynamic key manager for use in computer systems with database structure for storage of encrypted data and method for storage and retrieval of encrypted data |
US7200752B2 (en) * | 2000-11-13 | 2007-04-03 | Thomson Licensing | Threshold cryptography scheme for message authentication systems |
US6954790B2 (en) * | 2000-12-05 | 2005-10-11 | Interactive People Unplugged Ab | Network-based mobile workgroup system |
US6865681B2 (en) * | 2000-12-29 | 2005-03-08 | Nokia Mobile Phones Ltd. | VoIP terminal security module, SIP stack with security manager, system and security methods |
US20020090089A1 (en) * | 2001-01-05 | 2002-07-11 | Steven Branigan | Methods and apparatus for secure wireless networking |
US7222187B2 (en) * | 2001-07-31 | 2007-05-22 | Sun Microsystems, Inc. | Distributed trust mechanism for decentralized networks |
US7389412B2 (en) * | 2001-08-10 | 2008-06-17 | Interactive Technology Limited Of Hk | System and method for secure network roaming |
US7185362B2 (en) * | 2001-08-20 | 2007-02-27 | Qualcomm, Incorporated | Method and apparatus for security in a data processing system |
US20030093680A1 (en) * | 2001-11-13 | 2003-05-15 | International Business Machines Corporation | Methods, apparatus and computer programs performing a mutual challenge-response authentication protocol using operating system capabilities |
US9544297B2 (en) * | 2002-03-08 | 2017-01-10 | Algorithmic Research Ltd. | Method for secured data processing |
US7529933B2 (en) * | 2002-05-30 | 2009-05-05 | Microsoft Corporation | TLS tunneling |
US7203844B1 (en) * | 2002-06-20 | 2007-04-10 | Oxford William V | Method and system for a recursive security protocol for digital copyright control |
-
2003
- 2003-08-26 CA CA002438357A patent/CA2438357A1/en not_active Abandoned
-
2004
- 2004-01-07 US US10/752,027 patent/US7321971B2/en active Active
- 2004-04-08 CN CN 200410032545 patent/CN100568800C/en not_active Expired - Fee Related
- 2004-07-30 WO PCT/EP2004/051675 patent/WO2005020041A1/en active Application Filing
- 2004-08-02 TW TW93123112A patent/TWI313996B/en not_active IP Right Cessation
-
2007
- 2007-09-26 US US11/861,740 patent/US8904178B2/en active Active
Also Published As
Publication number | Publication date |
---|---|
TW200511793A (en) | 2005-03-16 |
TWI313996B (en) | 2009-08-21 |
US20050050329A1 (en) | 2005-03-03 |
US7321971B2 (en) | 2008-01-22 |
US20080016354A1 (en) | 2008-01-17 |
WO2005020041A1 (en) | 2005-03-03 |
US8904178B2 (en) | 2014-12-02 |
CN1592193A (en) | 2005-03-09 |
CN100568800C (en) | 2009-12-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7321971B2 (en) | System and method for secure remote access | |
CN109728909B (en) | Identity authentication method and system based on USBKey | |
JP5978759B2 (en) | Service request apparatus, service providing system, service request method, and service request program | |
US7584505B2 (en) | Inspected secure communication protocol | |
JP4770227B2 (en) | SIP message encryption method and encrypted SIP communication system | |
EP2060055B1 (en) | Destroying a Secure Session maintained by a Server on behalf of a Connection Owner | |
CN111901355B (en) | Authentication method and device | |
CN105119894B (en) | Communication system and communication means based on hardware security module | |
CN111918284B (en) | Safe communication method and system based on safe communication module | |
CN111756528B (en) | Quantum session key distribution method, device and communication architecture | |
JP2007281919A (en) | Communication system on public line for performing access restriction, terminal connection apparatus, and server connection restriction apparatus | |
KR101448866B1 (en) | Security apparatus for decrypting data encrypted according to the web security protocol and operating method thereof | |
WO2009018510A1 (en) | Systems and methods for implementing a mutating internet protocol security | |
CN113904767A (en) | System for establishing communication based on SSL | |
JPH10242957A (en) | User authentication method, system therefor and storage medium for user authentication | |
Sangster et al. | A posture transport protocol over TLS (PT-TLS) | |
Cam-Winget et al. | PT-EAP: Posture Transport (PT) Protocol for Extensible Authentication Protocol (EAP) Tunnel Methods | |
JP4866150B2 (en) | FTP communication system, FTP communication program, FTP client device, and FTP server device | |
CN114584393B (en) | Method for automatically selecting encryption protocol | |
KR101448711B1 (en) | security system and security method through communication encryption | |
CN115348578B (en) | Method and device for tracking contacter | |
KR100744603B1 (en) | Authentification method for packet level user by use of bio data | |
Garimella et al. | Secure Shell-Its significance in Networking (SSH) | |
WO2016124302A1 (en) | User opt-in computer implemented method for monitoring network traffic data, network traffic controller and computer programs | |
CN114531235A (en) | End-to-end encrypted communication method and system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
FZDE | Discontinued | ||
FZDE | Discontinued |
Effective date: 20100826 |