Method and apparatus for transaction and identity verification4264782Abstract A method and apparatus whereby the senders and receivers of messages sent over a transmission system including a Host CPU may guarantee the integrity of the data content of the message and also the absolute identity of the sender. Each user of the system as well as the Host CPU contains an identical key-controlled block-cipher cryptographic device with data chaining for encrypting and decrypting messages as required, wherein each user has knowledge of only his own cryptographic key and wherein the Host CPU has access to the unique cryptographic keys of all users of the system stored in a high security storage area available only to said CPU. Stated very generally, the originator of a message A sends a message to a receiver B which includes a transaction or message portion X and a unique digital signature portion Y which is a function both of the message and the senders unique cryptographic key K.sub.A. The receiver then communicates with the CPU for verification of the signature Y. The CPU accesses the sender's key K.sub.A from a secure memory and computes the digital signature Y utilizing the message portion X received from B and the key K.sub.A. Upon a successful verification of the signatures by the CPU, the CPU notifies B via an additional message that the signature of A is valid based on the data content of the message and the key K.sub.A. Based on the information received from the CPU, B may be certain that the signature and message originated with A and A may not later deny having sent the message as it would be virtually impossible for the signature to be forged since it is a complex function of the message content itself. A may also be assured that B cannot alter the message as the signature would no longer be valid. According to other aspects of the invention the interrupting of communications between A and B by an eavesdropper and the subsequent sending of stale messages is prevented. As a still further feature of the invention, an eavesdropper is prevented from sending the "forged" approval from the CPU to the receiver B. Claims Having thus described my invention, what I claim as new, and desire to secure by Letters Patent is: Description DESCRIPTION
______________________________________
A .rarw. .fwdarw. K.sub.A *
B .rarw. .fwdarw. K.sub.B *
.
.
.
Z .rarw. .fwdarw. K.sub.Z *
______________________________________
*TABLE-
In the above * Table and in the system it is assumed that an address into the * Table may be derived from the User's ID, i.e. A through Z. In the present system it is assumed that the signature for data D by any User A which is denoted by the symbol S(K.sub.A,D) is the final 8 bytes of the encipherment of the message D by the DES encryption system using chaining with the key K.sub.A. As will be apparent later, the data D is a composite of a number of different items including both user ID's, the date, both user time stamps and the message in a predetermined format which will be set forth more fully subsequently. There will now follow a description of the transaction protocol. It is assumed that each terminal is fitted with a DES encipherment box. Also, each terminal has a programmable timer or "clock" which continuously increments for at least a 24 hour period. The verification device which is denoted herein as the Verify Unit is located in the Host CPU and is equipped with the specific functional units shown in FIGS. 3A and 3B which consist essentially of a number of special registers for holding signatures and user keys, as well as a DES encipherment box. A transaction from User A (the originator) to User B (the recipient) proceeds in the following manner. It should first be noted, however, that the following description of the transaction presumes the existence of the above-referenced data stamp mechanisms, counters, etc. A much less secure system could be built without the re-use of same, however, the use of previously verified or stale messages would be impossible to detect without these features. Proceeding now with a description of a typical transaction. (i) User A and User B establish a link upon the request of User A and User B supplies to User A the current counter value CT.sub.rec at user B's terminal. At the same time User B stores this counter value at his own terminal for later checking. (ii) User A constructs a valid signature represented as follows: S(K.sub.A,D) wherein the data D is defined by the following formula: D.rarw..fwdarw."User A to User B on Feb. 28, 1977, CT.sub.ori, CT.sub.rec --Buy 100 shares of . . . " Upon completion of the generation of the signature S, A sends the pair: (D,S(K.sub.A, D)) to User B. As implied by the definition of the data value D, the actual message data is prefixed by the sequence of parameter values which are the identity of the originator and the recipient of the transaction, i.e., A and B; the date of the transaction, i.e., Feb. 2, 1977; the current counter value CT.sub.ori at User A's terminal and the received counter value CT.sub.rec from User B's terminal. In the following description for ease of reference, the message pair which A sends to B denoted by the above formula (D,S(K.sub.A,D)) will be referred to subsequently as the message pair (X,Y). In this pair value X corresponds to the data message D as defined above, and the value Y corresponds to the Signature S(K.sub.A,D). Proceeding now with the description of the protocol, the User B receives a pair (X,Y) which is presumptively equal to the previous message (D,S(K.sub.A,D)). At this point, the User B examines the prefix portion of the message (X,Y) denoted by X. As will be remembered, this prefix portion contains the User A and B identities, dates, and the two counter values, CT.sub.ori and CT.sub.rec. The verification process will continue only under the following conditions. The data information is current. User B is identified in the prefix as the recipient. The counter value in the prefix, i.e., CT.sub.rec agrees with the value forwarded to User A by User B when User A requested a link and which was subsequently stored at User B's terminal. Assuming all of these tests are met, User B then enciphers the entire message pair (X,Y) with User B's own individual key K.sub.B to form a message U, which is defined as: U= (K.sub.B,(X,Y)) After enciphering the message U, User B transmits same to the Host together with the names A and B of the originator and recipient of the transaction. The special purpose verify hardware resident in the CPU when supplied with the parameters A, B and U which have just been received from the User B will proceed to perform the following operations. Utilizing the identities A and B the CPU will cause the values K.sub.A.sup.* and K.sub.B.sup.* to be accessed from * Table in the CPU memory. It will be remembered from the previous description that K.sub.A.sup.* = (K.sub.HV,K.sub.A) and K.sub.B.sup.* = (K.sub.HV,K.sub.B) from the * Table. Utilizing the K.sub.A.sup.* and the K.sub.B.sup.* and the known Verify Unit key, K.sub.HV, the Verify Unit associated with the CPU will decipher the two values and determine the user keys K.sub.A and K.sub.B internally of the Verify Unit and appropriately store these in holding registers therefor, as will be explained subsequently. The Verify Unit next deciphers the message U under its original encipherment key K.sub.B internally. This is represented by the formula U= .sup.-1 (K.sub.B,U). The system then treats the deciphered message U as two different parts U.sub.1 and U.sub.2 wherein U.sub.1 =U[1,n] U.sub.2 =U[n+1,n+8] In the above formulas it will be noted that U.sub.1 is the first n bytes which correspond to the data portion of the message X as originally transmitted and the portion U.sub.2 is equal to the last eight bytes of the message U which it will be remembered corresponds to the signature portion Y. At this point in time the system computes the signature of U.sub.1 utilizing the key K.sub.A and compares with the actual received signature U.sub.2. Utilizing a compare variable C, if C=1 it is assumed that there is a complete agreement of the signatures and if C=0 it is assumed that there is no such agreement. Assuming C=1 the verify portion of the system will cause a signature to be derived for the logical complement of the concatenation (U.sub.1,U.sub.2), this logical complement being denoted by .about.(U.sub.1,U.sub.2), using the DES encryption system under chaining with the key K.sub.B. The resulting verification message V will be returned to User B wherein: V=S(K.sub.B,.about.(U.sub.1,U.sub.2)) or if C=0, the verify portion of the system will cause a signature to be derived for the concatenation (U.sub.1,U.sub.2) using the DES encryption system under chaining with the key K.sub.B. The resulting message V will be returned to User B wherein: V=S(K.sub.B,(U.sub.1,U.sub.2)) At this point it should be noted that the operation of the Verify Unit is shown as performing a comparison of signatures to determine whether a successful or correct signature has been received from the User A. However, a further decision is made by the User B based on the message V returned to the User B by the CPU and the Verify Unit. As previously stated, regardless of the result of the comparison, i.e., C=1 or C=0, the Verify Unit will derive a signature V based on (U.sub.1,U.sub.2) utilizing DES and the key K.sub.B. The resulting verify message V will be returned to User B. User B, using the verify message V, can now determine if the message (X,Y) from User A (presumptively equal to (D,S(K.sub.A,D)) was properly signed. Upon receipt of the message V, User B will calculate a new signature defined by the following formula: V'=S(K.sub.B,.about.(X,Y)) It will be noted that if everything is proper the newly calculated signature V' will equal and correspond exactly to the message V, which the CPU has returned to User B. Thus, in summary, User B will accept the transaction if and only if the data information in X is current, the "counter" values in X agree with the stored counter values which operations were done previously upon receipt of the initial transaction from User A. The final requirement, and the most critical is the receipt of a valid verify signal from the CPU, i.e., V=V'. It should be noted that in each case the signatures V and V' are the last 8 bytes of the total encryption of the indicated data contents of said signatures under the key K.sub.B. In the case of a dispute between the originator, User A and the recipient User B, User B will be required to produce the pair (X,Y) where Y is claimed to be the signature of X by User A. The arbiter will decide that the transaction is valid if and only if: Y=S(K.sub.A,X) which again is the signature for the putative data message X using User A's key K.sub.A. Only one transaction with the same counter values will be declared valid on a given date. The role of the counter or time value is to protect against the re-use of a previously verified transaction; for example, User C, masquerading as User A, retransmits a previously verified (and accepted) transaction to User B. The "time stamp" imposes the protocol that no two messages will be accepted if they have identical time stamps, thus, eliminating this attempt at subversion of the transaction system. BEST MODE FOR CARRYING OUT THE INVENTION Having generally described the herein disclosed method for establishing a transaction protocol in accordance with the teachings of the present invention a description will follow of a best mode hardware configuration capable of performing this protocol. FIG. 1, as stated briefly before, comprises a broad functional block diagram of the overall system wherein a plurality of terminals are shown connected via a data communication system to a centrally located Host CPU. A Verify Unit (VAULT) is directly connected to the Host CPU and may in fact be embedded therein. It is referred to as the VAULT to indicate the very high security nature of the hardware contained therein, it being clearly understood that only the system manager with special authorization should ever have access to any of the internal information stored in said VAULT and that the security of the system is limited by the security of the personnel having access thereto. This will be well understood since the various user keys stored in the * Tables in main memory would be decipherable to anyone having access to the Verify Unit's master key K.sub.HV which is not accessible, it being loaded into the VAULT at the time of system initialization by the system manager. The principal functioning units of the Verify Unit will be set forth subsequently in the description of FIGS. 3A and 3B. The details of the Verify Unit Controller are shown in FIGS. 4A and 4B. FIG. 2 shows the structure of a typical remote terminal suitable for use with the present system. The majority of the blocks of the terminal are completely conventional in nature and operate in a straightforward way. For example, the MODEM block is a modulator/demodulator well known in the art for connecting the terminal to the data bus. The CRT Display and Display Controller perform the obvious function of displaying information keyed into the terminal via the keyboard, accessed from the system memory, or received from the CPU. The keyboard is a conventional unit for entering alphanumeric data and for purposes of the present invention it should be understood that the user keys K.sub.A or K.sub.B could either be entered via the keyboard or could be stored in the System Memory uniquely accessible via a special code enterable at the keyboard by a particular user. Thus, a number of different users having different user keys K.sub.X could utilize a single terminal in accordance with the teachings of the present invention it being understood that their particular keys would either have to be entered at the keyboard or suitably accessed from the System Memory. The unique devices required of the terminal for practicing the present invention are a Programmable Timer which would be utilized to produce the counter values CT.sub.rec and CT.sub.ori mentioned in the previous description of the present transaction verification system. The DES Module shown in the terminal is identical to that shown as the DES unit in FIGS. 3A and 3B and comprises a standard key controlled block cipher encryption box with chaining. The best known example being the previously referenced U.S. Pat. No. 4,078,152, of L. B. Tuckerman. It will be noted that the encryption system denoted herein by the symbol (.pi.) in the formulas of FIGS. 5A through 5G, operate in a straightforward manner when provided with an encryption key K and a data block to be encrypted. Given this data the DES block will automatically produce encrypted (.pi.) or decrypted (.pi..sup.-1) data in its output. The System Memory Controls are so configured that when the particular data message D is being encrypted, the last 8 bytes thereof may be automatically accessed as they comprise the unique digital signatures of the present system as described in detail previously. The block marked File Controller is a back up storage device associated with the terminal unit and would be used for example to store messages when the terminal is used as an originator, i.e., User A, or as a recipient, i.e., User B. In this case it should be clearly understood that User A and User B in the present description, refer to the originator and recipient of a particular transaction respectively. The operation of such terminals under control of a suitable microprocessor is well known in the art and will not be gone into in greater detail since the performance of the various operations required of the terminals are extremely straightforward and well known as is the case with the Programmable Timer and also the Data Security Module. Referring now to FIGS. 3A and 3B, the primary functional units of the Verify Unit are disclosed. The S-Register stores derived signatures generated in the Verify Unit. The contents of the S-Register may be sent to the Comparator or to the Host CPU as the case requires. The DES Unit, as stated previously with respect to the description of FIG. 2, is a key controlled block cipher encryption device with chaining of the type described previously with respect to the DES Module of FIG. 2. This unit receives three data items, namely an encryption key, the data, either to be encrypted or decrypted, and finally, an indication of whether an encryption or decryption cycle is required. Control lines C13, C14 and C15 control the loading of key data, message data, select the mode of operation and initiate the cryptographic conversion process. The Register is for the purpose of specifically storing the originator's key, either in clear (K.sub.A) form or in encrypted (K.sub.A *) form. The B-Register stores the receiver's (User B) key in either clear or encrypted form. The block entitled, Read Write Memory (RWM), essentially stores the received complete messages transmitted by the system. The K.sub.HV Register stores the Verify Unit's master key under which all of the user keys K.sub.X are stored in the Host CPU's master memory, in encrypted form in the previously described * Table. When these encrypted keys are sent to the Verify Unit they are decrypted utilizing the master encryption key K.sub.HV to access the actual keys, i.e., K.sub.A and K.sub.B in the present illustration. The Comparator block performs the exclusive function of comparing signatures on demand and will produce a one (1) or a zero (0) on its output line, depending upon whether or not the comparison is successful. The Verify Unit Controller shown at the bottom of FIG. 3B, as is apparent, controls the operation of the Verify Unit wherein the various signals utilized are shown on the left side of the block and the handshake output signals, both to the Host and to its own circuitry, are shown emanating from the right side of the block. No commands as such are received by the Verify Unit Controller from the outside. The only signals received by the Verify Unit Controller are two status signals (S1, S2) and five handshake signals (RQVRF, . . . ,URDY). The Verify Unit is under control of the command structure set up in the microprogram memory (FIG. 4A) and is independent of external commands thereby precluding any external attempts to modify the operating sequences of the hardware resources within the Verify Unit. The Verify Unit Controller is shown in more detailed form in FIGS. 4A and 4B. The functional units in the Verify Unit designated as CP1 through CP18 are referred to by digital design engineers as control points. Their operational sequences are quite complex in that they may perform both a gating function and a multiplexing or demultiplexing operation depending upon whether they are gating byte serial data into the various registers or out of said registers. From a functional standpoint, however, they may be simply considered as gate circuits having the multiplexing function indicated by the bit configurations entering and emanating from each control point. Each of the control points CP1 through CP18 are indicated as being controlled by control line C1 through C18. For example, control point CP2 takes seven consecutive 8 bit bytes and places them in seven consecutive 8 bit storage registers in the functional unit denoted as the A-Register (a total of 56 bits). Similarly, the control point CP6 does just the opposite. That is, it takes 7 consecutive 8 bit bytes from the A-Register and reconverts them into a series of seven 8 bit bytes which it places serially on the CD bus. It will be noted that the two control points designated as CP5 and CP17 convert from 8 bits to 64 bits since the S-Register utilizes an 8 byte signature. It will be remembered that, by definition, the signature is the last 8 bytes of the appropriately encoded message. Also, the control point CP10 is a selective inverter. That is, depending upon whether a 1 or 0 appears on control line C10, then 8 data bits passing through same will be inverted or pass through in true form. Control point CP11 merely performs a gating function. It will be noted that the Read/Write Memory (RWM) is organized in 8 bit storage locations, accordingly the control points, CP4, CP10 and CP11 need not perform any multiplexing/demultiplexing functions as described previously. The details of the Control Point Units are not specifically shown as they would be obvious to a digital design engineer and moreover, could take a number of different design forms and still perform the required function. The following table clearly indicates the specific functions performed by each of the Control Point Units.
______________________________________
VERIFY UNIT CONTROL POINT
FUNCTIONAL DEFINITION TABLE
Func-
tional
Con- Unit
trol Con-
Signal
trolled Operation Controlled
______________________________________
C1 CP1 INPUT BUS .rarw. HOST CPU DATA
C2 CP2 A-REG .rarw. INPUT BUS DATA
C3 CP3 B-REG .rarw. INPUT BUS DATA
C4 CP4 RWM .rarw. INPUT BUS DATA
C5 CP5 S-REG .rarw. INPUT BUS DATA
C6 CP6 C-D BUS .rarw. A-REG DATA
C7 CP7 CLEAR A-, B-REGS TO ZERO
C8 CP8 C-D BUS .rarw. B-REG DATA
C9 CP9 READ/WRITE MODE AND ENABLE
CONTROL
C10 CP10 PASS/INVERT RWM OUTPUT DATA
C11 CP11 C-D BUS .rarw. RWM DATA
C12 CP12 C-D BUS .rarw. K.sub.HV REG DATA
C13 DES LOAD DES KEY BUFFER FROM C-D
BUS
C14 DES LOAD DES DATA BUFFER FROM C-D
BUS
C15 DES CONVERT DATA (CRYPTOGRAPHIC
PROCESSING)-SELECT MODE -
INITIATE OPERATION
C16 CP16 INPUT BUS .rarw. DES OUTPUT DATA
C17 CP17 OUTPUT BUS .rarw. S-REGISTER DATA
COMPARATOR .rarw. S-REGISTER DATA
C18 CP18 HOST CPU .rarw. OUTPUT BUS DATA
______________________________________
Referring now to FIGS. 4A and 4B the details of the hardware configuration of the Verify Unit Controller are shown. The controller follows the well known architecture of a small microprogrammed controller, such as is well known in the art. Part of the controller is of course the Micro Program Memory wherein the various operational sequences are stored. Particular addresses in the Micro Program Memory selected for particular operations are determined, as will be well understood, by the Micro Program Controller 12. As a given sequence is running the next address to the Micro Program Memory 10 comes from an internal microprogram counter which is incremented unless a branch to another location in the microprogram memory is required whereupon the branch address is loaded into the microprogram controller from the branch address field of the control word register. The various conditions which control operation of the Micro Program Controller are received from the Input Multiplexer wherein the various status and/or handshaking control signals will allow a particular sequence to proceed or be terminated. The particular line of the Input Multiplexor 14 utilized for controlling a given sequence is selected by the 3 bit IMPX Address field in the Control Word Register which is connected to the IMPX 14 address input port. The following Host CPU/Verify Unit Handshake Control Definition Table is included for convenience of reference.
______________________________________
HOST CPU/VERIFY UNIT INTERFACE
DEFINITION TABLE
Handshake
Signal Function
______________________________________
RQVRF Inform VU of request for verification
RQV Inform VU of request for derived sig-
nature V
KA*RDY Inform VU that KA* data are ready for
transfer
KB*RDY Inform VU that KB* data are ready for
transfer
URDY Inform VU that U data are ready for
transfer
BUSY A flag indicating Verify Unit status
RQKA* Inform CPU of request for KA* data
RQKB* Inform CPU of request for KB* data
RQU Inform CPU of request for U data
VRDY Inform CPU derived signature V is ready
for transfer
______________________________________
The Control Word Register clearly indicates the format of the instructions stored in Micro Program Memory and utilized by the system. The six specified fields are believed to be self-explanatory. The next address select, IMPX address, and branch address have just been described. The handshake control field comprises six bits, three of which address the five bit addressable latch 16. The 3 bit address lines selects an output line; "data" line is supplied with a binary value (0 or 1) that is desired at the selected output line; the "enable" line causes the binary value on the "data line" to be "latched" and thereby appear on the selected output line. The "clear" line clears all output lines to zero. For example, if you wish to set "RQU" to 1 (as in block 10 of Verify Unit Flow Chart). RQU is associated with output line 3 of the 5-bit addressable latch. The 3 "address" lines are set to "011" (binary 3), the "data" line is set to 1, and the "enable" line is set to 1 (momentarily) thereby causing output line 3 to take on the binary value of 1. Thus, RQU=1, informing the Host CPU of a request for U data. The Data Path control field of the Control Word Register controls the various Control Point Units described previously. These signals are used to either control the data flow paths between the various registers or to control the operation of functional units such as the RWM and the DES unit of the Verify Unit as will be well understood. It will be noted on FIG. 3 that 18 Data Paths Control Lines are indicated. This is in essence a functional number of the Control Point Units requiring a plurality of inputs. Finally, the R/W Memory Address Generation field, has a five bit field which controls the R/W Memory Address Generator block 18. This block actually contains two functional units, a twelve bit bidirectional counter and a storage register for saving desired counter settings or addresses. The counter supplies an ascending sequence of memory addresses to the RWM unit to enable it to store the remaining string of message bytes making up a particular message which are received by the Verify Unit. The upper input to the generator 18, from the clock generator, produces a pulse each time a data byte is received by the system. The five bits coming from R/W Memory Address generation field of the Control Word Register perform selectively the following functions. The "reset" line causes the counter to be reset to all zeros. The "load" line causes the current contents of the storage register mentioned previously to be loaded into the counter. The "count" line is essentially an enable line which allows the clock pulses to increment or decrement the counter as determined by the "up/down" line which controls whether, depending on the given operational sequence the counter is being incremented or decremented respectively. When the save line is actuated it causes the contents of the counter to be stored into the register. It will be noted that the 12 bit output R/W Memory Address cable emanating from the generator 18 comes directly from the counter stages. It is these consecutive addresses which cause a given message to be stored in consecutive storage locations in the R/W Memory shown in FIG. 3B of the Verify Unit. The two units designated 3 state buffers 20 are in effect gate circuits which will selectively gate to the Micro Program Controller either the data on the 12 bit cable emanating from the branch address field of the Control Word Register or from the R/W Memory Address Generator 18. This essentially completes the general description of the presently disclosed transaction verification system. It should be noted that the various operations required of the Host CPU would conventionally be performed by straightforward programming means. The functions required of the CPU are essentially those of setting up communication paths between the user A and user B, requesting service from the resident Verify Unit and for providing requested entries from the * Table to the Verify Unit. Reference to the Operational Sequence Charts for the Verify Unit together with the following description of the overall flow chart of FIGS. 5A through 5G will clearly explain the detailed operation of the present system. It should be understood that the User A and the User B flow charts are both present in any given terminal, however, depending upon whether a given user is an originator or a recipient, the "originating" or "receiving" operational sequence will be activated. In the flow chart of FIGS. 5A through 5G, it will be noted that there are a number of dashed lines terminating in an arrow implying a direction of communication between the various operational sequences comprising the present transaction verification system. Each of these arrows in effect represents a handshaking operation which is required of the present system, wherein control passes from one operational sequence to the other as the need arises. These handshaking operations take place between the CPU and the Verify Unit Controller and utilize the handshaking control signal lines for that purpose. The occurrence of the handshaking operations is clearly apparent in the operational sequence charts. Referring now to the system flow diagram which describes a complete Transaction Verification Operation, reference will first be made to FIG. 5, which is an organizational diagram for FIGS. 5A through 5G. By arranging the figures in this fashion a single flow chart for the operation of the entire system is shown. Referring to the flow chart, each of the operational sequences is clearly labeled as occurring within the terminal of User A or User B, the Host CPU, or the Verify Unit. It should be noted that on FIG. 5B there are six blocks which are the terminal portion of the User B operational sequence. This is specifically labeled on FIG. 5G. Before proceeding with the specific description of the flow chart, the following is a Definition of Terms Table setting forth the formulas and their definitions as used in the flow chart and in the prior general description of the overall operational protocol of the system. It is believed that reference to this table of definitions will greatly facilitate an understanding of the following description of the flow chart.
______________________________________
DEFINITION OF TERMS TABLE
______________________________________
1. M: message (i.e., Busy 50 shares RDQ common . . .)
2. D:data: (A, B, date, CT.sub.orig, CT.sub.rec, M)
3. S(K.sub.A, D): Signature of data D: S(K.sub.A, D): last
eight bytes of the chained encipherment of D
by DES using the key K.sub.A.
4. (X,Y): the message received from User A,
presumptively equal to (D,S(K.sub.A,D).
5. CT: a current counter value at a particular
terminal (orig/rec)
6. K.sub.A : User A's key - K.sub.B : User B's key
7. K.sub.HV : Verify Unit's master key
8. K.sub.Z *: .pi.(K.sub.HV, K.sub.Z), i.e., for any user Z
9. .pi./.pi..sup.-1 : encryption/decryption under an encryption
key
10. U = .pi.(K.sub.B, (X, Y))
11. --U = .pi..sup.-1 (K.sub.B,U) = ( --U.sub.1, --U.sub.2)
12. --U.sub.1 = --U[1,n]: - --U.sub.2 = --U[n + 1,n + 8]
13. V = S(K.sub.B, --Uor S(K.sub.B, .about. --U) = last eight bytes
of
the chained encipherment of U by DES using the
key K.sub.B
14. If S(K.sub.B, .about. --U) = S(K.sub.B .about.(X,Y)) then
signature of A
is valid for message X.
______________________________________
Referring now to the flow chart it will first be noted that the successive blocks in each of the separate sequences are numbered consecutively for ease of reference. In may be assumed, beginning in FIG. 5A that User A wishes to initiate a transaction utilizing the present transaction verification system. User A's terminal begins operation as indicated in block 1 and a determination is made as to whether a transaction is being initiated. If not the system proceeds to block 2 where a test is made as to whether a transaction request has been received, if so the operation sequence would branch downwardly into the "receiver" mode. It will be noted, as indicated in the figure, that the operational procedure would be the same from this point on, as is shown for User B. Thus, the "originator"/"receiver" modes are both present in every terminal although only one would be operative during any given transaction. If the answer to the test made in block 2 is "no" the system would branch back to the beginning and continue cycling through blocks 1 and 2 in a "wait" state until either User A decides to initiate a transaction or receives a transaction request from another user which will cause the operational sequence to proceed in the appropriate manner. Assuming at this point that User A is the initiator of a transaction the system proceeds to block 3 and a link is established via the Data Communication Network with User B's terminal and control switches to block 1 of User B. As will be apparent a branch to block 2 will then occur when it is determined that a transaction request has been received from User A. At this point the User B sequence proceeds to block 3 which, in fact, establishes a link to User A over the Data Communication Network. At this point User B sends his current counter value CT.sub.rec, and at the same time causes the data: "indentity of A and CT.sub.rec " to be saved in his local memory for subsequent comparison purposes and at this point control is transferred back to User A. At this same time it is determined whether or not the counter value from User B has been received (CT.sub.rec). Next, User A's sequence proceeds to block 5 which causes A's signature to be generated. The formula for this signature is set forth clearly in line 3 of the Definition of Terms Table (Definition Table). The sequence proceeds then to block 6 wherein each transaction message for transmission to User B is constructed which comprises the message pair (X,Y) the specific contents of which are clearly shown and defined in lines 2, 3, 4, 5 and 6 of the Definition Table. At this point, control transfers to the User B sequence, Block 4. The receipt of the complete transaction message from User A causes the system to proceed to blocks 5, 6 and 8 wherein three straightforward data content tests are made, i.e., for the date, the correct addressee, i.e., User B and the proper counter value which it will be remembered was saved by User B in block 3. If any of these tests are negative the transaction will immediately abort or terminate as shown in block 7 and the sequence will proceed no further. If everything is correct however, the system proceeds to block 9 wherein the user key K.sub.B is provided to User B's DES Module which is a key-controlled block cipher cryptographic unit as described previously and similarly the message pair (X,Y) is made available to the encryption unit as the data to be encrypted, and the entire message pair (X,Y) is encrypted under User B's key to produce the message U, which is defined in line 10 of the Definition Table. The system then proceeds to block 10 wherein User B transmits to the Host CPU the message A, B, U. The portion of the message defined as A, B defines the originator and recipient of the message which is being sent to the CPU for verification. As will be remembered the data A and B provide entries to the * Table where the keys K.sub.A * and K.sub.B * are stored. At this point control transfers over to the Host CPU sequence. It will first be assumed that in the start operation, the system is initialized and all handshake lines to the Verify Unit are effectively cleared to zero. In block 1 the "request for verification" signal is received from User B. The sequence proceeds to block 2 wherein the message A, B, U, is received and appropriately stored in the CPU memory. In block 3 a test is made of the "busy" status of Verify Unit and if "busy" the system will wait until it is not busy and can proceed to block 4 wherein a request for a new transaction verification operation (RQVRF) is sent to the Verify Unit. Control then transfers the Verify Unit, specifically, block 2. It will be assumed that the start block causes the requisite handshake control output lines to be appropriately set to zero. Upon the receipt of a "request verification" signal the system proceeds to block 3 in the Verify Unit sequence wherein the "busy" flag at the Verify Unit handshake control outputs is set to a "1" which will advise the CPU that the Vertify Unit is "busy" in case it should attempt to request a further transaction verification operation. The system then proceeds to block 4 wherein a request is made for K.sub.A *. This request goes back to the Host CPU where it will be remembered the various user keys are encrypted under the system master key K.sub.HV in the * Table. This request will cause the RQKA* handshake control output line from the Verify Unit to be set to a one. At this point control is shifted back to the Host CPU and specifically block 5 thereof. In block 5 the request for K.sub.A * is acknowledged and the system proceeds to block 6 of the Host CPU sequence. In this block, the previously received value A, identifying the originator of the transaction, is used as an address into the * Table and the data referred to as K.sub.A * is accessed and KA* RDY handshake line proceeding to the Verify Unit input handshake control is set to a one, indicating to the Verify Unit, that the K.sub.A * data is ready. In block 7 the K.sub.A * data is transmitted to the Verify Unit and the KA* RDY handshake line is reset to a zero. At this point control transfers back to block 5 of the Verify Unit sequence. Block 5 acknowledges the signal, which causes K.sub.A * to be read into the A register of the Verify Unit and at this point the RQKA* handshake control output line is reset to zero. Control now proceeds to block 7 wherein a request is made for the K.sub.B * data. At this point it will be noted that blocks 7, 8 and 9 of the Verify Unit are essentially identical functionally to blocks 4, 5 and 6 of the Verify Unit with the exception that at the end of this sequence the data K.sub.B * is now loaded in the B register of the Verify Unit. Similarly, blocks 8, 9 and 10 in the Host CPU sequence are essentially identical to blocks 5, 6 and 7 thereof with the exception that in this case the data K.sub.B * is extracted from the * Table and sent to the Verify Unit. Assuming now that the data K.sub.B * is resident in the B register, the system will proceed to block 10 of the Verify Unit sequence wherein a request is made for the data U which has been stored in the Host CPU memory. At the same time the handshake control RQU is set to a "1" in the output from the Verify Unit and control transfers back to block 11 of the Host CPU which receives the request. The Verify Unit waits until the CPU is ready to send U. When the CPU is ready, it then sets URDY line to 1. In the meanwhile the Verify Unit is waiting and monitoring the URDY line. It is assumed here that U is available and accordingly the handshake control indicated as URDY is set to a one which informs the Verify Unit that the message segment U is available for transmission. In block 13 of the Host CPU sequence, the message segment U is sent to the Verify Unit and the URDY handshake input line to the Verify Unit is reset to a "zero". Referring now to block 12 of the Verify Unit the message segment U is read from the Host CPU and stored in the RWM of the Verify Unit and the handshake control output line RQU is reset to a "zero". Block 13 of the Verify Unit causes the originator key K.sub.A to be deciphered from the value K.sub.A * currently stored in the A register by transmitting K.sub.A * plus the system master key K.sub.HV to the DES Unit whereby User A's encryption key K.sub.A is decrypted and stored in the A register for further verification operations. The system then proceeds to block 14 where precisely the same operation is performed for the value K.sub.B * to produce the User B's key, K.sub.B, which is stored in the B register. At this point the Verify Unit sequence proceeds to block 15 wherein the message U is deciphered under the user key K.sub.B and the results are stored in the RWM as U. The definition or specification of the data content of the deciphered message U is shown in block 15A and is indicated as U.sub.1 and U.sub.2 which are the first n bytes of the deciphered message and the last 8 bytes of the deciphered message respectively. As will be remembered from the prior definition of the signature, these last 8 bytes or U.sub.2, are presumptively equal to the signature of User A. To verify this in block 16 the Verify Unit now causes the signature of User A under key K.sub.A to be constructed at this time utilizing the value U.sub.1 as the data source for the signature. Thus, if U.sub.1 has been truly received as the original message X, set by User A to User B and then enciphered under key K.sub.B and sent to CPU, then the last 8 bytes of this encipherment as performed in block 16, should be equal to the value U.sub.2. This comparison is made in block 17 and if the comparison is successful the Verify Unit will have determined that the signature for User A is valid. After this comparison the Verify Unit sequence may either branch to blocks 18 or 19 where construction of an "invalid" or "valid" message to be transmitted back to the User B is performed. In order to insure the secrecy and integrity of the return message, rather than just sending back a simple yes or no signal, which could be easily synthesized by an interloper on the line, blocks 18 and 19 cause a complex message defined as the signature V of U or of .about.U under the key K.sub.B to be generated. Thus, depending upon whether the comparison in block 17 was or was not successful, the signature V is derived utilizing .about.U, the logical complement of U or U as the data source. In block 20 the VRDY handshake line from the handshake control outputs of the Verify Unit is set to a "1" which when detected by the Host CPU activates block 14 of the Host CPU which is informed that the signature V is now ready in the Verify Unit. In block 15 of the Host CPU, V is requested by setting the handshake control input line RQV to a "1" which actuates block 20 in the Verify Unit. In block 22 of the Verify Unit and block 16 of the Host CPU the message V is sent from the Verify Unit to the CPU and in block 17 of the CPU's sequence the derived signature V is transmitted directly to User B. This terminates the Host CPU operational sequence for this particular verification request and in effect returns same to the state of block 1. Returning breifly to the Verify Unit operational sequence, transmission of the signature V to the Host CPU ends the active role of the Verify Unit operational sequence in the overall verification procedure, it being noted that block 23 and block 24 are merely clearing and resetting operations for removing stale data from the operational registers and resetting the various handshake lines to their standby or wait condition in block 2. In block 11 of the User B sequence on FIG. 5G, the terminal of User B is appropriately notified that the verification message V is ready to be transmitted from the Host CPU. At this point, appropriate control is actuated and the message V is in effect read from the Host CPU in block 12 and in block 13, User B constructs the signature of the logical complement of (X,Y) denoted by .about.(X,Y) under his own key K.sub.B which as will be remembered, comprises the last 8 bytes of the encryption of message .about.(X,Y) under the key K.sub.B. This generated signature is compared with the message V, which was received from the Host CPU in block 14 of the User B sequence. The test made in this block and its consequences are implied in line 14 of the Definition Table. It should be noted in passing that, providing the entire system is operating properly, and no messages have been erroneously transmitted or fraudulently transmitted, then U which is the decipherment of U under the key K.sub.B should be equal to the original message (X,Y). Thus, a successful comparison in block 14 indicates that the signature Y which User B originally received from User A is correct and proper for the message portion X. It will be further noted that in addition to User B now having confidence that he has been communicating with the true User A and further that he has received a valid message X, User A is similarly protected because of the absolute dependence of his valid signature on the content of the message X. This was explained previously with respect to the arbitration procedure possible in the present system and is repeated here for purposes of emphasis only. Having thus described the operation of the present system from the flow charts of FIGS. 5A through 5G it is believed that the overall operational characteristics will be well understood by those skilled in the art. There will now follow a detailed exposition of the operation of the Verify Unit controls in the form of an Operational Sequence List for the Verify Unit. This list comprises a sequence of the individual operations which would conventionally be performed by micro code stored in the microprogram memory of the Verify Unit which operations must be performed to practice the herein disclosed preferred embodiment of the invention. Referring to these operational sequence lists which are numbered in accordance with the blocks of the flow chart the discrete operations carried out and the manner in which the various units of hardware shown specifically in FIGS. 3A, 3B, 4A and 4B, operate will be readily understood. A list of definitions appears at the beginning of the Operational Sequence List which defines the various acronyms or abbreviations utilized.
______________________________________
Operational Sequence List
for Verify Unit
______________________________________
Definitions
RWM: Read/Write Memory
RWMAG: Read/Write Memory Address Generator
IMPX: Input Multiplexer
DES Unit:
Data Encryption Standard Unit
(Ci): i-th Control Point, activation of
RESET: RWMAG set to zero
LOAD: Contents of internal storage register are
loaded into RWMAG
COUNT: Enables RWMAG to count
U/--D: Up (1) /down (0) count-mode control for RWMAG
SAVE: Contents of RWMAG are saved in internal storage
register
CLEAR: All handshake control output lines are
cleared to zero
STEP
1 CLEAR
2 Set IMPX ADDRESS to 2
TEST RQVRF:
If 0, hold;
If 1, continue
3 Set BUSY to 1
4 Set RQKA* to 1
5 Set IMPX ADDRESS to 4
TEST KA*RDY:
If 0, hold
If 1, continue
6.1 Load A-Register with KA* from Host CPU. (C1,C2)
6.2 Clear RQKA* to 0
7 Set RQKB* to 1
8 Set IMPX ADDRESS to 5
9
9.1 Load B-Register with KB* from Host CPU. (C1,C2)
9.2 Clear RQKB* to 0
10 Set RQU to 1
11 Set IMPX ADDRESS to 6
Test URDY:
If 0, hold
If 1, continue
12
12.1 RESET
12.2 Set U/--Dto 1
12.3 Set RWM for write operation (C9)
12.4 Set IMPX ADDRESS to 6
12.5 Load one data byte of U from Host CPU to RWM
via Input-Bus (C1,C4)
12.6 Test URDY:
If 1, increment RWMAG and go to step 12.5;
If 0, continue
12.7 Clear RQU to 0
12.8 SAVE
13
13.1 Load key KHV into DES Unit (C12,C13)
13.2 Load data from A-Register (KA*) into DES Unit
(C6,C14)
13.3 Decipher data (C15)
13.4 Read 7 bytes of data (KA) from DES Unit into
A-Register (C16,C2)
14
14.1 Load key KHV into DES Unit (C12,C13)
14.2 Load data from B-Register (KB*) into DES Unit
(C8,C14)
14.3 Decipher data (C15)
14.4 Read 7 bytes of data (KB) from DES Unit into
B-Register (C16,C3)
15
15.1 Load N + 8 into Microprogram Controller
15.2 Load Key K.sub.B into DES Unit (C8,C13)
15.3 Set U/--Dto 1
15.4 RESET
15.5 SAVE
15.6 Set RWM for read operation (C9,C10)
15.7 Load 8 bytes of U data from RWM into DES Unit
(C11,C14)
15.8 Decipher data (C15)
15.9 LOAD
15.10 Set RWM for write operation (C4, C9)
15.11 Store 8 bytes of --Udata from DES Unit in
RWM (C16,C4)
Repeat steps 15.5 through 15.11 as necessary
until N + 8 bytes of U data have been processed.
16
16.1 Decrement RWMAG by 8 (RWMAG .rarw. N)
16.2 SAVE
16.3 Load N into Microprogram Controller
16.4 RESET
16.5 Set U/--Dto 1
16.6 Load Key KA into DES Unit (C6,C13)
16.7 Set RWM for non-inverting read operation
(C9,C10)
16.8 Load 8 bytes of --U.sub.1 data from RWM into DES Unit
(C11,C14)
16.9 Encipher data (C15)
Steps 16.8 and 16.9 are repeated as necessary until
a total of N bytes of data ( --U.sub.1) have been processed
from RWM. (A short block, if one occurs, and chain-
ing linkages are handled internally by the DES Unit). -
16.10 Read final 8 bytes of data from the DES Unit
into the S-Register (C16,C5)
[S-REGISTER .rarw. S(KA, --U)]
17
17.1
LOAD (RWMAG .rarw. N)
17.2
Set U/-- D to 1
17.3
Set RWM for non-inverting read operation
(C9,C14)
17.4
Set IMPX ADDRESS to 1
17.5
Increment RWMAG
17.6
Read data byte from RWM to comparator Q input
(C11)
17.7
Read data byte from S-Register to comparator P
input (C17)
17.8
Test S2 (S2 = O), go to step 17.5 if additional
bytes of S(KA, --U.sub.1) remain to be tested; else,
go to step 19
18
18.1
LOAD (RWMAG .rarw. N)
18.2
Increment RWMAG by 8 (RWMAG .rarw. N + 8)
18.3
Load N + 8 into Microprogram Controller
18.4
RESET (RWMAG .rarw. 0)
18.5
Load Key KB into DES Unit (C8,C13)
18.6
Set RWM for non-inverting read operation
(C9,C10)
18.7
Load 8 bytes of --Udata from RWM into DES Unit
(C11,C14)
18.8
Encipher data (C15)
Steps 18.7 and 18.8 are repeated as necessary until
N + 8 bytes of --Udata have been processed. (A short
block, if one occurs, and chaining linkages are
handled internally by the DES Unit).
18.9 Read final 8 bytes from DES Unit into the
S-Register (C16,C5)
[S-REGISTER .rarw. S(KB, --U)]
19
19.1 LOAD (RWMAG .rarw. N)
19.2 Increment RWMAG by 8 (RWMAG .rarw. N + 8)
19.3 Load N + 8 into Microprogram Controller
19.4 RESET
19.5 Set U/--Dto 1
19.6 Load key KB into DES Unit (C8,C13)
19.7 Set RWM for inverting read operation (C9,C10)
19.8 Load 8 bytes of inverted --Udata from RWM into
DES Unit (C11,C14)
19.9 Encipher data (C15)
Steps 19.8 and 19.9 are repeated as necessary
until N + 8 bytes of --Udata have been processed.
(A short block, if one occurs, and chaining
linkages are handled internally by the DES
Unit).
19.10 READ FINAL 8 bytes from DES Unit into the
S-Register (C16,C5)
[S-REGISTER .rarw. S(KB,.about. -- U)]
20 Set VRDY to 1
21 Set IMPX ADDRESS to 3
Test RQV:
If 0, hold
If 1, continue
22 Read 8 bytes of V data from S-Register to
Host CPU (C17,C18)
23 Clear A- and B-Registers (C7)
24
24.1 CLEAR (Handshake control output lines cleared
to 0)
24.2 Go to step 2
______________________________________
From the above detailed Operational Sequence List for the Verify Unit, it is believed that the operation of the overall system will be clearly apparent to those skilled in the art. Specific Operational Sequence Lists were not given for the Terminal Unit or for the Host CPU since these units are essentially well known in the art. Similarly, how to program such hardware to perform the various operations set forth in the flow chart of FIGS. 5A through 5G is well known. For example, within the terminals, the various operations required could easily be controlled by hardware dedicated keyboard operations or could be done via a microprogram controller such as utilized in the Verify Unit. Similarly, within the Host CPU, the actual operations performed are a relatively simple and straightforward list of fetches, data requests and the transmitting of messages between the User B and the Host upon command and it is believed that such functions are notoriously old per se and that, given the present flow charts, programming for such a verification routine would be extremely straightforward and would vary only with the particular Host CPU architecture, program language, etc., involved. INDUSTRIAL APPLICABILITY The uses of the herein disclosed transaction verification in the modern day business environment could be manifold. As has been reiterated herein, the system assures virtually a foolproof method of guaranteeing both the identity of the sender or originator of a message insofar as a receiver is concerned, while at the same time guaranteeing the integrity of the message to the original sender. This allows the utilization of long distance telecommunications facilities for the real time completion of transactions which could only be performed in the past utilizing much more time consuming and conventional methods, such as electronic mail or by actually having people meet to consummate various transactions. Thus for example, legally binding contracts could be effected by having both parties to the contract send an additional data or message portion to the other, each having his own unique signature appended thereto, plus each party to the transaction would have his own resident copy of the contract, electronically signed by the other party and wherein the actual wording of the contract would be verifiable at any time in the future, if a conflict arose and allegations were made that the wordings were at variance. Similarly, long distance highly verifiable purchase orders could be made between individuals where, due to the nature of the transaction, or the amount of money involved were great, the receiver of such a message would not normally act until the identity of the sender were irrevocably established. The system could also have applicability for such a commercial purpose as telephone ordering (i.e., local terminal) by an individual from a large, centrally located store, wherein both ordering and funds transfer could be handled in a highly reliable manner utilizing various aspects of the presently disclosed system. In short, any area where the identity of the sender and the actual content of the transmitted message must both be firmly established would be possible candidates for use of the present invention. In summary, the present system, as disclosed, prevents masquerading by any party (not having access to the secret keys) even though he has access to eavesdropping equipment over the line. It also prevents the gathering of any useful information via eavesdropping which could be subsequently used to bypass the present security system. The only actual data which could be obtained by an eavesdropper which might or might not prove useful would be the actual message content of the unencrypted portions of the message, i.e., from User A to the Host CPU during the initialization portion of the procedure. It will be readily understood that this could be easily avoided by utilizing further cryptographic transmission security via the system hardware already present in the system. In such cases all messages would be transmitted using an overall system message transmission key (K.sub.T) known to all users and the CPU but not presumptively to an eavesdropper. Such encryption would be superimposed on the message protocol described herein as will be well understood by those skilled in the art. It should also be understood that while the present invention has been specifically set forth and described with reference to a preferred embodiment, it will be readily appreciated by those skilled in the art that many changes in form and detail may be made without departing from the spirit and scope of the present invention as set forth in the appended claims.
|
Same subclass Same class Consider this |
||||||||||