CA2018270A1 - Method for utilizing an encrypted key as a key identifier in a data packet in a computer network - Google Patents
Method for utilizing an encrypted key as a key identifier in a data packet in a computer networkInfo
- Publication number
- CA2018270A1 CA2018270A1 CA002018270A CA2018270A CA2018270A1 CA 2018270 A1 CA2018270 A1 CA 2018270A1 CA 002018270 A CA002018270 A CA 002018270A CA 2018270 A CA2018270 A CA 2018270A CA 2018270 A1 CA2018270 A1 CA 2018270A1
- Authority
- CA
- Canada
- Prior art keywords
- node
- encrypted
- shared key
- key
- data
- 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 description 32
- 238000004891 communication Methods 0.000 claims abstract description 21
- 230000006870 function Effects 0.000 claims description 18
- 230000005540 biological transmission Effects 0.000 claims description 4
- 230000008878 coupling Effects 0.000 claims 11
- 238000010168 coupling process Methods 0.000 claims 11
- 238000005859 coupling reaction Methods 0.000 claims 11
- 238000013478 data encryption standard Methods 0.000 description 16
- 238000004364 calculation method Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 238000012546 transfer Methods 0.000 description 4
- 230000001419 dependent effect Effects 0.000 description 3
- 125000004122 cyclic group Chemical group 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 241000610375 Sparisoma viride Species 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- BCBIDXOBWXECET-UHFFFAOYSA-N n,n-dimethyl-3,3-diphenylcyclopentan-1-amine;hydrochloride Chemical compound Cl.C1C(N(C)C)CCC1(C=1C=CC=CC=1)C1=CC=CC=C1 BCBIDXOBWXECET-UHFFFAOYSA-N 0.000 description 1
- 230000003068 static effect 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/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
- H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
- H04L9/0822—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) using key encryption key
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
- H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
- H04L9/083—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Storage Device Security (AREA)
Abstract
Abstract of the Disclosure The nodes in a computer network utilize an encrypted key as a key identifier in a data packets transferred between nodes which eliminates the need for a receiving node to perform a memory look up operation to ascertain the key used to encrypt the data. Each node is provided with a master key that is unique to each node. When two nodes want to establish communications they first negotiate a shared key. This shared key is then encrypted under each nodes' master key. The nodes then exchange their respective encrypted key. The encrypted key of the receiving node is placed in the data packet to be sent by the transmitting node. Upon receiving a data packet, the receiving node decrypts the encrypted key to determine the shared key. This shared key is then used to decrypt encrypted data in the data packet.
Description
2~8~70 A Method for Utilizing an Encrypted Key as a Key Identifier in a Data Packet in a Computer Network Field of the Invention This invention relates to computer networks and, more particularly, to a system which provides for the encryption and decryption of data transmitted in a computer network.
Backqround of the Invention A computer network consists of a plurality of nodes which are coupled together in some fashion, for example, in a ring, daisy-chained, or clustered network. Such computer networks may involve a small number of users located geographically close to each other or thousands of users located on different continents. A nodt is an, device attached to a network which acts as an originator or recipient of data. Examples of such devices which could be nodes are computers, computer terminals and storage devices.
The ultimate goal of computer networks is to accurately transfer information between tne nodes comprising the network. Some network applications require the maintenance of security measures to insure either, or Expres, ~a~
. . .
', ' .' ': -.
- . . - . - -.. : .. .
2~
both, the con~identiality or integrity of the information transferred between nodes. Typically, such confidentiality is implemented by cryptographically protecting data transferred between nodes using devices implementing a cryptographic algorithm in conjunction with a cryptographic key. As used in this specification, cryptographic processing includes encryption, decryption, and/or checking the integrity of a data packet. The cryptographic key is a parameter which controls both encryption and decryption operations.
Encryption can be used to provide either, or both, confidentiality or integrity for a data transfer operation. Integrity as used in this specification means insuring that the data received at one node is an accurate represenation of the data transmitted from another node. The process of encryption for confidentiality is accomplished by an algorithm with a given key which will scramble data such that only a user who has that same key will be able to descramble the data. In order to ensure the integrity of the data, a similar algorithm is used which uses the data to obtain an integrity check vector which is transmitted along with the original, non-encrypted data and used to verify the data.
A node is coupled to a computer network by an adaptor which is an input/output device which receives data from or transmits data across the network under its own power without the need for intervention by a central processing unit ("CPU"). The adaptor may also perform the cryptographic operations. The adaptor can be a microprocessor-based or a hard-wired logic system. The adaptor monitors the network so that it can properly send or receive data. After receiving or sending data, the adaptor will interrupt the CPU to inform it that such transfer has occurred.
A node may be simultaneously maintaining multiple connections to many remote nodes. Such nodes communicate by exchanging data packets which typically consist of header information and data. Thus, in a network system for example where encryption is occurring, these data packets contain encrypted data and will arrive at the node from other various nodes in an interleaved manner and in an unpredictable order. The header information sets forth which node is the receiving node of the data packet, but each remote node and possibly each connection will have its data encrypted with a different key. Each data packet contains sufficient information for the receiving node to ascertain which key to use to decrypt and/or check the integrity of a data packet. This information may either be implicit, i.e., based upon the source address information, or explicit, i.e., based upon a key identifier placed in the packet. In the prior art, the header is not encrypted so that the data packet can be relayed by intermediaries along the network that do not have the key. Also, the key is not placed in the data packet header since this would allow any user of the network to intercept the data packet and, using the key, decrypt the data. For security purposes, the key must be known only to the nodes communicating with each other.
As a result of these requirements, there is a unique shared key for each communicating pair of nodes n the network and possibly for each connection existing between the communicating pair. In the case where the node's adapter performs the cryptographic functions, each node's adaptor must store all the keys it is currently using in a key table maintained in the node's adaptor memory. When an adaptor receives a data packet :
2~ 82~0 it can decrypt and/or check the integrity of the packet using the appropriate key for the transmitting node.
The required size of the key table memory is proportional to the maximum number of different keys that will be simultaneously active. Thus, for large networks each node's adaptor potentially would have to maintain a very large key table in its memory. This results in a large amount of board space on the adaptor being dedicated to key table memory. To overcome this problem, some known techniques for reducing the size of the key table include encrypting multiple connections under a single key (especially when there are several connections to a single end node), limiting the maximum number of "active" connections, and treating the key table as a key cache and resorting to a less efficient means for cryptographic processing of packets whose keys are not in the cache.
Also, the receiving node in performing the look up operation in its key table does this to find the sending node's key so that it can use that key to decrypt or check the integrity of the data. This look up operation must be performed very quickly so that the cryptographic processing can be done as the data packet arrives. A
common method used to facilitate the look up operation is to have the two nodes exchange an index in the data packet. This index serves as an index into the receiving node's look up table. The index enables the receiving node to locate the sending node's key, thus, enabling the receiving node to decrypt and/or check the received data.
While the prior art provides an adequate method of ascertaining the key of a sending node in order to decrypt a data packet, there is a need for advancement.
In particular, there is a need to minimize the amount of required key s.orage memory in a node while maintaining ~o~
the security of communications between nodes in a computer network.
Summary of the Invention The present invention enables a node in a computer network to either decrypt and/or check the integrity of a received data packet without performing a look up operation in a key table to ascertain the key of a sending node. Thus, the need for key table memory in the adaptor is eliminated. The present invention determines the cryptographic key by a decryption operation instead of a memory look up.
Before two nodes in a computer network can communicate securely, they must agree on a key referred to as a shared key, that will be used to encrypt, decrypt and/or check the integrity of the data transmitted between these nodes. The negotiation of the shared key can either be static, i.e., selected once and remain fixed, or dynamic, i.e., negotiated each time the nodes wants to communicate.
Each node in the network also has a master key that is unique to that node. The master key is used according to the present invention, to encrypt the shared key under the master key of each of the two nodes. This provides each node with an encrypted version of the shared key which is then used as a key identifier in each data packet transmitted between the nodes.
For example, in the course of a session establishment, each node tells the other what its encrypted version of the shared key is and to use this in any data packets communicated between them. ~ach time two nodes communicate, the sending node places the receiving node's encrypted version of the shared key in the data . .
~ ' ~
, - : :
:~ : ~ ' ' ' ' ~' ' ' , ' Z~8~
packet transmitted. The receiving node, upon receiving the data packet ~ill decrypt the transmitted encrypted version of the shared key under its master key and thus obtain the shared key ~hich the receiving node utilizes to process the remainder of the data packet. The receiving node thus needs only storage space for a single key - the master key for this node. Thus, the present invention substitutes a decryption operation for a memory look up.
The present invention also provides for the integrity of communication between two nodes. If the data in tne data packet is encrypted, then a simple error detection scheme is implemented to insure that the received data accurately represents the transmitted data. If, however, the data is not encrypted, the present invention provides an integrity check vector in each data packet. The integrity check vector is calculated pursuant to an encryption algorithm as a function of the data and the shared key. Upon receiving a data packet, the receiving node calculates its own integrity check vector based upon the received data and decrypted shared key. A comparison of the calculated integrity vector and received integrity check vector is performed to insure accurate communications.
Accordingly, the present invention provides two levels of decryption to be performed on a data packet by a receiving node or one level of decryption and one level of integrity checking. In order to do this, ~he receiving node need only decrypt the encrypted key under its master key to ascertain the shared key. Once the shared key is determined, it is then used '3 either decrypt the remainder of the data packet as it is received or verify the integrity of the received data packet. Thus, the need for key table memory resident on the adaptor is eliminated.
', ' ~'' .
8~70 Brief 3escription of the Drawin~s Figure 1 is a block diagram of a portion of a computer network.
Pigure 2 is a block diagram of an adaptor.
Figure 3 illustrates a data packet transmitted by a node in a computer network.
Figure 4 is a block diagram of a preferred embodiment of a computer network.
Figure 5 is a flow diagram illustrating the Data Encryption Standard algorithm.
Detailed Description Referring now to the drawings and initially to Figure 1, there is illustrated, in block diagram form, a simplified system configuration according to the invention. The system comprises a node A 11 and a node B 12. The nodes are coupled to a bus 13 by their respective adaptors 10 and 14. Serial data packets are transmitted between node A 11 to node B 12 across the bus 13.
Referring now to Figure 2, there is illustrated, in block diagram form, an exemplary embodiment of an adaptor 40. The adaptor 40 comprises an adaptor controller 31, a memory controller 32, a cryptographic function 33, a media access controller 34 and a network interface 35. The network interface 35 provides a physical connection to the network. The media access controller 3~ monitors the network for incoming messages and determines when outbound messages can be sent. The cryptographic function 33 encrypts and/or computes an .` ;, ' . ' : :- . : ~:
.
o integrity check vector for outgoing data packets or decrypts and/or checks the integrity of incoming data packets without the key table memory of prior art adaptors. The memory controller 32 is responsible for maintaining pointers to node memory where data packets are stored. The adaptor controller 31 off loads functions from the node's CPU and enhances adaptor's 40 independence.
Referring now to Figure 3, there is illustrated a data packet 15 which ~s transmitted between node A 11 and node B 12. The data packet 15 comprises a datalink header 16, a network header 17, a cryptographic header 18, data 19, an integrity check vector ("ICV") 20 and a datalink checksum 21. The datalink header 16 comprises -approximately fifteen bytes. The information stored in the datalink header 16 depends upon the network configuration in which the data packet is being transmitted, e.g., Ethernet, Tl, etc. The network header 17, comprising approximately sixty bytes, contains information in a format recognized on any network through international standards. The network header 17 contains all the information necessary to get a data packet from a sending node, through a network, to a receiving node. The data 19 contains the data being transmitted. This field may be encrypted for confidentiality. The number of bytes comprising the data depends upon the minimum number of bytes required for the data transfer, e.g., eight bytes, and the number of data bytes which the link can support, e.g., five hundred to four thousand bytes.
The cryptographic header 18 comprises a cryptographic ID
field 22, an algorithm identifier 23, a key identifier 24, and an I~ field 25. The cryptographic ID field 22 comprises one or two bytes and indicates that the following collection of bytes comprises the 2~)182~
g cryptographic header 18. The algorithm identifier 23 comprises one byte which indicates which of a number of standard cryptographic functions should be used to decrypt and/or check the integrity of this data packet and whether integrity and/or confidentiality is provided. A standard for cryptographic functions is the Data Encryption Standard (hereinafter "DES") passed by the National Board of Standards in January, 1977. DES
sets forth a data encryption algorithm for a 64-bit (eight byte) data block using a 64-bit (eight byte) key.
This algorithm is described below.
The two nodes involved in a communication must agree upon the interpretation of the algorithm identifier 23 for it to have any meaning. Most network implementations support only one algorithm, therefore, the algorithm identifier 23 is superfluous. However, the identifier is included in the cryptographic header 18 to avoid future expansion problems because it may be used in the future. For unauthorized user to intercept or modify a message in a network, he must know both the encryption algorithm and the key being used. Since the algorithm identifier 23 does not conform to some international standard, it alone does not divulge the algorithm in use. In any event, a basic philosophy of cryptography is that the security which is provided by the algorithms should not depend upon the secrecy of the algorithm itself.
The key identifier 24, which is typically one or two bytes long, is eight bytes long in the present invention. The IV field 25 which is eight bytes long, deals with the manner that cryptograhic functions work and guarantees that the same message is never sent twice.
The ICV 20, which is four or eight bytes depending upon .
- , .
.
.. , . ~: :
- . , : .
: -, , . : . : ~: .
-20i~ 0 whether the data is encrypted, provides modificationdetection for the data 19. The ICV 20 is used to detect transmission errors as well as prevent unauthorized users from modifying the data 19 without notice to the receiving node.
There are a multitude of methods for calculating the ICV
20. If the data 19 is encrypted, then, for example, a cyclic redundancy check as the ICV 20 is sufficient to provide data integrity. If the data 19 is not encrypted, however, then a cyclic redundancy check for the ICV 20 would be inadequate because potential modifications to the data 19 could be disguised by making corresponding modifications to the ICV 20. Thus, when the data 19 is not encrypted it is necessary to calculate the ICV 20 based upon an encryption algorithm such as the DES algorithm :plained below.
The datalink checksum 21 comprises approximately four bytes and provides error detection for random transmission errors for the entire data packet 15.
Prior to establishing a secure communications link, node A 1' and node B 12 (Figure 1) must aqree on a shared key that they will use in cryptographic processing. To do this, there are several methods of negotiating a shared key. For example, a manual method where a user at node A 11 will select a key, write it down on a piece of paper and hand it to a user at node B 12. The key is then entered by each user into his respective computer.
Thus, when a connection is opened, both node A 11 and node B 12 know the shared key. A major drawback to this method is it is too unwieldy to be implemented for a large, multiuser network.
Referring now to Figure 4, there is illustrated another method for negotiating a key where one node is Z018~
identified as a central trusted node 30. Both node A 11 and node B 12 have a key which they use to securely transmit data packets to the central trusted node 30.
Thus, all packets between node A 11 and node B 12 would be routed through the central trusted node 30. This is an inefficient but secure method of transmitting data between node A 11 and node B 12.
Another approach using the central trusted node 30 as a key distribution center is where when node A 11 wants to securely communicate with node B 12, node A 11 sends a message to the key distribution center 30. The key distribution center 30 generates and distributes a shared key to node A 11 and node B 12. ~ow both nodes have the shared key and can securely communicate directly with each other utilizing the shared key.
The use of a key distribution center 30 implies that the users in the network can trust the key distribution center 30 to not divulge the keys. Another method of negotiating a shared key is to utilize the key distributiôn center 30 to establish the initial contact between node A 11 and node B 12. Once secure communication is established, the two nodes are free to modify the shared key to establish a new shared key without any intervention by the key distribution center 30.
Each node also has a unique master key. In operation, after the shared key is successfully negotiated, the present invention provides for both node A 11 and node B
12 to separately encrypt this shared key under each node's unique master key utilizing an encryption algorithm. The encryption algorithm used could be the same one used ~o encrypt the data. This results ln two distinct versions of the shared key, one at each node.
The nodes 11 and 12 then exchange these encrypted ' ~ ' -- - . . - . -.' : , . - .
~: . . . , . : . ~, 20~1~2~7() versions of the shared key. Then each time a communication is initiated, for example, from node A 11 to node B 12, node A 11 will place in the key identifier field of the data packet 15 an encrypted version of the shared key.
In addition, according to one embodiment of the present invention, if confidentiality of the data is to be maintained, prior to actually transmitting the data packet 15, a node may encrypt the data under the control of the shared key and transmit the encrypted version of the shared key it received from the receiving node and data in a data packet to the receiving node.
To encrypt the data, there are a number of encryption algorithms which could be used. For illustrationl the DES algorithm is explained below.
When a user wishes to send data over the network, the DES algorithm is applied to the data using the correct shared key. The output of the DES algorithm is placed in the data packet 15 in data 19.
The same algorithm can be used to encrypt and decrypt the encrypted version of the shared key. The same steps are followed but instead of having a data block, the data input is the shared key and the key which controls the encryption/decryption is the master key.
At this point, both node A 11 and node B 12 have negotiated a shared key, have encrypted the shared key under their respective master keys, and have exchanged the enc.ypted keys. When a user at node A 11 wishes to communicate with a user at node B 12, the adaptor 10 of node A 1' builds the data packet l5 with the proper header information, inserting node B 12's version of the shared key ~i.e., the shared key encrypted under node -.~ . . .
20iL8~i'0 B's 12 master key) in the cryptographic header 18, and encrypts the data under the control of the shared key.
This data packet 15 is then transmitted to the adaptor 14 of node B 12 where it is received in serial fashion.
The adaptor 14 of node B 12 decrypts the key identifier containing its encrypted version of the shared key under the control of its master key to obtain the shared key.
This shared key is then used to decrypt the next block of the data packet, which is typically data, as it is received.
If the communication between node A 11 and node B 12 are not to be confidential, i.e., the data 19 in the data packet 15 is not encrypted, but integrity is to be provided, the DES algorithm and the shared key can be used to provide data integrity. When a user at node A
11 wishes to communicate with a user at node B 12, the adaptor 10 of node A 11 builds the data packet 15 with the proper header information, inserting node B's 12 encrypted version of the shared key in the cryptographic header 18. The data is placed in the data packet unencrypted. The DES algorithm performs a Cipher Block Chaining ("CBC") mode encryption calculation on the data as described below. The last eight bytes of the output of this algorithm are placed in ICV 20 of the data 2S packet 15. This data packet is then transmitted to the adaptor 14 of node B 12 where it is received in serial fashion. The adaptor 14 of node B 12 decrypts the key identifier containing the encrypted version of the shared key under the control of its master key to obtain the shared key. This shared key is used to apply the CBC mode of DES on the data 1~. The last eight bytes of the output of this calculation are compared with the ICV
20 of the received data packet 15 to determine if correct data has been received.
After the entire data packet is decrypted and/or its .
. ' ', : ' ' , 20:~8-~0 integrity has been checked, the data packet is placed in node B 12's memory where the node B 12 can perform a series of checks to determine which node in the network has sent the data packet and whether the proper shared key was used. These series of checks are performed by a look up operation in a look up table maintained in node memory. As stated above, these look up operations are performed after the cryptographic processing of the data packet. Thus, the present invention has moved the look up table from the adaptor 14 of node B 12 to node B 12's memory. Accordingly, the speed which the adaptor 14 performs the cryptographic processing is increased and more real estate is available on the adaptor 14 for other functions.
This is a description of the DES algorithm which was designed to encrypt and decrypt a block of eight bytes of data using an eight byte key. The decryption is done utilizing the same key as for encryption, but with an altered schedule of addressing the key bits so that the decryption process is the reverse of the encryption process. A data block to be encrypted is subjected to an initial permutation IP, then to a complex key-dependent computation and finally to a permutation which is the inverse of the initial permutation IP 1. The key-dependent computation is defined in terms of an encryption function f, and a key schedule function KS.
Certain notations must be defined to illustrate the data encryption algorithm. Given two blocks L and R of bits, LR denotes the block consisting of the bits of L
followed by the bits of R. The block of bits in LR are denoted as Bl, B2, ... B8, where the block consists of bits of 91 followed by B2 ... followed by B8.
The eight byte data block is first subjected to the initial permutation, IP which results in a permuted 2~8~'7~
input where bit 58 is its first bit, bit 50 is the second bit, and so on with bit 7 as the last bit.
IP
61 53 45 3729 21 ~3 5 The permuted input block is then input to a complex key-dependent computation set forth in Pisure 5 which produces an output referred to as a preoutput. The preoutput is then subjected to the inverse permutation set forth below to produce the encrypted data. The decrypted data bit locations are defined in the same manner as the permuted input block.
Ip_ ~ .
:
,' ., - : . -: . -. -,.
Z0~.8~
37 5 45 13 s3 21 61 29 The computation which uses the permuted input block as its input to produce the preoutput block consists primar ~ of 16 iterations of a calculation de~cribed below. The calculation is described in terms of the encryption function f, which operates on a data block of 32 bits and a data block of 48 bits, and produces a block of 32 bits.
Let the 64 bits of the input block to an iteration consist of a 32 bit block L followed by a 32 bit block R. Using the notations defined above, the input block is then LR. K is defined to be a block of 48 bits chosen from the 64 bit key. The output L'R' of an iteration with input LR is set forth below where +
denotes bit-by-bit modulo 2 addition.
L' = R (1) R' = L + f(RlR) ~he input to the first iteration of the calculation is the permuted input block as set forth in Figure 5.
Since L'R' is the output of the sixteenth iteration, the R'L' is the preoutput block. As shown in Figure 5, a different block of key bits K from the 64 bit key is utilized at each iteration in the calculation.
, . . -~
. . . . . . -:
21~:L82~
The key schedule, KS, is defined as a function which takes an integer n in the range from one to sixteen and eight byte block key as an input and yields a 48 bit block Kn output. This output is a permuted selection of bits from the key defined as follows with Kn determined by the bits in 48 distinct bit positions of KEY.
Kn = KS(n,KEY) (2) KS is called the key schedule because the block K used in the nth iteration of equation one is the block Kn set forth above.
Finally, Lo and Ro are chosen to be L and R, and Ln and Rn are chosen to be L' and R' of equation one when L and R are Ln_l and Rn 1 and K is Kn. When these variables are defined in this manner and n is in the range from one to sixteen, then the conditions set forth below exist.
Ln Rn-1 (3) Rn = Ln_1 + f(Rn-1~ Kn) The preoutput block is then defined by R16L16.
To decrypt the encrypted output of the above calculation, it is necessary to apply the same algorithm to the encrypted data block insuring that the same block of key bits K is used during decryption at each iteration of the computation as was used during data encryption. This can be expressed by the following equation where R,6L16 is now the permuted input block and LoRo is the preoutput block.
Rn-l Ln (4) ,, . - : .
. .: ,. : - ::: ... : . .
: , : . - . .
, : . . .. . , . . -. . : . - . . :
.. .
;~018~7~:) Ln 1 = Rn + F(Ln' Kn) For a more detailed explanation of the above algorithm as well as various possible modes of operation utilizing the algorithm, reference should be made to National Bureau of Standards publications FIPS PUB 46 entitled "Specification for the Data Encryption Standard" and particularly, Appendix D of FIPS PUB 112 entitled "Password Usage" which sets forth a FORTRAN program implementing the DES algorithm for password encryption.
The previous description demonstrates a method for encrypting and decrypting one eight byte block using the DES algorithm. To encrypt/decrypt larger groups of data it is necessary to using a chaining mode of DES such as Cipher Block Chaining ("CBC"). Using this mode, it is possible to encrypt/decrypt arbitrarily long groups of data. For a more detailed explanation of CBC, reference should be made to National Bureau of Standard publication FIPS PUB 81 entitled "DES Modes of Operation".
The above described exemplary embodiment of the invention is meant to be representative only, as certain changes may be made therein without departing from the clear teachings of the invention. Accordingly, reference should be made to the following claims which ~5 alone define the invention.
:.
- - :
. ~ , . . .
., . . .. ~ . .
Backqround of the Invention A computer network consists of a plurality of nodes which are coupled together in some fashion, for example, in a ring, daisy-chained, or clustered network. Such computer networks may involve a small number of users located geographically close to each other or thousands of users located on different continents. A nodt is an, device attached to a network which acts as an originator or recipient of data. Examples of such devices which could be nodes are computers, computer terminals and storage devices.
The ultimate goal of computer networks is to accurately transfer information between tne nodes comprising the network. Some network applications require the maintenance of security measures to insure either, or Expres, ~a~
. . .
', ' .' ': -.
- . . - . - -.. : .. .
2~
both, the con~identiality or integrity of the information transferred between nodes. Typically, such confidentiality is implemented by cryptographically protecting data transferred between nodes using devices implementing a cryptographic algorithm in conjunction with a cryptographic key. As used in this specification, cryptographic processing includes encryption, decryption, and/or checking the integrity of a data packet. The cryptographic key is a parameter which controls both encryption and decryption operations.
Encryption can be used to provide either, or both, confidentiality or integrity for a data transfer operation. Integrity as used in this specification means insuring that the data received at one node is an accurate represenation of the data transmitted from another node. The process of encryption for confidentiality is accomplished by an algorithm with a given key which will scramble data such that only a user who has that same key will be able to descramble the data. In order to ensure the integrity of the data, a similar algorithm is used which uses the data to obtain an integrity check vector which is transmitted along with the original, non-encrypted data and used to verify the data.
A node is coupled to a computer network by an adaptor which is an input/output device which receives data from or transmits data across the network under its own power without the need for intervention by a central processing unit ("CPU"). The adaptor may also perform the cryptographic operations. The adaptor can be a microprocessor-based or a hard-wired logic system. The adaptor monitors the network so that it can properly send or receive data. After receiving or sending data, the adaptor will interrupt the CPU to inform it that such transfer has occurred.
A node may be simultaneously maintaining multiple connections to many remote nodes. Such nodes communicate by exchanging data packets which typically consist of header information and data. Thus, in a network system for example where encryption is occurring, these data packets contain encrypted data and will arrive at the node from other various nodes in an interleaved manner and in an unpredictable order. The header information sets forth which node is the receiving node of the data packet, but each remote node and possibly each connection will have its data encrypted with a different key. Each data packet contains sufficient information for the receiving node to ascertain which key to use to decrypt and/or check the integrity of a data packet. This information may either be implicit, i.e., based upon the source address information, or explicit, i.e., based upon a key identifier placed in the packet. In the prior art, the header is not encrypted so that the data packet can be relayed by intermediaries along the network that do not have the key. Also, the key is not placed in the data packet header since this would allow any user of the network to intercept the data packet and, using the key, decrypt the data. For security purposes, the key must be known only to the nodes communicating with each other.
As a result of these requirements, there is a unique shared key for each communicating pair of nodes n the network and possibly for each connection existing between the communicating pair. In the case where the node's adapter performs the cryptographic functions, each node's adaptor must store all the keys it is currently using in a key table maintained in the node's adaptor memory. When an adaptor receives a data packet :
2~ 82~0 it can decrypt and/or check the integrity of the packet using the appropriate key for the transmitting node.
The required size of the key table memory is proportional to the maximum number of different keys that will be simultaneously active. Thus, for large networks each node's adaptor potentially would have to maintain a very large key table in its memory. This results in a large amount of board space on the adaptor being dedicated to key table memory. To overcome this problem, some known techniques for reducing the size of the key table include encrypting multiple connections under a single key (especially when there are several connections to a single end node), limiting the maximum number of "active" connections, and treating the key table as a key cache and resorting to a less efficient means for cryptographic processing of packets whose keys are not in the cache.
Also, the receiving node in performing the look up operation in its key table does this to find the sending node's key so that it can use that key to decrypt or check the integrity of the data. This look up operation must be performed very quickly so that the cryptographic processing can be done as the data packet arrives. A
common method used to facilitate the look up operation is to have the two nodes exchange an index in the data packet. This index serves as an index into the receiving node's look up table. The index enables the receiving node to locate the sending node's key, thus, enabling the receiving node to decrypt and/or check the received data.
While the prior art provides an adequate method of ascertaining the key of a sending node in order to decrypt a data packet, there is a need for advancement.
In particular, there is a need to minimize the amount of required key s.orage memory in a node while maintaining ~o~
the security of communications between nodes in a computer network.
Summary of the Invention The present invention enables a node in a computer network to either decrypt and/or check the integrity of a received data packet without performing a look up operation in a key table to ascertain the key of a sending node. Thus, the need for key table memory in the adaptor is eliminated. The present invention determines the cryptographic key by a decryption operation instead of a memory look up.
Before two nodes in a computer network can communicate securely, they must agree on a key referred to as a shared key, that will be used to encrypt, decrypt and/or check the integrity of the data transmitted between these nodes. The negotiation of the shared key can either be static, i.e., selected once and remain fixed, or dynamic, i.e., negotiated each time the nodes wants to communicate.
Each node in the network also has a master key that is unique to that node. The master key is used according to the present invention, to encrypt the shared key under the master key of each of the two nodes. This provides each node with an encrypted version of the shared key which is then used as a key identifier in each data packet transmitted between the nodes.
For example, in the course of a session establishment, each node tells the other what its encrypted version of the shared key is and to use this in any data packets communicated between them. ~ach time two nodes communicate, the sending node places the receiving node's encrypted version of the shared key in the data . .
~ ' ~
, - : :
:~ : ~ ' ' ' ' ~' ' ' , ' Z~8~
packet transmitted. The receiving node, upon receiving the data packet ~ill decrypt the transmitted encrypted version of the shared key under its master key and thus obtain the shared key ~hich the receiving node utilizes to process the remainder of the data packet. The receiving node thus needs only storage space for a single key - the master key for this node. Thus, the present invention substitutes a decryption operation for a memory look up.
The present invention also provides for the integrity of communication between two nodes. If the data in tne data packet is encrypted, then a simple error detection scheme is implemented to insure that the received data accurately represents the transmitted data. If, however, the data is not encrypted, the present invention provides an integrity check vector in each data packet. The integrity check vector is calculated pursuant to an encryption algorithm as a function of the data and the shared key. Upon receiving a data packet, the receiving node calculates its own integrity check vector based upon the received data and decrypted shared key. A comparison of the calculated integrity vector and received integrity check vector is performed to insure accurate communications.
Accordingly, the present invention provides two levels of decryption to be performed on a data packet by a receiving node or one level of decryption and one level of integrity checking. In order to do this, ~he receiving node need only decrypt the encrypted key under its master key to ascertain the shared key. Once the shared key is determined, it is then used '3 either decrypt the remainder of the data packet as it is received or verify the integrity of the received data packet. Thus, the need for key table memory resident on the adaptor is eliminated.
', ' ~'' .
8~70 Brief 3escription of the Drawin~s Figure 1 is a block diagram of a portion of a computer network.
Pigure 2 is a block diagram of an adaptor.
Figure 3 illustrates a data packet transmitted by a node in a computer network.
Figure 4 is a block diagram of a preferred embodiment of a computer network.
Figure 5 is a flow diagram illustrating the Data Encryption Standard algorithm.
Detailed Description Referring now to the drawings and initially to Figure 1, there is illustrated, in block diagram form, a simplified system configuration according to the invention. The system comprises a node A 11 and a node B 12. The nodes are coupled to a bus 13 by their respective adaptors 10 and 14. Serial data packets are transmitted between node A 11 to node B 12 across the bus 13.
Referring now to Figure 2, there is illustrated, in block diagram form, an exemplary embodiment of an adaptor 40. The adaptor 40 comprises an adaptor controller 31, a memory controller 32, a cryptographic function 33, a media access controller 34 and a network interface 35. The network interface 35 provides a physical connection to the network. The media access controller 3~ monitors the network for incoming messages and determines when outbound messages can be sent. The cryptographic function 33 encrypts and/or computes an .` ;, ' . ' : :- . : ~:
.
o integrity check vector for outgoing data packets or decrypts and/or checks the integrity of incoming data packets without the key table memory of prior art adaptors. The memory controller 32 is responsible for maintaining pointers to node memory where data packets are stored. The adaptor controller 31 off loads functions from the node's CPU and enhances adaptor's 40 independence.
Referring now to Figure 3, there is illustrated a data packet 15 which ~s transmitted between node A 11 and node B 12. The data packet 15 comprises a datalink header 16, a network header 17, a cryptographic header 18, data 19, an integrity check vector ("ICV") 20 and a datalink checksum 21. The datalink header 16 comprises -approximately fifteen bytes. The information stored in the datalink header 16 depends upon the network configuration in which the data packet is being transmitted, e.g., Ethernet, Tl, etc. The network header 17, comprising approximately sixty bytes, contains information in a format recognized on any network through international standards. The network header 17 contains all the information necessary to get a data packet from a sending node, through a network, to a receiving node. The data 19 contains the data being transmitted. This field may be encrypted for confidentiality. The number of bytes comprising the data depends upon the minimum number of bytes required for the data transfer, e.g., eight bytes, and the number of data bytes which the link can support, e.g., five hundred to four thousand bytes.
The cryptographic header 18 comprises a cryptographic ID
field 22, an algorithm identifier 23, a key identifier 24, and an I~ field 25. The cryptographic ID field 22 comprises one or two bytes and indicates that the following collection of bytes comprises the 2~)182~
g cryptographic header 18. The algorithm identifier 23 comprises one byte which indicates which of a number of standard cryptographic functions should be used to decrypt and/or check the integrity of this data packet and whether integrity and/or confidentiality is provided. A standard for cryptographic functions is the Data Encryption Standard (hereinafter "DES") passed by the National Board of Standards in January, 1977. DES
sets forth a data encryption algorithm for a 64-bit (eight byte) data block using a 64-bit (eight byte) key.
This algorithm is described below.
The two nodes involved in a communication must agree upon the interpretation of the algorithm identifier 23 for it to have any meaning. Most network implementations support only one algorithm, therefore, the algorithm identifier 23 is superfluous. However, the identifier is included in the cryptographic header 18 to avoid future expansion problems because it may be used in the future. For unauthorized user to intercept or modify a message in a network, he must know both the encryption algorithm and the key being used. Since the algorithm identifier 23 does not conform to some international standard, it alone does not divulge the algorithm in use. In any event, a basic philosophy of cryptography is that the security which is provided by the algorithms should not depend upon the secrecy of the algorithm itself.
The key identifier 24, which is typically one or two bytes long, is eight bytes long in the present invention. The IV field 25 which is eight bytes long, deals with the manner that cryptograhic functions work and guarantees that the same message is never sent twice.
The ICV 20, which is four or eight bytes depending upon .
- , .
.
.. , . ~: :
- . , : .
: -, , . : . : ~: .
-20i~ 0 whether the data is encrypted, provides modificationdetection for the data 19. The ICV 20 is used to detect transmission errors as well as prevent unauthorized users from modifying the data 19 without notice to the receiving node.
There are a multitude of methods for calculating the ICV
20. If the data 19 is encrypted, then, for example, a cyclic redundancy check as the ICV 20 is sufficient to provide data integrity. If the data 19 is not encrypted, however, then a cyclic redundancy check for the ICV 20 would be inadequate because potential modifications to the data 19 could be disguised by making corresponding modifications to the ICV 20. Thus, when the data 19 is not encrypted it is necessary to calculate the ICV 20 based upon an encryption algorithm such as the DES algorithm :plained below.
The datalink checksum 21 comprises approximately four bytes and provides error detection for random transmission errors for the entire data packet 15.
Prior to establishing a secure communications link, node A 1' and node B 12 (Figure 1) must aqree on a shared key that they will use in cryptographic processing. To do this, there are several methods of negotiating a shared key. For example, a manual method where a user at node A 11 will select a key, write it down on a piece of paper and hand it to a user at node B 12. The key is then entered by each user into his respective computer.
Thus, when a connection is opened, both node A 11 and node B 12 know the shared key. A major drawback to this method is it is too unwieldy to be implemented for a large, multiuser network.
Referring now to Figure 4, there is illustrated another method for negotiating a key where one node is Z018~
identified as a central trusted node 30. Both node A 11 and node B 12 have a key which they use to securely transmit data packets to the central trusted node 30.
Thus, all packets between node A 11 and node B 12 would be routed through the central trusted node 30. This is an inefficient but secure method of transmitting data between node A 11 and node B 12.
Another approach using the central trusted node 30 as a key distribution center is where when node A 11 wants to securely communicate with node B 12, node A 11 sends a message to the key distribution center 30. The key distribution center 30 generates and distributes a shared key to node A 11 and node B 12. ~ow both nodes have the shared key and can securely communicate directly with each other utilizing the shared key.
The use of a key distribution center 30 implies that the users in the network can trust the key distribution center 30 to not divulge the keys. Another method of negotiating a shared key is to utilize the key distributiôn center 30 to establish the initial contact between node A 11 and node B 12. Once secure communication is established, the two nodes are free to modify the shared key to establish a new shared key without any intervention by the key distribution center 30.
Each node also has a unique master key. In operation, after the shared key is successfully negotiated, the present invention provides for both node A 11 and node B
12 to separately encrypt this shared key under each node's unique master key utilizing an encryption algorithm. The encryption algorithm used could be the same one used ~o encrypt the data. This results ln two distinct versions of the shared key, one at each node.
The nodes 11 and 12 then exchange these encrypted ' ~ ' -- - . . - . -.' : , . - .
~: . . . , . : . ~, 20~1~2~7() versions of the shared key. Then each time a communication is initiated, for example, from node A 11 to node B 12, node A 11 will place in the key identifier field of the data packet 15 an encrypted version of the shared key.
In addition, according to one embodiment of the present invention, if confidentiality of the data is to be maintained, prior to actually transmitting the data packet 15, a node may encrypt the data under the control of the shared key and transmit the encrypted version of the shared key it received from the receiving node and data in a data packet to the receiving node.
To encrypt the data, there are a number of encryption algorithms which could be used. For illustrationl the DES algorithm is explained below.
When a user wishes to send data over the network, the DES algorithm is applied to the data using the correct shared key. The output of the DES algorithm is placed in the data packet 15 in data 19.
The same algorithm can be used to encrypt and decrypt the encrypted version of the shared key. The same steps are followed but instead of having a data block, the data input is the shared key and the key which controls the encryption/decryption is the master key.
At this point, both node A 11 and node B 12 have negotiated a shared key, have encrypted the shared key under their respective master keys, and have exchanged the enc.ypted keys. When a user at node A 11 wishes to communicate with a user at node B 12, the adaptor 10 of node A 1' builds the data packet l5 with the proper header information, inserting node B 12's version of the shared key ~i.e., the shared key encrypted under node -.~ . . .
20iL8~i'0 B's 12 master key) in the cryptographic header 18, and encrypts the data under the control of the shared key.
This data packet 15 is then transmitted to the adaptor 14 of node B 12 where it is received in serial fashion.
The adaptor 14 of node B 12 decrypts the key identifier containing its encrypted version of the shared key under the control of its master key to obtain the shared key.
This shared key is then used to decrypt the next block of the data packet, which is typically data, as it is received.
If the communication between node A 11 and node B 12 are not to be confidential, i.e., the data 19 in the data packet 15 is not encrypted, but integrity is to be provided, the DES algorithm and the shared key can be used to provide data integrity. When a user at node A
11 wishes to communicate with a user at node B 12, the adaptor 10 of node A 11 builds the data packet 15 with the proper header information, inserting node B's 12 encrypted version of the shared key in the cryptographic header 18. The data is placed in the data packet unencrypted. The DES algorithm performs a Cipher Block Chaining ("CBC") mode encryption calculation on the data as described below. The last eight bytes of the output of this algorithm are placed in ICV 20 of the data 2S packet 15. This data packet is then transmitted to the adaptor 14 of node B 12 where it is received in serial fashion. The adaptor 14 of node B 12 decrypts the key identifier containing the encrypted version of the shared key under the control of its master key to obtain the shared key. This shared key is used to apply the CBC mode of DES on the data 1~. The last eight bytes of the output of this calculation are compared with the ICV
20 of the received data packet 15 to determine if correct data has been received.
After the entire data packet is decrypted and/or its .
. ' ', : ' ' , 20:~8-~0 integrity has been checked, the data packet is placed in node B 12's memory where the node B 12 can perform a series of checks to determine which node in the network has sent the data packet and whether the proper shared key was used. These series of checks are performed by a look up operation in a look up table maintained in node memory. As stated above, these look up operations are performed after the cryptographic processing of the data packet. Thus, the present invention has moved the look up table from the adaptor 14 of node B 12 to node B 12's memory. Accordingly, the speed which the adaptor 14 performs the cryptographic processing is increased and more real estate is available on the adaptor 14 for other functions.
This is a description of the DES algorithm which was designed to encrypt and decrypt a block of eight bytes of data using an eight byte key. The decryption is done utilizing the same key as for encryption, but with an altered schedule of addressing the key bits so that the decryption process is the reverse of the encryption process. A data block to be encrypted is subjected to an initial permutation IP, then to a complex key-dependent computation and finally to a permutation which is the inverse of the initial permutation IP 1. The key-dependent computation is defined in terms of an encryption function f, and a key schedule function KS.
Certain notations must be defined to illustrate the data encryption algorithm. Given two blocks L and R of bits, LR denotes the block consisting of the bits of L
followed by the bits of R. The block of bits in LR are denoted as Bl, B2, ... B8, where the block consists of bits of 91 followed by B2 ... followed by B8.
The eight byte data block is first subjected to the initial permutation, IP which results in a permuted 2~8~'7~
input where bit 58 is its first bit, bit 50 is the second bit, and so on with bit 7 as the last bit.
IP
61 53 45 3729 21 ~3 5 The permuted input block is then input to a complex key-dependent computation set forth in Pisure 5 which produces an output referred to as a preoutput. The preoutput is then subjected to the inverse permutation set forth below to produce the encrypted data. The decrypted data bit locations are defined in the same manner as the permuted input block.
Ip_ ~ .
:
,' ., - : . -: . -. -,.
Z0~.8~
37 5 45 13 s3 21 61 29 The computation which uses the permuted input block as its input to produce the preoutput block consists primar ~ of 16 iterations of a calculation de~cribed below. The calculation is described in terms of the encryption function f, which operates on a data block of 32 bits and a data block of 48 bits, and produces a block of 32 bits.
Let the 64 bits of the input block to an iteration consist of a 32 bit block L followed by a 32 bit block R. Using the notations defined above, the input block is then LR. K is defined to be a block of 48 bits chosen from the 64 bit key. The output L'R' of an iteration with input LR is set forth below where +
denotes bit-by-bit modulo 2 addition.
L' = R (1) R' = L + f(RlR) ~he input to the first iteration of the calculation is the permuted input block as set forth in Figure 5.
Since L'R' is the output of the sixteenth iteration, the R'L' is the preoutput block. As shown in Figure 5, a different block of key bits K from the 64 bit key is utilized at each iteration in the calculation.
, . . -~
. . . . . . -:
21~:L82~
The key schedule, KS, is defined as a function which takes an integer n in the range from one to sixteen and eight byte block key as an input and yields a 48 bit block Kn output. This output is a permuted selection of bits from the key defined as follows with Kn determined by the bits in 48 distinct bit positions of KEY.
Kn = KS(n,KEY) (2) KS is called the key schedule because the block K used in the nth iteration of equation one is the block Kn set forth above.
Finally, Lo and Ro are chosen to be L and R, and Ln and Rn are chosen to be L' and R' of equation one when L and R are Ln_l and Rn 1 and K is Kn. When these variables are defined in this manner and n is in the range from one to sixteen, then the conditions set forth below exist.
Ln Rn-1 (3) Rn = Ln_1 + f(Rn-1~ Kn) The preoutput block is then defined by R16L16.
To decrypt the encrypted output of the above calculation, it is necessary to apply the same algorithm to the encrypted data block insuring that the same block of key bits K is used during decryption at each iteration of the computation as was used during data encryption. This can be expressed by the following equation where R,6L16 is now the permuted input block and LoRo is the preoutput block.
Rn-l Ln (4) ,, . - : .
. .: ,. : - ::: ... : . .
: , : . - . .
, : . . .. . , . . -. . : . - . . :
.. .
;~018~7~:) Ln 1 = Rn + F(Ln' Kn) For a more detailed explanation of the above algorithm as well as various possible modes of operation utilizing the algorithm, reference should be made to National Bureau of Standards publications FIPS PUB 46 entitled "Specification for the Data Encryption Standard" and particularly, Appendix D of FIPS PUB 112 entitled "Password Usage" which sets forth a FORTRAN program implementing the DES algorithm for password encryption.
The previous description demonstrates a method for encrypting and decrypting one eight byte block using the DES algorithm. To encrypt/decrypt larger groups of data it is necessary to using a chaining mode of DES such as Cipher Block Chaining ("CBC"). Using this mode, it is possible to encrypt/decrypt arbitrarily long groups of data. For a more detailed explanation of CBC, reference should be made to National Bureau of Standard publication FIPS PUB 81 entitled "DES Modes of Operation".
The above described exemplary embodiment of the invention is meant to be representative only, as certain changes may be made therein without departing from the clear teachings of the invention. Accordingly, reference should be made to the following claims which ~5 alone define the invention.
:.
- - :
. ~ , . . .
., . . .. ~ . .
Claims (22)
1. A method for establishing secure communications between a first node and a second node in a network, comprising the steps of:
(a) coupling the first node to the second node, the second node having a master key that is unique to that node and known only by the second node, both nodes having a shared key;
(b) encrypting the shared key at the second node under the control of the master key of the second node to form an encrypted version of the shared key; and (c) transmitting the encrypted version of the shared key from the second node to the first node so that the encrypted version of the shared key can be incorporated by the first node into the encrypted data packets transmitted to the second node and used by the second node to decrypt data in transmitted encrypted data packets to establish secure communication between the first node and the second node.
(a) coupling the first node to the second node, the second node having a master key that is unique to that node and known only by the second node, both nodes having a shared key;
(b) encrypting the shared key at the second node under the control of the master key of the second node to form an encrypted version of the shared key; and (c) transmitting the encrypted version of the shared key from the second node to the first node so that the encrypted version of the shared key can be incorporated by the first node into the encrypted data packets transmitted to the second node and used by the second node to decrypt data in transmitted encrypted data packets to establish secure communication between the first node and the second node.
2. A method for building a data packet in a network, comprising the steps of:
(a) coupling a first node to a second node, the second node having a master key that is unique to that node and known only by the second node, both nodes having a shared key, the first node including a memory;
(b) transmitting from the second node to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node;
(c) creating a data packet in the memory of the first node by:
(i) placing header information in the data packet, (ii) placing the encrypted version of the shared key received from the second node in the data packet, and (iii) placing encrypted data in the data packet.
(a) coupling a first node to a second node, the second node having a master key that is unique to that node and known only by the second node, both nodes having a shared key, the first node including a memory;
(b) transmitting from the second node to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node;
(c) creating a data packet in the memory of the first node by:
(i) placing header information in the data packet, (ii) placing the encrypted version of the shared key received from the second node in the data packet, and (iii) placing encrypted data in the data packet.
3. A method for establishing secure communications between a first node and a second node in a network, comprising the steps of:
(a) coupling the first node to the second node, the second node having a master key that is unique to that node and known only by the second node, both nodes having a shared key;
(b) transmitting from the second node to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node so that the encrypted version of the shared key can be incorporated by the first node into encrypted data packets transmitted to the second node and used by the second node to decrypt data in transmitted encrypted data packets to establish secure communications between the first node and the second node; and (c) transmitting from the first node to the second node an encrypted data packet including the encrypted version of the shared key and data encrypted under the shared key.
(a) coupling the first node to the second node, the second node having a master key that is unique to that node and known only by the second node, both nodes having a shared key;
(b) transmitting from the second node to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node so that the encrypted version of the shared key can be incorporated by the first node into encrypted data packets transmitted to the second node and used by the second node to decrypt data in transmitted encrypted data packets to establish secure communications between the first node and the second node; and (c) transmitting from the first node to the second node an encrypted data packet including the encrypted version of the shared key and data encrypted under the shared key.
4. A method for establishing secure communications between a first node and a second node in a network, comprising the steps of:
(a) coupling the first node to the second node, the second node having a master key that is unique to that node and known only by the second node, both nodes having a shared key;
(b) transmitting from the second node to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node so that the encrypted version of the shared key can be incorporated by the first node into encrypted data packets transmitted to the second node and used by the second node to decrypt data in transmitted encrypted data packets to establish secure communications between the first node and the second node;
(c) building an encrypted data packet in the first node incorporating the encrypted version of the shared key and data encrypted under the shared key; and (d) transmitting from the first node to the second node the encrypted data packet including the encrypted version of the shared key encrypted under the control of the master key of the second node and data encrypted under the shared key.
(a) coupling the first node to the second node, the second node having a master key that is unique to that node and known only by the second node, both nodes having a shared key;
(b) transmitting from the second node to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node so that the encrypted version of the shared key can be incorporated by the first node into encrypted data packets transmitted to the second node and used by the second node to decrypt data in transmitted encrypted data packets to establish secure communications between the first node and the second node;
(c) building an encrypted data packet in the first node incorporating the encrypted version of the shared key and data encrypted under the shared key; and (d) transmitting from the first node to the second node the encrypted data packet including the encrypted version of the shared key encrypted under the control of the master key of the second node and data encrypted under the shared key.
5. A method for transmitting and decrypting a data packet in a network, comprising the steps of:
(a) coupling a first node to a second node, the second node having a master key that is unique to that node and known only by the second node, both nodes having a shared key;
(b) transmitting from the second node to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node;
(c) transmitting from the first node to the second node an encrypted data packet including the encrypted version of the shared key and data encrypted under the shared key;
(d) decrypting the encrypted version of the shared key at the second node under the control of the master key of the second node to obtain the shared key; and (e) decrypting the data at the second node under the control of the shared key.
(a) coupling a first node to a second node, the second node having a master key that is unique to that node and known only by the second node, both nodes having a shared key;
(b) transmitting from the second node to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node;
(c) transmitting from the first node to the second node an encrypted data packet including the encrypted version of the shared key and data encrypted under the shared key;
(d) decrypting the encrypted version of the shared key at the second node under the control of the master key of the second node to obtain the shared key; and (e) decrypting the data at the second node under the control of the shared key.
6. A method for secure transmission of a data packet in a network comprising the steps of:
(a) coupling a first node to a second node, the second node having a master key that is unique to that node and known only by the second node, both nodes having a shared key;
(b) encrypting the shared key at the second node under the control of the master key of the second node to form an encrypted version of the shared key;
(c) transmitting the encrypted version of the shared key from the second node to the first node;
(d) encrypting data under the control of the shared key at the first node;
(e) building an encrypted data packet incorporating the encrypted version of the shard key received from the second node and data encrypted under the control of the shared key;
(f) transmitting the encrypted data packet from the first node to the second node;
(g) decrypting the encrypted version of the shared key at the second node under the control of the second node's master key to obtain the shared key: and (b) decrypting the data at the second node under the control of the shared key.
(a) coupling a first node to a second node, the second node having a master key that is unique to that node and known only by the second node, both nodes having a shared key;
(b) encrypting the shared key at the second node under the control of the master key of the second node to form an encrypted version of the shared key;
(c) transmitting the encrypted version of the shared key from the second node to the first node;
(d) encrypting data under the control of the shared key at the first node;
(e) building an encrypted data packet incorporating the encrypted version of the shard key received from the second node and data encrypted under the control of the shared key;
(f) transmitting the encrypted data packet from the first node to the second node;
(g) decrypting the encrypted version of the shared key at the second node under the control of the second node's master key to obtain the shared key: and (b) decrypting the data at the second node under the control of the shared key.
7. The method of any one of claims 3, 4, 5 and 6 wherein the step of transmitting the encrypted data packet is done serially.
8. The method of any one of claims 3, 4, 5 and 6 wherein the first node has a master key to provide for two-way encrypted communications.
9. A network comprising:
at least a first and a second node, each node having a master key known only to that node, both nodes having a shared key, the nodes being coupled to form a network;
the second node adapted to transmit to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node;
the first node adapted to transmit an encrypted data packet including the encrypted version of the shared key and encrypted data encrypted under the control of the shared key;
a decrypter coupled to the second node, comprising, an input device adapted to receive the encrypted data packet;
a storage device coupled to the input device adapted to store the master key of the second node;
a decryption device coupled to the input device and the storage device, adapted to decrypt the encrypted version of the shared key under the control of the master key and decrypt the encrypted data under the control of the shared key.
at least a first and a second node, each node having a master key known only to that node, both nodes having a shared key, the nodes being coupled to form a network;
the second node adapted to transmit to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node;
the first node adapted to transmit an encrypted data packet including the encrypted version of the shared key and encrypted data encrypted under the control of the shared key;
a decrypter coupled to the second node, comprising, an input device adapted to receive the encrypted data packet;
a storage device coupled to the input device adapted to store the master key of the second node;
a decryption device coupled to the input device and the storage device, adapted to decrypt the encrypted version of the shared key under the control of the master key and decrypt the encrypted data under the control of the shared key.
10. A network comprising:
at least a first and a second node, each node having a master key known only to that node, both nodes having a shared key, the nodes being coupled to form a network;
an encrypter coupled to the first node comprising:
an input device adapted to receive from the second node an encrypted version of the shared key encrypted under the control of a master key known only by the second node;
a storage device coupled to the input device, the storage device adapted to store the shared key and the encrypted version of the shared key;
a device coupled to the storage device adapted to encrypt data under the control of the shared key;
a packet builder coupled to the storage device and the device, adapted to build a data packet incorporating the encrypted version of the shared key and the encrypted data.
at least a first and a second node, each node having a master key known only to that node, both nodes having a shared key, the nodes being coupled to form a network;
an encrypter coupled to the first node comprising:
an input device adapted to receive from the second node an encrypted version of the shared key encrypted under the control of a master key known only by the second node;
a storage device coupled to the input device, the storage device adapted to store the shared key and the encrypted version of the shared key;
a device coupled to the storage device adapted to encrypt data under the control of the shared key;
a packet builder coupled to the storage device and the device, adapted to build a data packet incorporating the encrypted version of the shared key and the encrypted data.
11. The encrypter of claim 10, further comprising an output device coupled to the packet builder to transmit the encrypted data packet.
12. A network comprising:
at least a first and a second node, each node having a master key known only to that node, both nodes having a shared key, the nodes being coupled to form a network;
the second node adapted to transmit to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node;
a decrypter coupled to the second node;
an encrypted data packet at the first node, the encrypted data packet having an encrypted version of the shared key and encrypted data encrypted under the control of the shared key;
the first node adapted to transmit the encrypted data packet to the second node;
the decrypter adapted to receive the encrypted data packet transmitted from the first node;
the decrypter adapted to decrypt the encrypted version of the shared key under the control of the master key of the second node and decrypt the encrypted data under the control of the shared key.
at least a first and a second node, each node having a master key known only to that node, both nodes having a shared key, the nodes being coupled to form a network;
the second node adapted to transmit to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node;
a decrypter coupled to the second node;
an encrypted data packet at the first node, the encrypted data packet having an encrypted version of the shared key and encrypted data encrypted under the control of the shared key;
the first node adapted to transmit the encrypted data packet to the second node;
the decrypter adapted to receive the encrypted data packet transmitted from the first node;
the decrypter adapted to decrypt the encrypted version of the shared key under the control of the master key of the second node and decrypt the encrypted data under the control of the shared key.
13. A network comprising:
at least a first and second node, each node having a master key known only to that node, both nodes having a shared key, the nodes being coupled to form the network;
the second node adapted to transmit to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node;
a storage device at the first node adapted to store the shared key and an encrypted version of the shared key encrypted under the control of the master key of the second node;
a device coupled to the storage device adapted to encrypt data under the control of the shared key;
a packet builder coupled to the storage device and the device, adapted to build a data packet incorporating the encrypted version of the shared key and the encrypted data;
the first node adapted to transmit the data packet to the second node;
an input device at the second node adapted to receive the encrypted data packet including the encrypted version of the shared key encrypted under the control of the master key of the second node and the encrypted data encrypted under the control of the shared key;
a storage device coupled to the input device adapted to store the master key of the second node; and a decryption device coupled to the input device and the storage device, adapted to decrypt the encrypted version of the shared key under the control of the master key at the second node and decrypt the encrypted data under the control of the shared key.
at least a first and second node, each node having a master key known only to that node, both nodes having a shared key, the nodes being coupled to form the network;
the second node adapted to transmit to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node;
a storage device at the first node adapted to store the shared key and an encrypted version of the shared key encrypted under the control of the master key of the second node;
a device coupled to the storage device adapted to encrypt data under the control of the shared key;
a packet builder coupled to the storage device and the device, adapted to build a data packet incorporating the encrypted version of the shared key and the encrypted data;
the first node adapted to transmit the data packet to the second node;
an input device at the second node adapted to receive the encrypted data packet including the encrypted version of the shared key encrypted under the control of the master key of the second node and the encrypted data encrypted under the control of the shared key;
a storage device coupled to the input device adapted to store the master key of the second node; and a decryption device coupled to the input device and the storage device, adapted to decrypt the encrypted version of the shared key under the control of the master key at the second node and decrypt the encrypted data under the control of the shared key.
14. A method for building a data packet in a network, comprising the steps of:
(a) coupling a first node to a second node, the second node having a master key that is unique to that node and both nodes having a shared key, the first node including a memory;
(b) transmitting from the second node to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node; and (c) creating a data packet in the memory of the first node by:
(i) placing header information in the data packet, (ii) placing the encrypted version of the shared key received from the second node in the data packet, (iii) placing encrypted data in the data packet, and (iv) placing an integrity check vector in the data packet.
(a) coupling a first node to a second node, the second node having a master key that is unique to that node and both nodes having a shared key, the first node including a memory;
(b) transmitting from the second node to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node; and (c) creating a data packet in the memory of the first node by:
(i) placing header information in the data packet, (ii) placing the encrypted version of the shared key received from the second node in the data packet, (iii) placing encrypted data in the data packet, and (iv) placing an integrity check vector in the data packet.
15. A method for establishing secure communications between a first node and a second node in a network, comprising the steps of:
(a) coupling the first node to the second node, the second node having a master key that is unique to that node and both nodes having a shared key;
(b) transmitting from the second node to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node so that the encrypted version of the shared key can be incorporated by the first node into data packets transmitted to the second node and used by the second node to decrypt data in transmitted data packets to establish secure communications between the first node and the second node; and (c) transmitting from the first node to the second node a data packet including an encrypted version of the shared key encrypted under the control of the master key of the second node, data and an integrity check vector incorporated in the data packet as a function of the shared key and the data.
(a) coupling the first node to the second node, the second node having a master key that is unique to that node and both nodes having a shared key;
(b) transmitting from the second node to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node so that the encrypted version of the shared key can be incorporated by the first node into data packets transmitted to the second node and used by the second node to decrypt data in transmitted data packets to establish secure communications between the first node and the second node; and (c) transmitting from the first node to the second node a data packet including an encrypted version of the shared key encrypted under the control of the master key of the second node, data and an integrity check vector incorporated in the data packet as a function of the shared key and the data.
16. A method for establishing secure communications between a first node and a second node in a network, comprising the steps of:
(a) coupling the first node to the second node, the second node having a master key that is unique to that node and both nodes having a shared key;
(b) transmitting from the second node to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node to that the encrypted version of the shared key can be incorporated by the first node into encrypted data packets transmitted to the second node and used by the second node to decrypt data in transmitted encrypted data packets to establish secure communications between the first node and the second node;
(c) building a data packet at the first node, the data packet comprising an encrypted version of the shared key encrypted under the master key of the second node, data and an integrity check vector incorporated in the data packet as a function of the shared key and the data; and (d) transmitting from the first node to the second node an encrypted version of the data packet including the encrypted version of the shared key encrypted under the control of the master key of the second node, data and an integrity check vector incorporated in the data packet as a function of the shared key and the data.
(a) coupling the first node to the second node, the second node having a master key that is unique to that node and both nodes having a shared key;
(b) transmitting from the second node to the first node an encrypted version of the shared key encrypted under the control of the master key of the second node to that the encrypted version of the shared key can be incorporated by the first node into encrypted data packets transmitted to the second node and used by the second node to decrypt data in transmitted encrypted data packets to establish secure communications between the first node and the second node;
(c) building a data packet at the first node, the data packet comprising an encrypted version of the shared key encrypted under the master key of the second node, data and an integrity check vector incorporated in the data packet as a function of the shared key and the data; and (d) transmitting from the first node to the second node an encrypted version of the data packet including the encrypted version of the shared key encrypted under the control of the master key of the second node, data and an integrity check vector incorporated in the data packet as a function of the shared key and the data.
17. A method for transmitting and verifying the integrity of a data packet in a network, comprising the steps of:
(a) coupling a first node to a second node, the second node having a master key that is unique to that node and both nodes having a shared key;
(b) transmitting from the first node to the second node a data packet including an encrypted version of the shared key encrypted under the control of the master key of the second node, data and a first integrity check vector incorporated in the data packet as a function of the shared key and the data;
(c) decrypting an encrypted version of the shared key as it is received by the second node under the control of the master key of the second node to obtain the shared key;
(d) calculating at the second node a second integrity check vector utilizing the data of the data packet as received and the shared key at the second node; and (e) comparing the second integrity check vector to the first integrity check vector received by the second node in the data packet.
(a) coupling a first node to a second node, the second node having a master key that is unique to that node and both nodes having a shared key;
(b) transmitting from the first node to the second node a data packet including an encrypted version of the shared key encrypted under the control of the master key of the second node, data and a first integrity check vector incorporated in the data packet as a function of the shared key and the data;
(c) decrypting an encrypted version of the shared key as it is received by the second node under the control of the master key of the second node to obtain the shared key;
(d) calculating at the second node a second integrity check vector utilizing the data of the data packet as received and the shared key at the second node; and (e) comparing the second integrity check vector to the first integrity check vector received by the second node in the data packet.
18. The method of any one of claims 15, 16 and 17 wherein the step of transmitting the data packet is done serially.
19. The method of any one of claims 15, 16 and 17 wherein the first node has a master key to provide for two-way communications.
20. A method for high integrity transmission of a data packet in a network comprising the steps of:
(a) coupling a first node to a second node, the second node having a master key that is unique to that node and both nodes having a shared key;
(b) encrypting the shared key at the second node under the control of the master key of the second node to form an encrypted version of the shared key;
(c) transmitting the encrypted version of the shared key from the second node to the first node;
(d) building a data packet at the first node, the data packet comprising an encrypted version of the shared key encrypted under the master key of the second node, data and a first integrity check vector incorporated in the data packet as a function of the shared key and the data;
(e) transmitting the data packet from the first node to the second node;
(f) decrypting the encrypted version of the shared key as it is received at the second node under the control of the second node's master key to obtain the shared key;
(g) calculating at the second node a second integrity check vector utilizing the data of the data packet as it is received at the second node and the shared key of the data packet; and (h) comparing the second integrity check vector to the first integrity check vector received by the second node in the data packet.
(a) coupling a first node to a second node, the second node having a master key that is unique to that node and both nodes having a shared key;
(b) encrypting the shared key at the second node under the control of the master key of the second node to form an encrypted version of the shared key;
(c) transmitting the encrypted version of the shared key from the second node to the first node;
(d) building a data packet at the first node, the data packet comprising an encrypted version of the shared key encrypted under the master key of the second node, data and a first integrity check vector incorporated in the data packet as a function of the shared key and the data;
(e) transmitting the data packet from the first node to the second node;
(f) decrypting the encrypted version of the shared key as it is received at the second node under the control of the second node's master key to obtain the shared key;
(g) calculating at the second node a second integrity check vector utilizing the data of the data packet as it is received at the second node and the shared key of the data packet; and (h) comparing the second integrity check vector to the first integrity check vector received by the second node in the data packet.
21. A network comprising:
at least a first and a second node, each node having a master key and both nodes having a shared key, the nodes being coupled to form a network;
a decrypter coupled to the second node;
a data packet at the first node, the data packet having data, an encrypted version of the shared key encrypted under the master key of the second node and an integrity check vector;
the first node adapted to transmit the data packet to the second node;
the decrypter adapted to receive the data packet transmitted from the first node;
the decrypter adapted to decrypt the encrypted version of the shared key under the control of the master key of the second node, an integrity checking device coupled to the decrypter adapted to calculate an integrity check vector utilizing the data as received at the second node and the shared key and compare the calculated integrity check vector to the integrity check vector in the data packet.
at least a first and a second node, each node having a master key and both nodes having a shared key, the nodes being coupled to form a network;
a decrypter coupled to the second node;
a data packet at the first node, the data packet having data, an encrypted version of the shared key encrypted under the master key of the second node and an integrity check vector;
the first node adapted to transmit the data packet to the second node;
the decrypter adapted to receive the data packet transmitted from the first node;
the decrypter adapted to decrypt the encrypted version of the shared key under the control of the master key of the second node, an integrity checking device coupled to the decrypter adapted to calculate an integrity check vector utilizing the data as received at the second node and the shared key and compare the calculated integrity check vector to the integrity check vector in the data packet.
22. A network comprising:
at least a first and second node, each node having a master key and both nodes having a shared key, the nodes being coupled to form the network;
a first storage device at the first node adapted to store an encrypted version of at least one shared key encrypted under the control of the master key of the second node;
an integrity check vector calculating device coupled to the first storage device adapted to calculate an integrity check vector utilizing data and the at least one shared key; and a packet builder at the first node coupled to the first storage device and the integrity check vector calculating device, adapted to build a data packet incorporating the encrypted version of the at least one shared key, data and the integrity check vector;
the first node adapted to transmit the data packet to the second node;
an input device at the second node adapted to receive the data packet;
a second storage device at the second node coupled to the input device, adapted to store the master key;
a decryption device coupled to the input device and the second storage device, adapted to decrypt the encrypted version of the at least one shared key under the control of the master key;
an integrity checking device coupled to the input device and the decryption device, adapted to calculate an integrity check vector utilizing the data as received at the second node and the at least one shared key and compare the calculated integrity check vector to the integrity check vector in the data packet.
at least a first and second node, each node having a master key and both nodes having a shared key, the nodes being coupled to form the network;
a first storage device at the first node adapted to store an encrypted version of at least one shared key encrypted under the control of the master key of the second node;
an integrity check vector calculating device coupled to the first storage device adapted to calculate an integrity check vector utilizing data and the at least one shared key; and a packet builder at the first node coupled to the first storage device and the integrity check vector calculating device, adapted to build a data packet incorporating the encrypted version of the at least one shared key, data and the integrity check vector;
the first node adapted to transmit the data packet to the second node;
an input device at the second node adapted to receive the data packet;
a second storage device at the second node coupled to the input device, adapted to store the master key;
a decryption device coupled to the input device and the second storage device, adapted to decrypt the encrypted version of the at least one shared key under the control of the master key;
an integrity checking device coupled to the input device and the decryption device, adapted to calculate an integrity check vector utilizing the data as received at the second node and the at least one shared key and compare the calculated integrity check vector to the integrity check vector in the data packet.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US07/372,651 US5081678A (en) | 1989-06-28 | 1989-06-28 | Method for utilizing an encrypted key as a key identifier in a data packet in a computer network |
US372,651 | 1989-06-28 |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2018270A1 true CA2018270A1 (en) | 1990-12-28 |
Family
ID=23469096
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002018270A Abandoned CA2018270A1 (en) | 1989-06-28 | 1990-06-05 | Method for utilizing an encrypted key as a key identifier in a data packet in a computer network |
Country Status (7)
Country | Link |
---|---|
US (1) | US5081678A (en) |
EP (1) | EP0405215B1 (en) |
JP (1) | JPH0338131A (en) |
AT (1) | ATE142064T1 (en) |
AU (1) | AU624507B2 (en) |
CA (1) | CA2018270A1 (en) |
DE (1) | DE69028254T2 (en) |
Families Citing this family (108)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE3919734C1 (en) * | 1989-06-16 | 1990-12-06 | Siemens Ag, 1000 Berlin Und 8000 Muenchen, De | |
US5581614A (en) * | 1991-08-19 | 1996-12-03 | Index Systems, Inc. | Method for encrypting and embedding information in a video program |
JPH06102822A (en) * | 1991-09-26 | 1994-04-15 | Rooreru Intelligent Syst:Kk | File security system |
EP0537903A2 (en) * | 1991-10-02 | 1993-04-21 | International Business Machines Corporation | Distributed control system |
US5557518A (en) * | 1994-04-28 | 1996-09-17 | Citibank, N.A. | Trusted agents for open electronic commerce |
US7028187B1 (en) | 1991-11-15 | 2006-04-11 | Citibank, N.A. | Electronic transaction apparatus for electronic commerce |
WO1993026109A1 (en) * | 1992-06-17 | 1993-12-23 | The Trustees Of The University Of Pennsylvania | Apparatus for providing cryptographic support in a network |
US5317638A (en) * | 1992-07-17 | 1994-05-31 | International Business Machines Corporation | Performance enhancement for ANSI X3.92 data encryption algorithm standard |
US5235642A (en) * | 1992-07-21 | 1993-08-10 | Digital Equipment Corporation | Access control subsystem and method for distributed computer system using locally cached authentication credentials |
US5268962A (en) * | 1992-07-21 | 1993-12-07 | Digital Equipment Corporation | Computer network with modified host-to-host encryption keys |
US5237611A (en) * | 1992-07-23 | 1993-08-17 | Crest Industries, Inc. | Encryption/decryption apparatus with non-accessible table of keys |
US5222136A (en) * | 1992-07-23 | 1993-06-22 | Crest Industries, Inc. | Encrypted communication system |
US5301247A (en) * | 1992-07-23 | 1994-04-05 | Crest Industries, Inc. | Method for ensuring secure communications |
US5491752A (en) * | 1993-03-18 | 1996-02-13 | Digital Equipment Corporation, Patent Law Group | System for increasing the difficulty of password guessing attacks in a distributed authentication scheme employing authentication tokens |
US5442703A (en) * | 1993-05-30 | 1995-08-15 | Motorola, Inc. | Method for identifying corrupt encryption keys within a secure communication system |
US5351295A (en) * | 1993-07-01 | 1994-09-27 | Digital Equipment Corporation | Secure method of neighbor discovery over a multiaccess medium |
US5475763A (en) * | 1993-07-01 | 1995-12-12 | Digital Equipment Corp., Patent Law Group | Method of deriving a per-message signature for a DSS or El Gamal encryption system |
US5483598A (en) * | 1993-07-01 | 1996-01-09 | Digital Equipment Corp., Patent Law Group | Message encryption using a hash function |
US5455862A (en) * | 1993-12-02 | 1995-10-03 | Crest Industries, Inc. | Apparatus and method for encrypting communications without exchanging an encryption key |
US7991347B1 (en) * | 1994-04-07 | 2011-08-02 | Data Innovation Llc | System and method for accessing set of digital data at a remote site |
US6473860B1 (en) | 1994-04-07 | 2002-10-29 | Hark C. Chan | Information distribution and processing system |
US6088797A (en) * | 1994-04-28 | 2000-07-11 | Rosen; Sholom S. | Tamper-proof electronic processing device |
US5495533A (en) * | 1994-04-29 | 1996-02-27 | International Business Machines Corporation | Personal key archive |
US7181758B1 (en) * | 1994-07-25 | 2007-02-20 | Data Innovation, L.L.C. | Information distribution and processing system |
US5550984A (en) * | 1994-12-07 | 1996-08-27 | Matsushita Electric Corporation Of America | Security system for preventing unauthorized communications between networks by translating communications received in ip protocol to non-ip protocol to remove address and routing services information |
US5696823A (en) * | 1995-03-31 | 1997-12-09 | Lucent Technologies Inc. | High-bandwidth encryption system with low-bandwidth cryptographic modules |
US8548166B2 (en) * | 1995-04-03 | 2013-10-01 | Anthony J. Wasilewski | Method for partially encrypting program data |
US7224798B2 (en) * | 1995-04-03 | 2007-05-29 | Scientific-Atlanta, Inc. | Methods and apparatus for providing a partial dual-encrypted stream in a conditional access overlay system |
US6937729B2 (en) * | 1995-04-03 | 2005-08-30 | Scientific-Atlanta, Inc. | Representing entitlements to service in a conditional access system |
US5764772A (en) * | 1995-12-15 | 1998-06-09 | Lotus Development Coporation | Differential work factor cryptography method and system |
US5913921A (en) * | 1996-07-12 | 1999-06-22 | Glenayre Electronics, Inc. | System for communicating information about nodes configuration by generating advertisements having era values for identifying time reference for which the configuration is operative |
WO1998002815A1 (en) * | 1996-07-12 | 1998-01-22 | Glenayre Electronics, Inc. | Apparatus and methods for transmission security in a computer network |
US6005939A (en) * | 1996-12-06 | 1999-12-21 | International Business Machines Corporation | Method and apparatus for storing an internet user's identity and access rights to world wide web resources |
US6385723B1 (en) * | 1997-05-15 | 2002-05-07 | Mondex International Limited | Key transformation unit for an IC card |
US5958073A (en) * | 1997-05-30 | 1999-09-28 | Motorola, Inc. | Reliability enhanced processing system and method for optimizing |
US7515712B2 (en) * | 1997-08-01 | 2009-04-07 | Cisco Technology, Inc. | Mechanism and apparatus for encapsulation of entitlement authorization in conditional access system |
US6738907B1 (en) | 1998-01-20 | 2004-05-18 | Novell, Inc. | Maintaining a soft-token private key store in a distributed environment |
US6233687B1 (en) * | 1998-01-21 | 2001-05-15 | Nortel Networks Limited | Method and apparatus for providing configuration information in a network |
US6834111B1 (en) * | 1998-04-01 | 2004-12-21 | Matsushita Electric Industrial Co., Ltd. | Data transmitting/receiving method, data transmitter, data receiver, data transmitting/receiving system, av content transmitting method, av content receiving method, av content transmitter, av content receiver, and program recording medium |
US6230186B1 (en) * | 1998-04-28 | 2001-05-08 | Rhoda Yaker | Private electronic message system |
US6385730B2 (en) | 1998-09-03 | 2002-05-07 | Fiware, Inc. | System and method for restricting unauthorized access to a database |
US6799270B1 (en) * | 1998-10-30 | 2004-09-28 | Citrix Systems, Inc. | System and method for secure distribution of digital information to a chain of computer system nodes in a network |
JP2000156678A (en) * | 1998-11-19 | 2000-06-06 | Sony Corp | Signal processing circuit |
WO2000049764A1 (en) * | 1999-02-18 | 2000-08-24 | Sun Microsystems, Inc. | Data authentication system employing encrypted integrity blocks |
US6944762B1 (en) | 1999-09-03 | 2005-09-13 | Harbor Payments Corporation | System and method for encrypting data messages |
EP1132828A4 (en) * | 1999-09-17 | 2007-10-10 | Sony Corp | Data providing system and method therefor |
US6601170B1 (en) | 1999-12-30 | 2003-07-29 | Clyde Riley Wallace, Jr. | Secure internet user state creation method and system with user supplied key and seeding |
WO2001063831A1 (en) * | 2000-02-24 | 2001-08-30 | Valicert Corporation | Mechanism for efficient private bulk messaging |
US9450749B2 (en) * | 2000-03-29 | 2016-09-20 | Wolfgang S. Hammersmith | One-time-pad encryption with central key service |
FI111208B (en) * | 2000-06-30 | 2003-06-13 | Nokia Corp | Arrangement of data encryption in a wireless telecommunication system |
FR2812504B1 (en) * | 2000-07-31 | 2003-01-24 | At Sky | "ON THE FLY" ENCRYPTION / DECRYPTION SYSTEM FOR DATA BROADCAST |
US6909723B1 (en) | 2000-08-04 | 2005-06-21 | Intellon Corporation | Segment bursting with priority pre-emption and reduced latency |
US7298691B1 (en) | 2000-08-04 | 2007-11-20 | Intellon Corporation | Method and protocol to adapt each unique connection in a multi-node network to a maximum data rate |
US7352770B1 (en) | 2000-08-04 | 2008-04-01 | Intellon Corporation | Media access control protocol with priority and contention-free intervals |
US6987770B1 (en) | 2000-08-04 | 2006-01-17 | Intellon Corporation | Frame forwarding in an adaptive network |
US6907044B1 (en) | 2000-08-04 | 2005-06-14 | Intellon Corporation | Method and protocol to support contention-free intervals and QoS in a CSMA network |
US7469297B1 (en) | 2000-08-04 | 2008-12-23 | Intellon Corporation | Mechanism for using a quasi-addressed response to bind to a message requesting the response |
US6851049B1 (en) * | 2000-10-02 | 2005-02-01 | Pgp Corporation | Method and apparatus for facilitating secure anonymous email recipients |
JP3571665B2 (en) | 2001-03-30 | 2004-09-29 | 啓二 木村 | Product packaging |
US7983419B2 (en) * | 2001-08-09 | 2011-07-19 | Trimble Navigation Limited | Wireless device to network server encryption |
JP2004032001A (en) * | 2002-05-10 | 2004-01-29 | Sony Corp | Method and apparatus for encrypting/decrypting data |
US8149703B2 (en) * | 2002-06-26 | 2012-04-03 | Qualcomm Atheros, Inc. | Powerline network bridging congestion control |
US7120847B2 (en) * | 2002-06-26 | 2006-10-10 | Intellon Corporation | Powerline network flood control restriction |
US7826466B2 (en) * | 2002-06-26 | 2010-11-02 | Atheros Communications, Inc. | Communication buffer scheme optimized for VoIP, QoS and data networking over a power line |
US7529372B2 (en) * | 2002-09-25 | 2009-05-05 | Intellon Corporation | Method for setting an encryption key for logical network separation |
US7623542B2 (en) | 2002-10-21 | 2009-11-24 | Intellon Corporation | Contention-free access intervals on a CSMA network |
US20040268123A1 (en) * | 2003-06-27 | 2004-12-30 | Nokia Corporation | Security for protocol traversal |
US7281187B2 (en) | 2003-11-20 | 2007-10-09 | Intellon Corporation | Using error checking bits to communicated an address or other bits |
US8396216B2 (en) * | 2003-11-21 | 2013-03-12 | Howard G. Pinder | Partial dual-encryption using program map tables |
US8090857B2 (en) * | 2003-11-24 | 2012-01-03 | Qualcomm Atheros, Inc. | Medium access control layer that encapsulates data from a plurality of received data units into a plurality of independently transmittable blocks |
US7660327B2 (en) * | 2004-02-03 | 2010-02-09 | Atheros Communications, Inc. | Temporary priority promotion for network communications in which access to a shared medium depends on a priority level |
US20050175184A1 (en) * | 2004-02-11 | 2005-08-11 | Phonex Broadband Corporation | Method and apparatus for a per-packet encryption system |
US7715425B2 (en) * | 2004-02-26 | 2010-05-11 | Atheros Communications, Inc. | Channel adaptation synchronized to periodically varying channel |
US7363513B2 (en) * | 2004-04-15 | 2008-04-22 | International Business Machines Corporation | Server denial of service shield |
US8051207B2 (en) | 2004-06-25 | 2011-11-01 | Citrix Systems, Inc. | Inferring server state in s stateless communication protocol |
US20060013397A1 (en) * | 2004-07-13 | 2006-01-19 | International Business Machines Corporation | Channel adapter managed trusted queue pairs |
US8042170B2 (en) * | 2004-07-15 | 2011-10-18 | Qualcomm Incorporated | Bearer control of encrypted data flows in packet data communications |
US8265060B2 (en) * | 2004-07-15 | 2012-09-11 | Qualcomm, Incorporated | Packet data filtering |
US20060021066A1 (en) * | 2004-07-26 | 2006-01-26 | Ray Clayton | Data encryption system and method |
KR100854845B1 (en) * | 2004-07-30 | 2008-08-27 | 메시네트웍스, 인코포레이티드 | System and method for effecting the secure deployment of networks |
US7636370B2 (en) * | 2005-03-03 | 2009-12-22 | Intellon Corporation | Reserving time periods for communication on power line networks |
US7822059B2 (en) | 2005-07-27 | 2010-10-26 | Atheros Communications, Inc. | Managing contention-free time allocations in a network |
US8175190B2 (en) * | 2005-07-27 | 2012-05-08 | Qualcomm Atheros, Inc. | Managing spectra of modulated signals in a communication network |
US20070177433A1 (en) * | 2005-09-07 | 2007-08-02 | Jean-Francois Poirier | Method and system for data security of recording media |
DE102005046462B4 (en) * | 2005-09-21 | 2008-09-18 | Engel Solutions Ag | Network component for a communication network, communication network and method for providing a data connection |
US8503681B1 (en) | 2005-11-04 | 2013-08-06 | Cisco Technology, Inc. | Method and system to securely transport data encryption keys |
US20070223701A1 (en) * | 2006-01-30 | 2007-09-27 | Motorola, Inc. | Method and apparatus for utilizing multiple group keys for secure communications |
US8209548B2 (en) * | 2006-02-06 | 2012-06-26 | International Business Machines Corporation | Secure caching technique for shared distributed caches |
US8670564B1 (en) | 2006-08-14 | 2014-03-11 | Key Holdings, LLC | Data encryption system and method |
JP4983165B2 (en) * | 2006-09-05 | 2012-07-25 | ソニー株式会社 | COMMUNICATION SYSTEM AND COMMUNICATION METHOD, INFORMATION PROCESSING DEVICE AND METHOD, DEVICE, PROGRAM, AND RECORDING MEDIUM |
US8600528B2 (en) * | 2006-09-18 | 2013-12-03 | The Research Foundation Of State University Of New York | Real-time, packet-level quality assurance of electromechanical device control data |
US8493995B2 (en) | 2007-05-10 | 2013-07-23 | Qualcomm Incorporated | Managing distributed access to a shared medium |
US8543831B2 (en) * | 2007-11-14 | 2013-09-24 | Qimonda Ag | System and method for establishing data connections between electronic devices |
KR20100071209A (en) * | 2008-12-19 | 2010-06-29 | 한국전자통신연구원 | Verification of device using device tag |
JP5279693B2 (en) * | 2009-12-14 | 2013-09-04 | キヤノン株式会社 | COMMUNICATION DEVICE, COMMUNICATION DEVICE CONTROL METHOD, PROGRAM |
US9525999B2 (en) * | 2009-12-21 | 2016-12-20 | Blackberry Limited | Method of securely transferring services between mobile devices |
EP2559200A4 (en) | 2010-04-12 | 2015-04-22 | Qualcomm Inc | Detecting delimiters for low-overhead communication in a network |
US8601306B1 (en) * | 2010-06-22 | 2013-12-03 | Xilinx, Inc. | Decryption of configuration data for multi-die integrated circuits |
US8058897B1 (en) | 2010-06-28 | 2011-11-15 | Xilinx, Inc. | Configuration of a multi-die integrated circuit |
WO2012092399A2 (en) * | 2010-12-29 | 2012-07-05 | Secureall Corporation | Cryptographic communication with mobile devices |
US9091727B1 (en) | 2012-10-16 | 2015-07-28 | Xilinx, Inc. | Configuration and testing of multiple-die integrated circuits |
US20140244997A1 (en) * | 2013-02-25 | 2014-08-28 | Qualcomm Incorporated | Emergency mode for iot devices |
US8891605B2 (en) | 2013-03-13 | 2014-11-18 | Qualcomm Incorporated | Variable line cycle adaptation for powerline communications |
US20140281488A1 (en) * | 2013-03-15 | 2014-09-18 | Aruba Networks, Inc. | System and Method for Offloading Cryptographic Functions to Support a Large Number of Clients in a Wireless Access Point |
US9705850B2 (en) * | 2013-03-15 | 2017-07-11 | Arizona Board Of Regents On Behalf Of Arizona State University | Enabling comparable data access control for lightweight mobile devices in clouds |
EP3133766B8 (en) | 2015-08-19 | 2020-08-12 | Rohde & Schwarz SIT GmbH | Communication device and method for performing encrypted communication in multipoint networks |
US11019034B2 (en) | 2018-11-16 | 2021-05-25 | Akamai Technologies, Inc. | Systems and methods for proxying encrypted traffic to protect origin servers from internet threats |
US20220393856A1 (en) * | 2021-06-07 | 2022-12-08 | Microsoft Technology Licensing, Llc | Securely and reliably transmitting messages between network devices |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4159468A (en) * | 1977-11-17 | 1979-06-26 | Burroughs Corporation | Communications line authentication device |
US4227253A (en) * | 1977-12-05 | 1980-10-07 | International Business Machines Corporation | Cryptographic communication security for multiple domain networks |
JPS56143744A (en) * | 1980-04-09 | 1981-11-09 | Nec Corp | Data interchanging system |
US4578530A (en) * | 1981-06-26 | 1986-03-25 | Visa U.S.A., Inc. | End-to-end encryption system and method of operation |
US4578531A (en) * | 1982-06-09 | 1986-03-25 | At&T Bell Laboratories | Encryption system key distribution method and apparatus |
US4613901A (en) * | 1983-05-27 | 1986-09-23 | M/A-Com Linkabit, Inc. | Signal encryption and distribution system for controlling scrambling and selective remote descrambling of television signals |
US4736422A (en) * | 1983-06-30 | 1988-04-05 | Independent Broadcasting Authority | Encrypted broadcast television system |
US4887296A (en) * | 1984-10-26 | 1989-12-12 | Ricoh Co., Ltd. | Cryptographic system for direct broadcast satellite system |
NL8501211A (en) * | 1985-04-29 | 1986-11-17 | Philips Nv | KEY STORAGE AND DISTRIBUTION SYSTEM FOR CRYPTOGRAPHICALLY SECURE COMMUNICATION. |
US4731840A (en) * | 1985-05-06 | 1988-03-15 | The United States Of America As Represented By The United States Department Of Energy | Method for encryption and transmission of digital keying data |
JPS6272243A (en) * | 1985-09-26 | 1987-04-02 | Fujitsu Ltd | Ciphering system |
US4688250A (en) * | 1986-01-29 | 1987-08-18 | Rca Corporation | Apparatus and method for effecting a key change via a cryptographically protected link |
US4805216A (en) * | 1987-01-08 | 1989-02-14 | Compfax Corporation | Method and apparatus for continuously acknowledged link encrypting |
GB8704920D0 (en) * | 1987-03-03 | 1987-04-08 | Hewlett Packard Co | Secure messaging system |
US4771458A (en) * | 1987-03-12 | 1988-09-13 | Zenith Electronics Corporation | Secure data packet transmission system and method |
-
1989
- 1989-06-28 US US07/372,651 patent/US5081678A/en not_active Expired - Lifetime
-
1990
- 1990-05-18 AU AU55179/90A patent/AU624507B2/en not_active Ceased
- 1990-06-05 CA CA002018270A patent/CA2018270A1/en not_active Abandoned
- 1990-06-11 AT AT90111016T patent/ATE142064T1/en not_active IP Right Cessation
- 1990-06-11 DE DE69028254T patent/DE69028254T2/en not_active Expired - Lifetime
- 1990-06-11 EP EP90111016A patent/EP0405215B1/en not_active Expired - Lifetime
- 1990-06-26 JP JP2168150A patent/JPH0338131A/en active Pending
Also Published As
Publication number | Publication date |
---|---|
EP0405215A3 (en) | 1992-11-04 |
AU624507B2 (en) | 1992-06-11 |
DE69028254T2 (en) | 1997-03-06 |
EP0405215B1 (en) | 1996-08-28 |
EP0405215A2 (en) | 1991-01-02 |
DE69028254D1 (en) | 1996-10-02 |
AU5517990A (en) | 1991-05-02 |
ATE142064T1 (en) | 1996-09-15 |
US5081678A (en) | 1992-01-14 |
JPH0338131A (en) | 1991-02-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US5081678A (en) | Method for utilizing an encrypted key as a key identifier in a data packet in a computer network | |
US6052466A (en) | Encryption of data packets using a sequence of private keys generated from a public key exchange | |
JP3502200B2 (en) | Cryptographic communication system | |
EP0998799B1 (en) | Security method and system for transmissions in telecommunication networks | |
US5179591A (en) | Method for algorithm independent cryptographic key management | |
US5297208A (en) | Secure file transfer system and method | |
US7277548B2 (en) | Cryptographic method and computer program product for use in wireless local area networks | |
US5638444A (en) | Secure computer communication method and system | |
US4503287A (en) | Two-tiered communication security employing asymmetric session keys | |
EP0576224B1 (en) | Cryptographic key management apparatus and method | |
US20120250863A1 (en) | Chaotic cipher system and method for secure communication | |
WO2010064666A1 (en) | Key distribution system | |
JPH06232861A (en) | Apparatus and method for cipher key management | |
WO1990009009A1 (en) | Data carrier and data communication apparatus using the same | |
KR20010043748A (en) | Multi-node encryption and key delivery | |
US7133525B1 (en) | Communication security apparatus and method of using same | |
US6542607B1 (en) | Device and method for the cryptographic processing of a digital data stream presenting any number of data | |
JPH09312643A (en) | Key sharing method and ciphering communication method | |
CN114499857A (en) | Method for realizing data correctness and consistency in big data quantum encryption and decryption | |
JP2007500481A (en) | An encryption method based on the DES algorithm. | |
EP1456997A1 (en) | System and method for symmetrical cryptography | |
JPH08204701A (en) | Electronic mail cipher communication system and cipher communication method | |
WO2021152212A1 (en) | Method and device for encrypting data | |
JPH07336328A (en) | Cipher device | |
JP3327368B2 (en) | User password authentication method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
FZDE | Discontinued |