Multiparty Key Exchange

Abstract

This invention pertains to secure communications between multiple parties and/or secure computation or data transmission between multiple computers or multiple vehicles. This invention provides a secure method for three or more parties to establish one or more shared secrets between all parties. In some embodiments, there are less than 40 parties and in other embodiments there are more than 1 million parties that establish a shared secret. In some embodiments, establishing a shared secret among multiple parties provides a method for a secure conference call. In some embodiments, a shared secret is established with multiple computer nodes across the whole earth to help provide a secure Internet infrastructure that can reliably and securely route Internet traffic. In some embodiments, a shared secret is established so that self-driving vehicles may securely communicate and securely coordinate their motion to avoid collisions. In some embodiments, a shared secret is established with multiple computer nodes that participate as a network, performing blockchain computations.

Claims

1. A process comprising: a first party generating one or more private keys; the first party computing one or more public keys by applying mathematical operations to the one or more private keys; the first party sending one or more of its public keys to a second party; a second party generating one or more private keys; the second party computing one or more public keys by applying mathematical operations to the second party's one or more private keys; the second party sending one or more of its public keys to the first party; the first party receiving the second party's one or more public keys; the first party applying mathematical operations between the first party's one or more private keys and the second party's one or more public keys; the mathematical operations resulting in a shared secret for the first party; the second party receiving the first party's one or more public keys; the second party applying mathematical operations between the second party's one or more private keys and the first party's one or more public keys; the mathematical operations resulting in a shared secret for the second party; the first party transforming its shared secret to one or more multiparty private keys that are distinct from the first party's private keys and distinct from the second party's private keys; the first party computing one or more multiparty public keys by applying mathematical operations to the one or more multiparty private keys; the first party sending one or more multiparty public keys to a third party that is distinct from the first party and distinct from the second party; wherein the computing of the one or more public keys by the first party is performed by a machine having a processor system and a memory system, the processor system including one or more processors; wherein the computing of the one or more public keys by the second party is performed by a machine having a processor system and a memory system, the processor system including one or more processors.

2. The process of claim 1 further comprising: a third party generating one or more private keys; the third party computing one or more public keys by applying mathematical operations to the one or more private keys; the third party sending one or more of its public keys to a fourth party; a fourth party generating one or more private keys; the fourth party computing one or more public keys by applying mathematical operations to the fourth party's one or more private keys; the fourth party sending one or more of its public keys to the third party; the third party receiving the fourth party's one or more public keys; the third party applying mathematical operations between the third party's one or more private keys and the fourth party's one or more public keys; the mathematical operations resulting in a shared secret for the third party; the fourth party receiving the third party's one or more public keys; the fourth party applying mathematical operations between the fourth party's one or more private keys and the third party's one or more public keys; the mathematical operations resulting in a shared secret for the fourth party; the third party transforming its shared secret to one or more multiparty private keys that are distinct from the third party's private keys and distinct from the fourth party's private keys; the third party computing one or more multiparty public keys by applying mathematical operations to the one or more multiparty private keys; the third party sending one or more multiparty public keys to a party that is not the third party and not the fourth party; wherein the computing of the one or more public keys by the third party is performed by a machine having a processor system and a memory system, the processor system including one or more processors; wherein the computing of the one or more public keys by the fourth party is performed by a machine having a processor system and a memory system, the processor system including one or more processors.

3. The process of claim 1 further comprising: wherein said mathematical operations are group operations, derived from an elliptic curve.

4. The process of claim 1 further comprising: wherein said mathematical operations are lattice operations.

5. The process of claim 1 further comprising: wherein said mathematical operations are Goppa code operations or McEliece group operations.

6. The process of claim 1 further comprising: the first party sending one or more public keys to a location outside of a sending machine of the first party.

7. The process of claim 1 wherein a non-deterministic process contributes to the generation of the first party's private keys.

8. The process of claim 7 further comprising: the non-deterministic process is based at least on a behavior of photons.

9. The process of claim 8 further comprising: emitting said photons from a light emitting diode.

10. An information system comprising: a first party generating one or more private keys; the first party computing one or more public keys by applying mathematical operations to the one or more private keys; the first party sending one or more of its public keys to a second party; a second party generating one or more private keys; the second party computing one or more public keys by applying mathematical operations to the second party's one or more private keys; the second party sending one or more of its public keys to the first party; the first party receiving the second party's one or more public keys; the first party applying mathematical operations between the first party's one or more private keys and the second party's one or more public keys; the mathematical operations resulting in a shared secret for the first party; the second party receiving the first party's one or more public keys; the second party applying mathematical operations between the second party's one or more private keys and the first party's one or more public keys; the mathematical operations resulting in a shared secret for the second party; the first party transforming its shared secret to one or more multiparty private keys that are distinct from the first party's private keys and distinct from the second party's private keys; the first party computing one or more multiparty public keys by applying mathematical operations to the one or more multiparty private keys; the first party sending one or more multiparty public keys to a third party; wherein the computing of the one or more public keys by the first party is executed by a machine having a processor system and a memory system, the processor system including one or more processors; wherein the computing of the one or more public keys by the second party is executed by a machine having a processor system and a memory system, the processor system including one or more processors.

11. The system of claim 10 further comprising: a third party generating one or more private keys; the third party computing one or more public keys by applying mathematical operations to the one or more private keys; the third party sending one or more of its public keys to a fourth party; a fourth party generating one or more private keys; the fourth party computing one or more public keys by applying mathematical operations to the fourth party's one or more private keys; the fourth party sending one or more of its public keys to the third party; the third party receiving the fourth party's one or more public keys; the third party applying mathematical operations between the third party's one or more private keys and the fourth party's one or more public keys; the mathematical operations resulting in a shared secret for the third party; the fourth party receiving the third party's one or more public keys; the fourth party applying mathematical operations between the fourth party's one or more private keys and the third party's one or more public keys; the mathematical operations resulting in a shared secret for the fourth party; the third party transforming its shared secret to one or more multiparty private keys that are distinct from the third party's private keys and distinct from the fourth party's private keys; the third party computing one or more multiparty public keys by applying mathematical operations to the one or more multiparty private keys; the third party sending one or more multiparty public keys to a party that is distinct from the third party and the fourth party; wherein the computing of the one or more public keys by the third party is performed by a machine having a processor system and a memory system, the processor system including one or more processors; wherein the computing of the one or more public keys by the fourth party is performed by a machine having a processor system and a memory system, the processor system including one or more processors.

12. The system of claim 10 further comprising: wherein said mathematical operations are group operations, derived from an elliptic curve.

13. The system of claim 10 further comprising: wherein said mathematical operations are lattice operations.

14. The system of claim 10 further comprising: wherein said mathematical operations are based on Goppa codes or McEliece group operations.

15. The system of claim 10 further comprising: the first party sending one or more public keys to a location outside of a sending machine of the first party.

16. The system of claim 10 wherein a non-deterministic process contributes to the generation of the first party's private keys.

17. The system of claim 16 further comprising: the non-deterministic process is based at least on a behavior of photons.

18. The system of claim 17 further comprising: emitting said photons from a light emitting diode.

19. An information system comprising: a first party generating one or more private keys; the first party computing one or more public keys by applying mathematical operations to the one or more private keys; the first party sending one or more of its public keys to a second party; a second party generating one or more private keys; the second party computing one or more public keys by applying mathematical operations to the second party's one or more private keys; the second party sending one or more of its public keys to the first party; the first party receiving the second party's one or more public keys; the first party applying mathematical operations between the first party's one or more private keys and the second party's one or more public keys; the mathematical operations resulting in a shared secret for the first party; the second party receiving the first party's one or more public keys; the second party applying mathematical operations between the second party's one or more private keys and the first party's one or more public keys; the mathematical operations resulting in a shared secret for the second party; the first party transforming its shared secret to one or more multiparty private keys that are distinct from the first party's private keys and distinct from the second party's private keys; the first party computing one or more multiparty public keys by applying mathematical operations to the one or more multiparty private keys; the first party sending one or more multiparty public keys to a third party; wherein the computing of the one or more public keys by the first party is performed by a first vehicle having a processor system and a memory system; wherein the computing of the one or more public keys by the second party is performed by a second vehicle having a processor system and a memory system.

20. The system of claim 19 further comprising: a third party generating one or more private keys; the third party computing one or more public keys by applying mathematical operations to the one or more private keys; the third party sending one or more of its public keys to a fourth party; a fourth party generating one or more private keys; the fourth party computing one or more public keys by applying mathematical operations to the fourth party's one or more private keys; the fourth party sending one or more of its public keys to the third party; the third party receiving the fourth party's one or more public keys; the third party applying mathematical operations between the third party's one or more private keys and the fourth party's one or more public keys; the mathematical operations resulting in a shared secret for the third party; the fourth party receiving the third party's one or more public keys; the fourth party applying mathematical operations between the fourth party's one or more private keys and the third party's one or more public keys; the mathematical operations resulting in a shared secret for the fourth party; the third party transforming its shared secret to one or more multiparty private keys that are distinct from the third party's private keys and distinct from the fourth party's private keys; the third party computing one or more multiparty public keys by applying mathematical operations to the one or more multiparty private keys; the third party sending one or more multiparty public keys to a party that is distinct from the third party and the fourth party; wherein the computing of the one or more public keys by the third party is performed by a third vehicle having a processor system and a memory system; wherein the computing of the one or more public keys by the fourth party is performed by a fourth vehicle having a processor system and a memory system.

Description

6 DESCRIPTION OF FIGURES

[0017] In the following figures, although they may depict various examples of the invention, the invention is not limited to the examples depicted in the figures.

[0018] FIG. 1A shows an embodiment of an information system for sending, receiving multiparty public keys and computing a multiparty key exchange.

[0019] FIG. 1B shows an embodiment of a process for computing a multiparty key exchange that can be used in the embodiment of FIG. 1A.

[0020] FIG. 2A shows an embodiment of a computer network transmitting multiparty public keys. In some embodiments, the transmission may be over the Internet or a part of a network that supports an infrastructure such as the electrical grid, a financial exchange, or a power plant, which can be used with the embodiment of FIG. 1A.

[0021] FIG. 2B shows an embodiment of a secure computing area for computing, sending and receiving multiparty keys, which includes a processor, memory and input/output system, which may be the sending and/or receiving machines of FIG. 1A.

[0022] FIG. 3A shows an embodiment of a USB drive that can act as a sending machine and receiving machine to store and protect a user's information.

[0023] FIG. 3B shows an embodiment of an authentication token, which may include the sending and/or receiving machines of FIG. 1A, that contains a computer processor that can compute multiparty keys.

[0024] FIG. 4 shows a mobile phone embodiment 400 that executes a multiparty key exchange for the purpose of a private voice conference call. Mobile phone embodiment 400 transmits the multiparty public keys wirelessly. Mobile phone embodiment 400 may include the sending and/or receiving machines of FIG. 1A.

[0025] FIG. 5a shows step 4 of a 4-party key exchange between Alice, Bob, Fred and Haley.

[0026] FIG. 5b shows step 9 of a 4-party key exchange where Bob sends his multiparty public key to Haley; Haley sends her multiparty public key to Alice; Alice sends her multiparty public key to Fred; and Fred sends his multiparty public key to Bob.

[0027] FIG. 6A shows an embodiment of a non-deterministic generator, based on quantum randomness. Non-deterministic generator 942 is based on the behavior of photons to help generate one or more private keys. Non-deterministic generator 942 contains a light emitting diode 946 that emits photons and a phototransistor 944 that absorbs photons.

[0028] FIG. 6B shows an embodiment of a non-deterministic generator, based on quantum randomness. Non-deterministic generator 952 is based on the behavior of photons to help generate one or more private keys. Non-deterministic generator 952 contains a light emitting diode 956 that emits photons and a phototdiode 954 that absorbs photons.

[0029] FIG. 7 shows a light emitting diode 702, which emits photons. In some embodiments, LED 702 is part of the random number generator, which is used to generate private keys.

[0030] FIG. 8 shows n self-driving vehicles that have used a multiparty key exchange to establish shared secrets between the self-driving vehicles. The shared secrets help prevent a rogue vehicle or rogue communication from an unauthorized vehicle or unauthorized computer from subverting the communication or driving directions of the self-driving vehicles.

7 DETAILED DESCRIPTION

7.1 Information Terms and Definitions

[0031] In this specification, party refers to any number of objects or entities that participate in a multiparty key exchange. A party may be a device such as a USB device or smartcard. A party may be any number of possible devices or computing environments, where private keys and public keys are generated, sent, received and computed. A party may be a computer node in an Internet infrastructure, a computer processor chip in a mobile phone, a computer acting as domain name server, a computer acting as a proxy, a computer chip in an embedded environment, a computer running a Linux operating system, a computer running Apple OS, a router. A party may refer to a computing environment operating inside a drone. A party may refer to a single quantum computer.

[0032] In this specification, multiparty refers to two or more parties. In some embodiments, multiparty may refer to four parties called Alice, Bob, Fred and Haley. In some embodiments, multiparty may refer to one thousand (i.e., 1,000) parties. In some embodiments, multiparty may refer to one million (i.e., 1,000,000) parties. In some embodiments, multiparty may refer to one billion (i.e., 1,000,000,000) parties. When there are a small number of participants in a multiparty key exchange, the human names Alice, Bob, Ella, Fred, Joanne and Kate are used even though each name may refer to one of the aforementioned devices or computing environments. When there is a multiparty exchange that involves a large number of participants, the symbols P.sub.1, P.sub.2, . . . , P.sub.n may be used instead of human names. Thus, P.sub.1 is a symbol that refers to the first party involved in a multiparty key exchange. P.sub.2 is a symbol that refers to the second party involved in a multiparty key exchange. P.sub.3 is a symbol that refers to the third party involved in a multiparty key exchange. P.sub.n is a symbol that refers to the nth party involved in a multiparty key exchange. In an embodiment, the number of distinct parties may be greater than one thousand so that n>1,000. In another embodiment, the number of distinct parties may be greater than one million so that n>1,000,000. In embodiments that have a smaller number of parties, the human names are often used. For example, in a 4-party exchange, the names Alice, Bob, Ella and Fred are used.

[0033] In this specification, the term key is a type of information and is a value or collection of values to which one or more operations are performed. In some embodiments, one or more of these operations are cryptographic operations. {0, 1}.sup.n is the set of all bit-strings of length n. When a public key is represented with bits, mathematically a n-bit key is an element of the collection {0, 1}.sup.n which is the collection of strings of 0's and 1's of length n. For example, the string of 0's and 1's that starts after this colon is a 128-bit key: 01100001 11000110 01010011 01110001 11000101 10001110 11011001 11010101 01011001 01100100 10110010 10101010 01101101 10000111 10101011 00010111. In an embodiment, n=3000 so that a key is a string of 3000 bits. In some embodiments, a public key is larger than 10 million bits.

[0034] In other embodiments, a public key may be a sequence of values that are not represented as bits. Consider the set {A, B, C, D, E}. For example, the string that starts after this colon is a 40-symbol key selected from the set {A, B, C, D, E}: AC DEB AADBC EAEBB AAECB ADDCB BDCCE AAECB EACAE. In an embodiment, a key could be a string of length n selected from {A, B, C, D, E}.sup.n. In an embodiment, n=700 so that the key is a string of 700 symbols where each symbol is selected from {A, B, C, D, E}.

[0035] In this specification, the term public key refers to any kind of public key used in public key cryptography. In an embodiment, public key refers to an RSA public key. (For RSA, see reference [23] with Rivest as an author.) In an embodiment, public key refers to an elliptic curve public key. (See references [24, 25, 26] with authors Silverman, Edwards and Montgomery.) In an embodiment, public key refers to a McEliece public key. (See reference [21] with McEliece as an author.) In an embodiment, public key refers to a lattice-based public key.

[0036] In this specification, the term multiparty public key refers to a public key derived from two or more parties. In this specification, the term multiparty private key refers to a private key derived from two or more parties. In this specification, the term multiparty shared secret refers to a shared secret derived from two or more parties.

[0037] In some embodiments, multiparty public key(s) 109 in FIG. 1A may be read as input by processor system 258 in FIG. 2B, that executes instructions which perform multiparty receiving instructions 116 in FIG. 1A. In some embodiments, multiparty public key(s) 132 in FIG. 1B, may be read as input by processor system 258, that executes instructions which perform multiparty receiving instructions 116.

[0038] In some embodiments, public key(s) 104 are RSA public key(s), which is a well-known public key cryptography [23]. RSA is described from the perspective of Alice. Alice chooses two huge primes p.sub.A and q.sub.A. Alice computes n.sub.A=p.sub.Aq.sub.A and a random number r.sub.A which has no common factor with (p.sub.A1)(q.sub.A1). In other words, 1 is the greatest common divisor of r.sub.A and (p.sub.A1)(q.sub.A1). he Euler-phi function is defined as follows. If k=1, then (k)=1; if k>1, then (k) is the number positive integers i such that i<k and i and k are relatively prime. Relatively prime means the greatest common divisor of i and k is 1. The positive integer e.sub.A is randomly selected such that e.sub.A is relatively prime to (n.sub.A).

[0039] Alice computes (n.sub.A)=n.sub.A+1p.sub.Aq.sub.A. Alice computes the multiplicative inverse of r.sub.A modulo (n.sub.A); the multiplicative inverse is d.sub.A=e.sub.A.sup.1 modulo (n.sub.A). Alice makes public her public key (n.sub.A,r.sub.A): that is, the two positive integers (n.sub.A,r.sub.A) are Alice's public key.

[0040] In an embodiment, random generator 128 generates r.sub.1 . . . r.sub. which is input to private key instructions 124. In an embodiment that hides RSA public keys, private key instruction 124 use r.sub.1 . . . r.sub. to find two huge primes p.sub.A and q.sub.A and a random number r.sub.A relatively prime to (p.sub.A1)(q.sub.A1).

[0041] In an embodiment, random generator 128 and private key instructions 124 generate two huge primes p.sub.A and q.sub.A; compute n.sub.A=p.sub.Aq.sub.A; and randomly choose e.sub.A that is relatively prime to (n.sub.A). In an embodiment, private key instructions 124 compute d.sub.A=e.sub.A.sup.1 modulo (n.sub.A). In an embodiment, an RSA private key is (n.sub.A,d.sub.A). In an embodiment that hides RSA public keys, public key instructions 126 compute RSA public key (n.sub.A,r.sub.A). In an embodiment, positive integer n.sub.A is a string of 4096 bits and r.sub.A is a string of 4096 bits.

[0042] In this specification, the term location may refer to geographic locations and/or storage locations. A particular storage location may be a collection of contiguous and/or noncontiguous locations on one or more machine readable media. Two different storage locations may refer to two different sets of locations on one or more machine-readable media in which the locations of one set may be intermingled with the locations of the other set.

[0043] In this specification, the term machine-readable medium refers to any non-transitory medium capable of carrying or conveying information that is readable by a machine. One example of a machine-readable medium is a computer-readable medium. Another example of a machine-readable medium is paper having holes that are detected that trigger different mechanical, electrical, and/or logic responses. The term machine-readable medium also includes media that carry information while the information is in transit from one location to another, such as copper wire and/or optical fiber and/or the atmosphere and/or outer space.

[0044] In this specification, the term process refers to a series of one or more operations. In an embodiment, process may also include operations or effects that are best described as non-deterministic. In an embodiment, process may include some operations that can be executed by a digital computer program and some physical effects that are non-deterministic, which cannot be executed by a digital computer program and cannot be performed by a finite sequence of processor instructions.

[0045] In this specification, the machine-implemented processes implement algorithms and non-deterministic processes on a machine. The formal notion of algorithm was introduced in Turing's work [4] and refers to a finite machine that executes a finite number of instructions with finite memory. In other words, an algorithm can be executed with a finite number of machine instructions on a processor. Algorithm is a deterministic process in the following sense: if the finite machine is completely known and the input to the machine is known, then the future behavior of the machine can be determined. In contrast, there is hardware that can measure quantum effects from photons (or other physically non-deterministic processes), whose physical process is non-deterministic. The recognition of non-determinism produced by quantum randomness and other quantum embodiments is based on decades of experimental evidence and statistical testing. Furthermore, the quantum theoryderived from the Kochen-Specker theorem and its extensions [2, 3]predicts that the outcome of a quantum measurement cannot be known in advance and cannot be generated by a Turing machine (digital computer program). As a consequence, a physically non-deterministic process cannot be generated by an algorithm: namely, a sequence of operations executed by a digital computer program. FIG. 9A shows an embodiment of a non-deterministic process arising from quantum events; that is, the emission and absorption of photons.

[0046] Some examples of physically non-deterministic processes are as follows. In some embodiments that utilize non-determinism, photons strike a semitransparent mirror and can take two or more paths in space. In one embodiment, if the photon is reflected by the semitransparent mirror, then it takes on one bit value b{0, 1}; if the photon passes through by the semitransparent mirror, then the non-deterministic process produces another bit value 1b. In another embodiment, the spin of an electron may be sampled to generate the next non-deterministic bit. In still another embodiment, a protein, composed of amino acids, spanning a cell membrane or artificial membrane, that has two or more conformations can be used to detect non-determinism: the protein conformation sampled may be used to generate a non-deterministic value in {0, . . . n1} where the protein has n distinct conformations. In an alternative embodiment, one or more rhodopsin proteins could be used to detect the arrival times of photons and the differences of arrival times could generate non-deterministic bits. In some embodiments, a Geiger counter may be used to sample non-determinism.

[0047] In this specification, the term photodetector refers to any type of device or physical object that detects or absorbs photons. A photodiode is an embodiment of a photodetector. A phototransistor is an embodiment of a photodetector. A rhodopsin protein is an embodiment of a photodetector.

7.2 Information System

[0048] FIG. 1A shows an information system 100 for executing a multiparty key exchange in a manner that is expected to be secure. Information system 100 includes one or more private keys 103 and one or more corresponding multiparty public keys 104, and multiparty sending instructions 106, a sending machine 102, multiparty public key(s) 109 and a transmission path 110, a receiving machine 112, multiparty receiving instructions 116, multiparty public key(s) 114. In other embodiments, information system 100 may not have all of the components listed above or may have other components instead of and/or in addition to those listed above.

[0049] Information system 100 may be a system for transmitting multiparty public key(s). Multiparty public key(s) 104 refers to information that is intended for a multiparty key exchange. In some embodiments, multiparty public key(s) 104 are intended to be delivered to another location, software unit, machine, person, or other entity.

[0050] In some embodiments, multiparty public key(s) 104 may serve as part of a multiparty key exchange. In an embodiment, multiparty public key(s) 104 may be transmitted wirelessly between satellites. Multiparty public key(s) 104 may be represented in analog form in some embodiments and may be represented in digital form. In an embodiment, the public key(s) may be one or more RSA public keys based on huge prime numbers. In an another embodiment, the public key(s) may be one or more elliptic curve public keys, computed from an elliptic curve over a finite field.

[0051] In information system 100, private keys 103 are used to help compute multiparty public key(s) 104. Multiparty public key(s) 104 may be a collection of multiple, blocks of information, an entire sequence of public keys, a segment of public keys, or any other portion of one or more public keys. When there is more than one public key, multiparty public keys 104 may be computed from distinct commutative groups, as described in section 7.10. For example, one commutative group may be based on an elliptic curve over a finite field; another commutative group may be based on multiplication modulo, as used in RSA; another commutative group may be based on Goppa codes; another commutative group may be based on lattices.

[0052] Multiparty sending instructions 106 may be a series of steps that are performed on multiparty public keys 104. In one embodiment, the term process refers to one or more instructions for sending machine 102 to execute the series of operations that may be stored on a machine-readable medium. Alternatively, the process may be carried out by and therefore refer to hardware (e.g., logic circuits) or may be a combination of instructions stored on a machine-readable medium and hardware that cause the operations to be executed by sending machine 102 or receiving machine 112. Public key(s) 104 may be input for multiparty sending instructions 106. The steps that are included in multiparty sending instructions 106 may include one or more mathematical operations and/or one or more other operations.

[0053] As a post-processing step, one-way hash function 948 may be applied to a sequence of random events such as quantum events (non-deterministic) generated by non-deterministic generator 942 in FIG. 9A. As a post-processing step, one-way hash function 948 may be applied to a sequence of random events such as quantum events (non-deterministic) generated by non-deterministic generator 952 in FIG. 9B.

[0054] In FIG. 1B receiving/sending machine 122 may implement multiparty sending instructions 106 in FIG. 1A. In some embodiments, random number generator 128 help generate randomness that is used by private key instructions 130. In some embodiments, receiving/sending machine 122 requests random number generator 128 and private key instructions 124 to help generate one or more private keys 103 that are used to compute public keys 104. In an embodiment, non-deterministic generator 942 (FIG. 9A) may be part of random generator 128. In an embodiment, non-deterministic generator 952 (FIG. 9B) may be part of random generator 128.

[0055] Sending machine 102 may be an information machine that handles information at or is associated with a first location, software unit, machine, person, sender, or other entity. Sending machine 102 may be a computer, a phone, a mobile phone, a telegraph, a satellite, or another type of electronic device, a mechanical device, or other kind of machine that sends information. Sending machine 102 may include one or more processors and/or may include specialized circuitry for handling information. Sending machine 102 may receive public key(s) 104 from another source (e.g., a transducer such as a microphone which is inside mobile phone 402 or 502 of FIG. 4), may produce all or part of public key(s) 104, may implement multiparty sending instructions 106, and/or may transmit the output to another entity. In another embodiment, sending machine 102 receives public key(s) 104 from another source, while multiparty sending instructions 106 and the delivery of the output of multiparty sending instructions 106 are implemented manually. In another embodiment, sending machine 102 implements multiparty sending instructions 106, having multiparty public key(s) 104 entered, via a keyboard (for example) or via a mobile phone microphone, into sending machine 102. In another embodiments, sending machine 102 receives output from multiparty sending instructions 106 and sends the output to another entity.

[0056] Sending machine 102 may implement any of the multiparty key exchange methods described in this specification. In some embodiments, receiving/sending machine 122, shown in FIG. 1B, generates one or more private keys 103 from private key instructions 124 and random generator 128; computes one or more multiparty public keys 104 with multiparty public key instructions 126.

[0057] Transmission path 110 is the path taken by multiparty public key(s) 109 to reach the destination to which multiparty public key(s) 109 were sent. Transmission path 110 may include one or more networks, as shown in FIG. 2A. In FIG. 2A, network 212 may help support transmission path 110. For example, transmission path 110 may be the Internet, which is implemented by network 212; for example, transmission path 110 may be wireless using voice over Internet protocol, which is implemented by network 212. Transmission path 110 may include any combination of any of a direct connection, hand delivery, vocal delivery, one or more Local Area Networks (LANs), one or more Wide Area Networks (WANs), one or more phone networks, including paths under the ground via fiber optics cables and/or one or more wireless networks, and/or wireless inside and/or outside the earth's atmosphere.

[0058] Receiving machine 112 may be an information machine that handles information at the destination of an multiparty public key(s) 109. Receiving machine 112 may be a computer, a phone, a telegraph, a router, a satellite, or another type of electronic device, a mechanical device, or other kind of machine that receives information. Receiving machine 112 may include one or more processors and/or specialized circuitry configured for handling information, such as multiparty public key(s) 109. Receiving machine 112 may receive multiparty public key(s) 109 from another source and/or reconstitute all or part of multiparty public key(s) 109. Receiving machine 112 may implement any of the multiparty key exchange methods described in this specification and is capable of receiving any multiparty public keys from sending machine 102 and multiparty sending instructions 106.

[0059] In one embodiment, receiving machine 112 only receives public keys 109 from transmission path 110, while multiparty sending instructions 106 is implemented manually and/or by another information machine. In another embodiment, receiving machine 112 implements multiparty receiving instructions 116 that reproduces all or part of public key(s) 104, referred to as multiparty public key(s) 114 in FIG. 1A. In another embodiment, receiving machine 112 receives multiparty public key(s) 109 from transmission path 110, and reconstitutes all or part of multiparty public key(s) 114 using multiparty receiving instructions 116. Multiparty receiving instructions 116 may store or process any of the multiparty public keys described in this specification.

[0060] Receiving machine 112 may be identical to sending machine 102. For example, receiving machine 112 may receive 104 from another source, produce all or part of multiparty public key(s) 104, and/or implement multiparty sending instructions 106. Similar to sending machine 102, receiving machine 112 may create random private keys and compute unpredictable multiparty public key(s). Receiving machine 112 may transmit the output of multiparty receiving instructions 116, via transmission path 110 to another entity and/or receive multiparty public key(s) 109 (via transmission path 110) from another entity. Receiving machine 112 may present public key(s) 109 for use as input to multiparty receiving instructions 116.

7.3 PROCESSOR, MEMORY and INPUT/OUTPUT HARDWARE

[0061] Information system 200 illustrates some of the variations of the manners of implementing information system 100. Sending machine 202 is one embodiment of sending machine 101. Sending machine 202 may be a secure USB memory storage device as shown in 3A. Sending machine 202 may be an authentication token as shown in FIG. 3B. A mobile phone embodiment of sending machine 202 is shown in FIG. 4.

[0062] Sending machine 202 or sending machine 400 may communicate wirelessly with computer 204. In an embodiment, computer 204 may be a call station for receiving multiparty public key 109 from sending machine 400. A user may use input system 254 and output system 252 of sending machine (mobile phone) 400 to transmit multiparty public key to a receiving machine that is a mobile phone. In an embodiment, input system 254 in FIG. 2B includes a microphone that is integrated with sending machine (mobile phone) 400. In an embodiment, output system 252 in FIG. 2B includes a speaker that is integrated with sending machine (mobile phone) 400. In another embodiment, sending machine 202 is capable of being plugged into and communicating with computer 204 or with other systems via computer 204.

[0063] Computer 204 is connected to system 210, and is connected, via network 212, to system 214, system 216, and system 218, which is connected to system 220. Network 212 may be any one or any combination of one or more Local Area Networks (LANs), Wide Area Networks (WANs), wireless networks, telephones networks, and/or other networks. System 218 may be directly connected to system 220 or connected via a LAN to system 220. Network 212 and system 214, 216, 218, and 220 may represent Internet servers or nodes that route multiparty public key(s) 109 received from sending machine 400 shown in FIG. 4. In FIG. 2A, system 214, 216, 218, and system 220 and network 212 may together serve as a transmission path 110 for multiparty public key(s) 109. In an embodiment, system 214, 216, 218, and system 220 and network 212 may execute the Internet protocol stack in order to serve as transmission path 110 for multiparty public key 109. In an embodiment, multiparty public key(s) 109 may be one or more public keys computed from elliptic curve computations over a finite field. In an embodiment, multiparty public key(s) 109 may be one or more public keys computed using algebraic coding theory such as McEliece public key cryptography. In an embodiment, multiparty public key 109 may sent via TCP/IP or UDP. In an embodiment, multiparty public key 109 may be sent by email. In an embodiment, multiparty public key 109 may be represented as ASCII text sent from sending machine 400.

[0064] In FIG. 1B, receiving/sending machine 122 may be implemented by any of, a part of any of, or any combination of any of system 210, network 212, system 214, system 216, system 218, and/or system 220. As an example, routing information of transmission path 110 may be sent with receiving/sending machine 122 that executes in system computer 210, network computers 212, system computer 214, system computer 216, system computer 218, and/or system computer 220. multiparty sending instructions 106 may be executed inside sending machine 400 and multiparty receiving instructions 116 may be executed inside receiving machine 400 in FIG. 4.

[0065] In an embodiment, multiparty sending instructions 106 and multiparty receiving instructions 116 execute in a secure area of processor system 258 of FIG. 2B. In an embodiment, specialized hardware in processor system 258 may be implemented to speed up the computation of shared secret instructions 130 in FIG. 1B. In an embodiment, this specialized hardware in processor system 258 may be embodied as an ASIC (application specific integrated circuit) that computes SHA-1 and/or SHA-512 and/or Keccak and/or BLAKE and/or JH and/or Skein that help execute one-way hash function 948 in non-deterministic generator 942 or one-way hash function 958 in non-deterministic generator 952 or one-way hash instructions 964 in deterministic generator 962.

[0066] In an embodiment, specialized hardware in processor system 258 may be embodied as an ASIC (application specific integrated circuit) that computes SHA-1 and/or SHA-512 and/or Keccak and/or BLAKE and/or JH and/or Skein that help execute the HMAC function in processes 1 and 2. An ASIC chip can increase the execution speed and protect the privacy of multiparty sending instructions 106 and multiparty receiving instructions 116.

[0067] In an embodiment, input system 254 of FIG. 2B receives public key(s) 104 and processor system 258 computes them with receiving/sending machine 122. Output system 252 sends the multiparty public key(s) 109 to a telecommunication network 212. In an embodiment, memory system 256 stores private key instructions 124, public key instructions 126 and shared secret instructions 130.

[0068] In an embodiment, memory system 256 of FIG. 2B stores shared secret key(s) 132. In an embodiment, memory system 256 stores multiparty public key(s) 109 that is waiting to be sent to output system 252 and sent out along transmission path 110, routed and served by system computers 210, 214, 216, 218 and 220 and network 212.

7.4 Non-Deterministic Generators

[0069] FIG. 6A shows an embodiment of a non-deterministic generator 642 arising from quantum events: that is, random number generator 128 uses the emission and absorption of photons for its non-determinism. In FIG. 6A, phototransistor 644 absorbs photons emitted from light emitting diode 654. In an embodiment, the photons are produced by a light emitting diode 646. In FIG. 9B, non-deterministic generator 652 has a photodiode 654 that absorbs photons emitted from light emitting diode 656. In an embodiment, the photons are produced by a light emitting diode 656.

[0070] FIG. 7 shows a light emitting diode (LED) 702. In an embodiment, LED 702 emits photons and is part of the non-deterministic generator 642 (FIG. 6A). In an embodiment, LED 702 emits photons and is part of the non-deterministic generator 652 (FIG. 6B). LED 702 contains a cathode, a diode, an anode, one terminal pin connected to the cathode and one terminal pin connected to the anode, a p-layer of semiconductor, an active region, an n-layer of semiconductor, a substrate and a transparent plastic case. The plastic case is transparent so that a photodetector outside the LED case can detect the arrival times of photons emitted by the LED. In an embodiment, photodiode 644 absorbs photons emitted by LED 702. In an embodiment, phototransistor 654 absorbs photons emitted by LED 702.

[0071] The emission times of the photons emitted by the LED experimentally obey the energy-time form of the Heisenberg uncertainty principle. The energy-time form of the Heisenberg uncertainty principle contributes to the non-determinism of random number generator 128 because the photon emission times are unpredictable due to the uncertainty principle. In FIGS. 6A and 6B, the arrival of photons are indicated by a squiggly curve with an arrow and h next to the curve. The detection of arrival times of photons is a non-deterministic process. Due to the uncertainty of photon emission, the arrival times of photons are quantum events.

[0072] In FIGS. 6A and 6B, hv refers to the energy of a photon that arrives at photodiode 644, respectively, where h is Planck's constant and v is the frequency of the photon. In FIG. 6A, the p and n semiconductor layers are a part of a phototransistor 644, which generates and amplifies electrical current, when the light that is absorbed by the phototransistor. In FIG. 6B, the p and n semiconductor layers are a part of a photodiode 654, which absorbs photons that strike the photodiode.

[0073] A photodiode is a semiconductor device that converts light (photons) into electrical current, which is called a photocurrent. The photocurrent is generated when photons are absorbed in the photodiode. Photodiodes are similar to standard semiconductor diodes except that they may be either exposed or packaged with a window or optical fiber connection to allow light (photons) to reach the sensitive part of the device. A photodiode may use a PIN junction or a p-n junction to generate electrical current from the absorption of photons. In some embodiments, the photodiode may be a phototransistor.

[0074] A phototransistor is a semiconductor device comprised of three electrodes that are part of a bipolar junction transistor. Light or ultraviolet light activates this bipolar junction transistor. Illumination of the base generates carriers which supply the base signal while the base electrode is left floating. The emitter junction constitutes a diode, and transistor action amplifies the incident light inducing a signal current.

[0075] When one or more photons with high enough energy strikes the photodiode, it creates an electron-hole pair. This phenomena is a type of photoelectric effect. If the absorption occurs in the junction's depletion region, or one diffusion length away from the depletion region, these carriers (electron-hole pair) are attracted from the PIN or p-n junction by the built-in electric field of the depletion region. The electric field causes holes to move toward the anode, and electrons to move toward the cathode; the movement of the holes and electrons creates a photocurrent. In some embodiments, the amount of photocurrent is an analog value, which can be digitized by a analog-to-digital converter. In some embodiments, the analog value is amplified before being digitized. The digitized value is what becomes the random number. In some embodiments, a one-way hash function 648 or 658 may also be applied to post-process the raw random bits to produce private keys used by processes 1 and 2. In some embodiments, a one-way hash function may be applied using one-way hash instructions 664 to the random digitized output of non-deterministic generator 642 before executing private key(s) instructions 124, used by processes 1 and 2.

[0076] In an embodiment, the sampling of the digitized photocurrent values may converted to threshold times as follows. A photocurrent threshold is selected as a sampling parameter. If a digitized photocurrent value it is above at time t.sub.1, then t.sub.1 is recorded as a threshold time. If the next digitized photocurrent value i.sub.2 above occurs at time t.sub.2, then t.sub.2 is recorded as the next threshold time. If the next digitized value i.sub.3 above occurs at time t.sub.3, then t.sub.3 is recorded as the next threshold time.

[0077] After three consecutive threshold times are recorded, these three times can determine a bit value as follows. If t.sub.2t.sub.1>t.sub.3t.sub.2, then non-deterministic generator 642 or 652 produces a 1 bit. If t.sub.2t.sub.1<t.sub.3t.sub.2, then non-deterministic generator 642 or 652 produces a 0 bit. If t.sub.2t.sub.1=t.sub.3t.sub.2, then no random bits are produced. To generate the next bit, non-deterministic generator 642 or 652 continues the same sampling steps as before and three new threshold times are produced and compared.

[0078] In an alternative sampling method, a sample mean is established for the photocurrent, when it is illuminated with photons. In some embodiments, the sampling method is implemented as follows. Let i.sub.1 be the photocurrent value sampled at the first sampling time. i.sub.1 is compared to . is selected as a parameter in the sampling method that is much smaller number than . If i.sub.1 is greater than +, then a 1 bit is produced by the non-deterministc generator 642 or 652. If i.sub.1 is less than , then a 0 bit is produced by non-deterministc generator 642 or 652. If it is in the interval [, +], then NO bit is produced by non-deterministc generator 642 or 652.

[0079] Let i.sub.2 be the photocurrent value sampled at the next sampling time. i.sub.2 is compared to . If i.sub.2 is greater than +, then a 1 bit is produced by the non-deterministc generator 642 or 652. If i.sub.2 is less than , then a 0 bit is produced by the non-deterministc generator 642 or 652. If i.sub.2 is in the interval [, +], then NO bit is produced by the non-deterministc generator 642 or 652. This alternative sampling method continues in the same way with photocurrent values i.sub.3, i.sub.4, and so on. In some embodiments, the parameter is selected as zero instead of a small positive number relative to .

[0080] Some alternative hardware embodiments of random number generator 128 (FIG. 1B) are described below. In some embodiments that utilize non-determinism to produce randomness, a semitransparent mirror may be used. In some embodiments, the mirror contains quartz (glass). The photons that hit the mirror may take two or more paths in space. In one embodiment, if the photon is reflected, then the random number generator creates the bit value b{0, 1}; if the photon is transmitted, then the random number generator creates the other bit value 1b. In another embodiment, the spin of an electron may be sampled to generate the next non-deterministic bit. In still another embodiment of a random number generator, a protein, composed of amino acids, spanning a cell membrane or artificial membrane, that has two or more conformations can be used to detect non-determinism: the protein conformation sampled may be used to generate a random number value in {0, . . . n1} where the protein has n distinct conformations. In an alternative embodiment, one or more rhodopsin proteins could be used to detect the arrival times t.sub.1<t.sub.2<t.sub.3 of photons and the differences of arrival times (t.sub.2t.sub.1>t.sub.3t.sub.2 versus t.sub.2t.sub.1<t.sub.3t.sub.2) could generate non-deterministic bits that produce a random number.

[0081] In some embodiments, the seek time of a hard drive can be used as non-deterministic generator as the air turbulence in the hard drive affects the seek time in a non-deterministic manner. In some embodiments, local atmospheric noise can be used as a source of randomness. For example, the air pressure, the humidity or the wind direction could be used. In other embodiments, the local sampling of smells based on particular molecules could also be used as a source of randomness.

[0082] In some embodiments, a Geiger counter may be used to sample non-determinism and generate randomness. In these embodiments, the unpredictability is due to radioactive decay rather than photon emission, arrivals and detection.

7.5 One-Way Hash Functions

[0083] In FIG. 9, one-way hash function 148 may include one or more one-way functions. A one-way hash function , has the property that given an output value z, it is computationally intractable to find an information element m.sub.z such that (m.sub.z)=z. In other words, a one-way function is a function that can be easily computed, but that its inverse .sup.1 is computationally intractable to compute [6]. A computation that takes 10.sup.101 computational steps is considered to have computational intractability of 10.sup.101.

[0084] More details are provided on computationally intractable. In an embodiment, there is an amount of time T that encrypted information must stay secret. If encrypted information has no economic value or strategic value after time T, then computationally intractable means that the number of computational steps required by all the world's computing power will take more time to compute than time T. Let C(t) denote all the world's computing power at the time t in years.

[0085] Consider an online bank transaction that encrypts the transaction details of that transaction. Then in most embodiments, the number of computational steps that can be computed by all the world's computers for the next 30 years is in many embodiments likely to be computationally intractable as that particular bank account is likely to no longer exist in 30 years or have a very different authentication interface.

[0086] To make the numbers more concrete, the 2013 Chinese supercomputer that broke the world's computational speed record computes about 33,000 trillion calculations per second [7]. If T=1 one year and we can assume that there are at most 1 billion of these supercomputers. (This can be inferred from economic considerations, based on a far too low 1 million dollar price for each supercomputer. Then these 1 billion supercomputers would cost 1,000 trillion dollars.). Thus, C(2014)1 year is less than 10.sup.93310.sup.15360024365=1.0410.sup.33 computational steps.

[0087] As just discussed, in some embodiments and applications, computationally intractable may be measured in terms of how much the encrypted information is worth in economic value and what is the current cost of the computing power needed to decrypt that encrypted information. In other embodiments, economic computational intractability may be useless. For example, suppose a family wishes to keep their child's whereabouts unknown to violent kidnappers. Suppose T=100 years because it is about twice their expected lifetimes. Then 100 yearsC(2064) is a better measure of computationally intractible for this application. In other words, for critical applications that are beyond an economic value, one should strive for a good estimate of the world's computing power.

[0088] One-way functions that exhibit completeness and a good avalanche effect or the strict avalanche criterion [8] are preferable embodiments: these properties are favorable for one-way hash functions. The definition of completeness and a good avalanche effect are quoted directly from [8]: [0089] If a cryptographic transformation is complete, then each ciphertext bit must depend on all of the plaintext bits. Thus, if it were possible to find the simplest Boolean expression for each ciphertext bit in terms of plaintext bits, each of those expressions would have to contain all of the plaintext bits if the function was complete. Alternatively, if there is at least one pair of n-bit plaintext vectors X and X.sub.i that differ only in bit i, and (X) and (X.sub.i) differ at least in bit j for all {(i,j): 1i,jn}, the function must be complete. [0090] For a given transformation to exhibit the avalanche effect, an average of one half of the output bits should change whenever a single input bit is complemented. In order to determine whether a mn (m input bits and n output bits) function satisfies this requirement, the 2.sup.m plaintext vectors must be divided into 2.sup.m-1 pairs, X and X.sub.j such that X and X.sub.j differ only in bit i. Then the 2.sup.m-1 exclusive-or sums V.sub.i=(X)(X.sub.i) must be calculated. These exclusive-or sums will be referred to as avalanche vectors, each of which contains n bits, or avalanche variables. If this procedure is repeated for all i such that 1im and one half of the avalanche variables are equal to 1 for each i, then the function has a good avalanche effect. Of course this method can be pursued only if m is fairly small; otherwise, the number of plaintext vectors becomes too large. If that is the case then the best that can be done is to take a random sample of plaintext vectors X, and for each value i calculate all avalanche vectors V.sub.i. If approximately one half the resulting avalanche variables are equal to 1 for values of i, then we can conclude that the function has a good avalanche effect.

[0091] A hash function, also denoted as , is a function that accepts as its input argument an arbitrarily long string of bits (or bytes) and produces a fixed-size output of information. The information in the output is typically called a message digest or digital fingerprint. In other words, a hash function maps a variable length m of input information to a fixed-sized output, (m), which is the message digest or information digest. Typical output sizes range from 160 to 512 bits, but can also be larger. An ideal hash function is a function , whose output is uniformly distributed in the following way: Suppose the output size of is n bits. If the message m is chosen randomly, then for each of the 2.sup.n possible outputs z, the probability that (m)=z is 2.sup.n. In an embodiment, the hash functions that are used are one-way.

[0092] A good one-way hash function is also collision resistant. A collision occurs when two distinct information elements are mapped by the one-way hash function to the same digest. Collision resistant means it is computationally intractable for an adversary to find collisions: more precisely, it is computationally intractable to find two distinct information elements m.sub.1, m.sub.2 where m.sub.1m.sub.2 and such that (m.sub.1)=(m.sub.2).

[0093] A number of one-way hash functions may be used to implement one-way hash function 148. In an embodiment, SHA-512 can implement one-way hash function 148, designed by the NSA and standardized by NIST [15]. The message digest size of SHA-512 is 512 bits. Other alternative hash functions are of the type that conform with the standard SHA-384, which produces a message digest size of 384 bits. SHA-1 has a message digest size of 160 bits. An embodiment of a one-way hash function 148 is Keccak [10]. An embodiment of a one-way hash function 148 is BLAKE [11]. An embodiment of a one-way hash function 148 is Grstl [12]. An embodiment of a one-way hash function 148 is JH [13]. Another embodiment of a one-way hash function is Skein [14].

7.6 Algebraic Groups

[0094] In this section, some terms and definitions about algebraic groups are described that are relevant to various embodiments, including the mathematical operations applied and/or computed in these embodiments. It is helpful to review the mathematical definition of a group. A group G is a set with a binary operation * such that the following four properties hold:

[0095] I. Binary operation * is closed on G. This means a*b lies in G for all elements a and b in G.

[0096] II. Binary operation * is associative. That is, a*(b*c)=(a*b)*c for all elements a, b, and c in G.

[0097] III. There is a unique identity element e in G, where a*e=e*a=a.

[0098] IV. Each element a in G has a unique inverse denoted as a.sup.1. This means a a.sup.1=a.sup.1*a=e.

[0099] Group G is a commutative group when a*b=b*a for every pair of elements a and b selected from G. The product g*g is denoted as g.sup.2; g*g*g*g*g is denoted as g.sup.5. Sometimes, the binary operation * will be omitted so that a*b is expressed as ab.

[0100] The integers { . . . , 2, 1, 0, 1, 2, . . . } with respect to the binary operation+(integer addition) are an example of an infinite commutative group. It is commutative because m+n=n+m for any two integers m and n. 0 is the identity element. For example, the inverse of 5 is 5 and the inverse of 107 is 107.

[0101] The set of permutations on n elements {1, 2, . . . , n}, denoted as S.sub.n, is an example of a finite group with n! elements where the binary operation is function composition. Each element of S.sub.n is a function p:{1, 2, . . . , n}.fwdarw.{1, 2, . . . , n} that is 1 to 1 and onto. In this context, p is called a permutation. The identity permutation e is the identity element in S.sub.n, where e(k)=k for each k in {1, 2, . . . , n}.

[0102] If H is a non-empty subset of a group G and H is a group with respect to the binary group operation of G, then H is called a subgroup of G. H is a proper subgroup of G if H is not equal to G (i.e., H is a proper subset of G). G is a cyclic group if G has no proper subgroups.

[0103] Define A.sub.n= custom-character [0]={[1], . . . , [n1]}; in other words, A.sub.n is the integers modulo n with equivalence class [0] removed. If n=5, [4]*[4]=[16 mod 5]=[1] in (, *) Similarly, [3]*[4]=[12 mod 5]=[2] in (.sub.5, *). Let (a, n) represent the greatest common divisor of a and n. Let U.sub.n={[a]A.sub.n:(a, n)=1}. Define binary operator on U.sub.n as [a]*[b]=[ab], where ab is the multiplication of positive integers a and b. Then (U.sub.n, *) is a finite, commutative group.

[0104] Suppose g lies in group (G, *). This multiplicative notation works as follows: g.sup.2=g*g. Also g.sup.3=g*g*g; g.sup.6=g*g*g*g*g*g and so on. In section 7.10, this multiplicative notation (superscripts) is used in the description of multiparty key exchanges.

[0105] There are an infinite number of finite groups and an infinite number of these groups are huge. The notion of huge means the following: if 2.sup.1024 is considered to be a huge number based on the computing power of current computers, then there are still an infinite number of finite, commutative groups with each group containing more than 2.sup.1024 elements.

7.7 Elliptic Curve Group Operations

[0106] For elliptic curves [24] the mathematical operationsderived from the Weierstrauss curveare as follows:

[0107] 1. Select two geometric points p.sub.1, p.sub.2 on the Weierstrauss curve.

[0108] 2. Draw a line through these two points p.sub.1 and p.sub.2.

[0109] 3. Compute the new intersection point of the line with the Weierstrauss curve.

[0110] 4. Reflects this new intersection point about the y axis, resulting in the point p.sub.new=p.sub.1*p.sub.2

[0111] 5. The new point p.sub.new is the result of the mathematical operations on points p.sub.1 and p.sub.2.

[0112] In the special case, when the two points are the same point (i.e., p.sub.1=p.sub.2), the mathematical operations consist of the following. A tangent line to the Weierstrauss curve at p.sub.1 is computed. Then a new intersection point with the tangent line and the Weierstrauss curve is computed. Then a reflection is applied to this new intersection point, resulting in p.sub.new.

[0113] In another embodiment, elliptic curve computations are performed on an Edwards curve over a finite field. When the field K does not have characteristic two, an Edwards curve is of the form: x.sup.2+y.sup.2=1+dx.sup.2y.sup.2, where d is an element of the field K not equal to 0 and not equal to 1. For an Edwards curve of this form, the binary operator * is defined as

[00002] $(x_{1}, y_{1}) * (x_{2}, y_{2}) = (\frac{x_{1} .Math. y_{2} + x_{2} .Math. y_{1}}{1 + {dx}_{1} .Math. x_{2} .Math. y_{1} .Math. y_{2}}, \frac{y_{1} .Math. y_{2} - x_{1} .Math. x_{2}}{1 - {dx}_{1} .Math. x_{2} .Math. y_{1} .Math. y_{2}}),$

where the elements of the group are the points (x.sub.1,y.sub.1) and (x.sub.2,y.sub.2). The definition of * defines elliptic curve computations that form a commutative group. For more information on Edwards curves, refer to the math journal paper [25].

[0114] In an alternative embodiment, elliptic curve computations are performed on a Montgomery curve over a finite field. Let K be the finite field over which the elliptic curve is defined. A Montgomery curve is of the form By.sup.2=x.sup.3+Ax.sup.2+x, for some field elements A, B chosen from K where B(A.sup.24)0. For more information on Montgomery curves, refer to the publication [26].

7.8 Goppa Code Operations

[0115] Goppa codes are covered in Chapter 8 of reference [20]. This section summarizes how Goppa codes and the mathematical operations described below can used in a public-key cryptosystem, conceived by McEliece [21]. As of this time, this McEliece public-key cryptosystem is considered resistant to known quantum computing algorithms.

[0116] Corresponding to each irreducible polynomial of degree t over GF(2.sup.m), there exists a binary irreducible Goppa code of length n=2.sup.m, such that the Goppa code's dimension kntm. Furthermore, this Goppa code is capable of correcting any pattern with t or fewer errors. Moreover, there exists a fast algorithm for decoding these Goppa codes: the run time is O(nt). This fast algorithm is called Patterson's algorithm. See problem 8.18 in reference [20].

[0117] Suppose that the information system chooses a large enough value of n and t, and then randomly selects an irreducible polynomial of degree t over GF(2.sup.m). The value

[00003] $\frac{1}{t}$

is close to the probability that a randomly selected polynomial of degree t is irreducible. There is a fast algorithm for testing irreducibility, shown in chapter 6 of reference [17]. Next, the information system (Alice) computes a kn generator matrix G for the code which is canonical, for example, row-reduced echelon form.

[0118] After generating G, Alice's information system scrambles G by randomly selecting a dense kk nonsingular matrix S and randomly selecting an nn permutation matrix P. Next, Alice's information system computes G=S*G*P, where * represents matrix multiplication. The result G generates a linear code with the same rate and minimum distance as the code generated by G. Matrix G is called the public generator matrix and acts as Alice's public key.

[0119] Alice transmits her public key G to Bob. Bob is able to encrypt his plaintext data using the following encryption algorithm, along with Alice's public key G.

[0120] McEliece Encryption Algorithm. [0121] 1. Bob divides the plaintext data into k-bit blocks. [0122] 2. Suppose u is a plaintext block that Bob wishes to securely send to Alice. Bob computes the vector x=u*G+z, where G is a public generator matrix, and z is a randomly generated random vector of length n and weight t. Bob keeps z local. [0123] 3. Bob transmits encrypted data x to Alice.

[0124] Alice can efficiently recover u by performing the following decryption algorithm.

[0125] McEliece Decryption Algorithm. [0126] 1. Alice computes x=x*P.sup.1, where P.sup.1 is the inverse of permutation matrix P. [0127] 2. x is a codeword for the Goppa code previously chosen. Alice executes Patterson's algorithm to help compute u=u*S [0128] 3. Alice recovers a by computing u=u*S.sup.1, where S.sup.1 is the inverse matrix of the nonsingular matrix S, randomly selected by her information system.

7.9 Lattice Operations

[0129] This section describes lattices and how public keys can be computed from mathematical operations based on lattices. In some embodiments, the binary operation of vector addition on a lattice makes the lattice into a commutative group. The symbol custom-character represents the real numbers. The symbol represents the integers.

[0130] Let L be subset of points of the vector space custom-character .sup.n that contains the origin (0, 0, . . . , 0). Then the set L is a lattice if it satisfies the following two conditions. [0131] 1. L is a group with vector addition as its binary operation. [0132] 2. There exists an r>0, such that for each point x in L, the open ball with center x and radius r contains no other points of L besides x.

[0133] It is well-known [22] that if L is a lattice in an n-space (n-dimensional vector space) then there exists k linearly independent vectors v.sub.1, v.sub.2 . . . v.sub.k with kn such that L consists of all points of the form

m.sub.1v.sub.1+m.sub.2v.sub.2+ . . . +m.sub.kv.sub.k

where each m.sub.i is an integer.

[0134] Let, custom-character .sub.q.sup.mn be the set of a n rows of m tuples of integers modulo q. The following math operations make up a public cryptographic system, called LWE (i.e., Learning with Errors) based on lattices. The errors are assigned according to the noise distribution such that

[00004] $.Math. e .Math. \frac{q}{4 .Math. m}$

with high probability.

[0135] LWE Key-Pair Generation. [0136] 1. n is the input parameter for Alice. [0137] 2. A in custom-character .sub.q.sup.mn is randomly selected by Alice and is open to the public. A is an nm matrix with entries in .sub.q, selected according to a uniform distribution. [0138] 3. Alice selects e in .sub.q.sup.m, according to a uniform distribution. [0139] 4. Alice's secret s is randomly selected in custom-character .sub.q.sup.n, according to a uniform distribution. [0140] 5. Alice's key pair is (p, s), with public key p=(A, s.sup.T*A+e.sup.T). Note s.sup.T*A is vector s.sup.T multiplied by matrix A. Expression s.sup.T is the transpose of vector s. Expression e.sup.T is the transpose of vector e.

[0141] LWE Encryption with the Public Key. [0142] 1. Bob receives as input Alice's public key (A, b.sup.T) and plaintext message m in {0, 1}. [0143] 2. Bob randomly samples m-bit vector r in {0, 1}.sup.m and computes ciphertext

[00005] $(A * r, b^{T} * r + m .Math. .Math. \frac{q}{2} .Math.) .$

7.10 Multiparty Key Exchange

Multiparty Process 1. A 4-Party Key Exchange

[0144] Step 1. Alice, Bob, Haley and Fred agree on a common generator g in commutative group (G,*). [0145] Alice, Bob, Haley and Fred agree on a shared secret transformation function . [0146] Shared secret transformation function maps a shared secret to a multiparty private key. [0147] Step 2. Alice generates her private key a. [0148] Bob generates his private key b. [0149] Haley generates her private key h. [0150] Fred generates his private key . [0151] Step 3. Haley uses commutative group operation * to compute her public key g.sup.h from her private key h and generator g. [0152] Alice computes her public key g.sup.a from her private key a. [0153] Bob computes his public key g.sup.b from his private key b. [0154] Fred computes his public key g.sup. from his private key . [0155] Step 4. Fred sends his public key g.sup. to Haley. [0156] Bob sends his public key g.sup.b to Alice. [0157] Alice sends her public key g.sup.a to Bob. [0158] Haley sends her public key g.sup.h to Fred. [0159] Step 5. Bob receives Alice's public key g.sup.a. [0160] Haley receives Fred's public key g.sup.. [0161] Fred receives Haley's public key g.sup.h. [0162] Alice receives Bob's public key g.sup.b. [0163] Step 6. Fred computes shared secret g.sup.h with private key and Haley's public key. [0164] Alice computes shared secret g.sup.ba with private key a and Bob's public key. [0165] Haley computes shared secret g.sup.h with private key h and Fred's public key. [0166] Bob computes shared secret gab with private key b and Bob's public key. [0167] Step 7. Bob transforms his shared secret gab to multiparty private key .sub.b=(g.sup.ab) [0168] Fred transforms his shared secret g.sup.h to multiparty private key .sub.=(g.sup.h). [0169] Alice transforms her shared secret g.sup.ba to multiparty private key .sub.a=(g.sup.ba) [0170] Haley transforms her shared secret g.sup.h to multiparty private key .sub.h=(g.sup.h). [0171] Step 8. Bob computes his multiparty public key g.sup..sup.b from his multiparty private key .sub.b. [0172] Haley computes her multiparty public key g.sup..sup.h from her multiparty private key .sub.h. [0173] Alice computes her multiparty public key g.sup..sup.a from her multiparty private key .sub.a. [0174] Fred computes his multiparty public key g.sup..sup. from his multiparty private key .sub.. [0175] Step 9. Bob sends his multiparty public key g.sup..sup.b to Haley. [0176] Haley sends her multiparty public key g.sup..sup.h to Alice. [0177] Alice sends her multiparty public key g.sup..sup.a to Fred. [0178] Fred sends his multiparty public key g.sup..sup. to Bob. [0179] Step 10. Fred uses his multiparty private key and multiparty public key g.sup..sup.a to compute 4-party shared secret g.sup..sup.a.sup..sup.. [0180] Alice uses her multiparty private key and multiparty public key g.sup..sup.h to compute 4-party shared secret g.sup..sup.h.sup..sup.a. [0181] Haley uses her multiparty private key and multiparty public key g.sup..sup.a to compute 4-party shared secret g.sup..sup.b.sup..sup.h. [0182] Bob uses his multiparty private key and multiparty public key g.sup..sup. to compute 4-party shared secret g.sup..sup..sup..sup.b.

[0183] In an embodiment, is a Turing computable function. Because is a function, Bob's multiparty private key .sub.b=(g.sup.ab) equals Alice's multiparty private key .sub.a=(g.sup.ba). Similarly, Haley's multiparty private key [0184] .sub.h=(g.sup.h) equals Fred's multiparty private key of n.sub.=(g.sup.h). Because the multiparty private keys satisfy .sub.b=.sub.a and .sub.h=n.sub. and G is a commutative group, the resulting 4 shared secrets are equal: g.sup..sup.a.sup..sup.=g.sup..sup.h.sup..sup.a=g.sup..sup.b.sup..sup.h=g.sup..sup..sup..sup.b.

[0185] FIG. 5A shows step 4 of multiparty process 1.

[0186] FIG. 5B shows step 9 of multiparty process 1. In an embodiment of step 9, Bob sends multiparty public key g.sup..sup.b with sending machine 102 over transmission path 110 and Haley receives multiparty public key g.sup..sup.b with receiving machine 112. In an embodiment, transmission path 110 uses network 212 (FIG. 2A) that is part of the Internet to route multiparty public key g.sup..sup.b to Haley.

[0187] In an embodiment of step 9, Haley sends multiparty public key g.sup..sup.h with sending machine 102 over transmission path 110 and Alice receives multiparty public key g.sup..sup.h with receiving machine 112. In an embodiment, transmission path 110 uses network 212 (FIG. 2A) that is part of the Internet to route multiparty public key g.sup..sup.h to Alice.

[0188] In an embodiment of step 9, Alice sends multiparty public key g.sup..sup.a with sending machine 102 over transmission path 110 and Fred receives multiparty public key g.sup..sup.a with receiving machine 112. In an embodiment, transmission path 110 uses network 212 that is part of the Internet to route multiparty public key g.sup..sup.a to Fred.

[0189] In an embodiment of step 9, Fred sends multiparty public key g.sup..sup. with sending machine 102 over transmission path 110 and Bob receives multiparty public key g.sup..sup. with receiving machine 112. In an embodiment, transmission path 110 uses network 212 that is part of the Internet to route multiparty public key g.sup..sup. to Bob.

[0190] In an embodiment, shared secret transformation function , executed in private key instructions 124, is implemented with a MAC (e.g., HMAC [9] or [16]) or one-way hash function and then a projection function. The projection function assures that the resulting multiparty private key has the appropriate number of bits with respect to group (G, *).

[0191] In an embodiment of multiparty process 1, Alice, Bob, Haley and Fred's steps are performed in receiving/sending machine 122. In an embodiment, each of Alice, Bob, Fred and Haley's non-deterministic generators 942 (FIG. 6a) generate input to private key instructions 124, which create private keys a, b, , h, respectively. In an embodiment, deterministic generator 942 is an instance of random number generator 128 in FIG. 1B. In some embodiments, the private keys a, b, , h are each randomly selected from the positive integers {1, 2, 3, . . . , o(g)1} based on generator g and the output from each party's non-deterministic generators 942.

[0192] In an embodiment of multiparty process 1, Alice's shared secret instructions 130 (FIG. 1B) compute shared secret g.sup.ba by computing g.sup.b* . . . *g.sup.b with the group operation * in G. In other words, Bob's public key g.sup.b is multiplied to itself a times. Then Alice's private key instructions 124 compute Alice's multiparty party private key .sub.a=(g.sup.ba) Afterward, Alice's multiparty public key instructions 126 compute g.sup..sup.a=g* . . . *g, where g is multiplied by itself .sub.a times.

[0193] In an embodiment of multiparty process 1, Bob's shared secret instructions 130 (FIG. 1B) compute shared secret g.sup.ab by computing g.sup.a* . . . *g.sup.a with the group operation * in G. In other words, Alice's public key g.sup.a is multiplied to itself b times. Then Bob's private key instructions 124 compute Bob's multiparty party private key .sub.b=(g.sup.ab) Afterward, Bob's multiparty public key instructions 126 compute g.sup..sup.b=g* . . . *g, where g is multiplied by itself .sub.b times.

[0194] In an embodiment of multiparty process 1, Fred's shared secret instructions 130 (FIG. 1B) compute shared secret g.sup.h by computing g.sup.h* . . . *g.sup.h; in other words, Haley's public key g.sup.h is multiplied to itself times. Then Fred's private key instructions 124 compute Fred's multiparty party private key .sub.=(g.sup.h) Afterward, Fred's multiparty public key instructions 126 compute g.sup..sup.=g* . . . *g, where g is multiplied to itself .sub. times.

[0195] In an embodiment of multiparty process 1, Haley's shared secret instructions 130 (FIG. 1B) compute shared secret g.sup.h by computing g.sup.* . . . *g.sup.; in other words, Fred's public key g.sup. is multiplied to itself h times. Then Haley's private key instructions 124 compute Haley's multiparty party private key .sub.h=(g.sup.h) Afterward, Haley's multiparty public key instructions 126 compute g.sup..sup.h=g* . . . *g, where g is multiplied to itself .sub.h times.

[0196] In an embodiment of multiparty process 1, Alice, Bob, Haley and Fred's steps are performed in receiving machine 112 by multiparty receiving instructions 116. In an embodiment of multiparty process 1, Alice, Bob, Haley and Fred's steps are performed in sending machine 102 by multiparty sending instructions 116.

[0197] In some embodiments of multiparty process 1, private key instructions 124, multiparty public key instructions 126 and shared secret instructions 130 execute elliptic curve computations over a finite field; in other words, (G, *) is an elliptic curve group. In other embodiments of process 1, private key instructions 124, multiparty public key instructions 126 and shared secret instructions 130 are computed with RSA cryptography. In some embodiments, private key instructions 124, multiparty public key instructions 126 and shared secret instructions 130 compute McEliece cryptography [21], based on Goppa codes [20].

[0198] Multiparty Process 2. A n-Party Key Exchange [0199] Step 1. n parties P.sub.1, P.sub.2, . . . , P.sub.n agree on generator g in commutative group (G,*). [0200] Parties P.sub.1, P.sub.2, . . . , P.sub.n agree on a shared secret transformation function . [0201] Shared secret transformation function maps a shared secret to a multiparty private key. [0202] Step 2. Party P.sub.1 generates her private key a.sub.1. [0203] Party P.sub.2 generates her private key a.sub.2. [0204] . . . [0205] Party P.sub.n generates her private key a.sub.n. [0206] Step 3. Party P.sub.1 uses commutative group operation * to compute her public key g.sup.a.sup.1 from her private key a.sub.1 and generator g. [0207] Party P.sub.2 computes her public key g.sup.a.sup.2 from her private key a.sub.2. [0208] . . . [0209] Party P.sub.n computes her public key g.sup.a.sup.n from her private key a.sub.n. [0210] Step 4. Party P.sub.1 sends her public key g.sup.a.sup.1 to party P.sub.2. [0211] Party P.sub.2 sends her public key g.sup.a.sup.2 to party P.sub.1. [0212] Party P.sub.3 sends her public key g.sup.a.sup.3 to party P.sub.4. [0213] Party P.sub.4 sends her public key g.sup.a.sup.4 to party P.sub.3. [0214] . . . [0215] Party P.sub.n-1 sends her public key g.sup.a.sup.n-1 to party P.sub.n. [0216] Party P.sub.n sends her public key g.sup.a.sup.n to party P.sub.n-1. [0217] Step 5. Party P receives P.sub.2's public key g.sup.a.sup.2. [0218] Party P.sub.2 receives P.sub.1's public key g.sup.a.sup.1. [0219] Party P.sub.3 receives P.sub.4's public key g.sup.a.sup.4. [0220] Party P.sub.4 receives P.sub.3's public key g.sup.a.sup.3. [0221] . . . [0222] Party P.sub.n-1 receives P.sub.n's public key g.sup.a.sup.n. [0223] Party P.sub.n receives P.sub.n-1's public key g.sup.a.sup.n-1. [0224] Step 6. Party P.sub.1 private key a.sub.1 and public key g.sup.a.sup.2 compute shared secret g.sup.a.sup.2.sup.a.sup.1. [0225] Party P.sub.2 private key a.sub.2 and public key g.sup.a.sup.1 compute shared secret g.sup.a.sup.1.sup.a.sup.2. [0226] Party P.sub.3 private key a.sub.3 and public key g.sup.a.sup.4 compute shared secret g.sup.a.sup.4.sup.a.sup.3. [0227] Party P.sub.4 private key a.sub.4 and public key g.sup.a.sup.3 compute shared secret g.sup.a.sup.3.sup.a.sup.4. [0228] . . . [0229] Party P.sub.n-1's private key a.sub.n-1 and public key g.sup.a.sup.n compute shared secret g.sup.a.sup.n.sup.a.sup.n-1. [0230] Party P.sub.n's private key a.sub.n and public key g.sup.a.sup.n-1 compute shared secret g.sup.a.sup.n-1.sup.a.sup.n. [0231] Step 7. Party P.sub.1 maps her shared secret g.sup.a.sup.2.sup.a.sup.1 to multiparty private key .sub.1,2=(g.sup.a.sup.2.sup.a.sup.1) [0232] Party P.sub.2 maps her shared secret g.sup.a.sup.1.sup.a.sup.2 to multiparty private key a.sub.2,1=(g.sup.a.sup.1.sup.a.sup.2) [0233] . . . [0234] Party P.sub.n-1 maps shared secret g.sup.a.sup.n.sup.a.sup.n-1 to multiparty private key .sub.n,n-1=(g.sup.a.sup.n.sup.a.sup.n-1). [0235] Party P.sub.n maps shared secret g.sup.a.sup.n-1.sup.a.sup.n to multiparty private key .sub.n-1,n=(g.sup.a.sup.n-1.sup.a.sup.n). [0236] Step 8. Party P.sub.1 computes her multiparty public key g.sup..sup.1,2 from her multiparty private key .sub.1,2. [0237] Party P.sub.2 computes her multiparty public key g.sup..sup.2,1 from her multiparty private key .sub.2,1. [0238] . . . [0239] Party P.sub.n-1 computes multiparty public key g.sup..sup.n-1,n from her multiparty private key .sub.n-1,n. [0240] Party P.sub.n computes multiparty public key g.sup..sup.n,n-1 from her multiparty private key .sub.n,n-1. [0241] Step 9. Party P.sub.1 sends her multiparty public key g.sup..sup.1,2 to party P.sub.3. [0242] Party P.sub.2 sends her multiparty public key g.sup..sup.2,1 to party P.sub.4. [0243] Party P.sub.3 sends her multiparty public key g.sup..sup.3,4 to party P.sub.1. [0244] Party P.sub.4 sends her multiparty public key g.sup..sup.4,3 to party P.sub.2. [0245] . . . [0246] Party P.sub.n-1 sends her multiparty public key g.sup..sup.n-1,n to party P.sub.n-3. [0247] Party P.sub.n sends her multiparty public key g.sup..sup.n,n-1 to party P.sub.n-2. [0248] Step 10. Party P.sub.1 uses her multiparty private key and multiparty public key g.sup..sup.3,4 to compute multiparty shared secret g.sup.a.sup.3,4.sup.a.sup.1,2. [0249] . . . [0250] Party P.sub.n uses her multiparty private key and multiparty public key g.sup..sup.n-3,n-2 to compute multiparty shared secret g.sup..sup.n-3,n-2.sup..sup.n,n-1. [0251] Remaining Steps Repeat [log.sub.2(n)] times the following: a sequence of steps similar steps 7 to 10. The final result establishes a shared secret .sub.1, 2, . . . , n between parties P.sub.1, P.sub.2, . . . , P.sub.n.

[0252] The expression x is the smallest integer greater than x. For example, 51/10=6. The n-party exchange description assumes the number of parties n is even. When n is odd, the multiparty exchange is similar.

[0253] In embodiments of multiparty processes 1 and 2, generator g is an element of a commutative group (G, *) with a huge order. In some embodiments, G is a cyclic group and the number of elements in G is a prime number. In an embodiment, generator g has an order o(g)>10.sup.80. In another embodiment, generator g has an order o(g) greater than 10.sup.1000.

[0254] In an embodiment of multiparty process 2, party P.sub.i's non-deterministic generator 942 produces input for private key instructions 124 which compute private key a.sub.i. In an embodiment, party P.sub.i's multiparty public key instructions 126 compute her public key as g.sup.a.sup.i=g* . . . *g where g is multiplied by itself a.sub.i times, using the group operations in (G, *). In some embodiments, the party P.sub.i's private key a.sub.i is randomly selected from the positive integers {1, 2, 3, . . . , o(g)1}. In an embodiment of multiparty process 2, party P.sub.i's steps are performed in receiving machine 112. In an embodiment of multiparty process 2, party P.sub.i's steps are performed in sending machine 102.

[0255] In some embodiments of multiparty process 2, private key instructions 124, multiparty public key instructions 126 and shared secret instructions 130 execute elliptic curve computations over a finite field; in other words, (G, *) is an elliptic curve group. In other embodiments of multiparty process 2, private key instructions 124, multiparty public key instructions 126 and shared secret instructions 130 are computed with RSA cryptography. In some embodiments, private key instructions 124, multiparty public key instructions 126 and shared secret instructions 130 compute McEliece cryptography [21], based on Goppa codes [20].

[0256] In some embodiments of multiparty process 2, party P.sub.1 instructions are executed inside of machine 210, as shown in FIG. 2A; party P.sub.2's instructions are executed inside of machine 214, as shown in FIG. 2A; party P.sub.3's instructions are executed inside of machine 216. In some embodiments, machines 210, 214, 216, 218 execute instructions in system 250, as shown in FIG. 2B, that contains output system 252, input system 254, memory system 256, and processor system 258. In some embodiments of multiparty process 2, parties P.sub.1, P.sub.2, . . . , P.sub.n transmit their public keys across network 212, as shown in FIG. 2A.

7.11 Secure Conference Call

[0257] In an embodiment of multiparty process 1 or 2, three or more parties make a voice or video conference call so that any outsiders may not listen or eavesdrop on their voice conversation. Encryption/decryption instructions 134 encrypt video and voice data before it is transmitted between the conference call parties. In an embodiment, encryption/decryption instructions are executed inside of mobile phone 400 and mobile phone 500, as shown in FIG. 4.

[0258] In an embodiment, shared secret key(s) 132 stores the shared secret .sub.1, 2, . . . , n established between parties P.sub.1, P.sub.2, . . . , P.sub.n. In an embodiment, as shown in FIG. 4, mobile phone 400 acts as party P.sub.1 and mobile phone 500 acts as party P.sub.2. Transformation function maps .sub.1, 2, . . . , n to a shared symmetric cryptographic key and a shared authentication key among parties P.sub.1, P.sub.2, . . . , P.sub.n. Using encryption/decryption instructions 134, parties P.sub.1, P.sub.2, . . . , P.sub.n, encrypt each party's voice and video data with the symmetric cryptographic key before sending it to the other parties via transmission path 110.

7.12 Secure Self-Driving Vehicles

[0259] In some embodiments of multiparty process 2, a multiparty key exchange can help protect a network of autonomous self-driving automobiles, trucks or flying vehicles. As shown in FIG. 8, each vehicle performs process 2 and transmits multiparty public keys to other self-driving vehicles and vice versa to establish one or more shared secrets between all valid self-driving vehicles. In some embodiments, the shared secret(s) established by the valid self-driving vehicles helps prevent a rogue vehicle or rogue communication from an unauthorized vehicle or unauthorized person, or unauthorized computer from subverting the communication or driving directions of the self-driving vehicles. This can help prevent catastrophic events such as two self-driving vehicles crashing due to subverted communications and/or a self-driving vehicle hitting one or more pedestrians. In some instances, an unauthorized computer may attempt to transmit malware that is installed as a software update, such that the malware subverts the driving instructions executed by processor system 258 (FIG. 2B), located inside vehicle 510.

[0260] In an embodiment, shared secret key(s) 132 stores the shared secret(s) .sub.1, 2, . . . , n established between parties P.sub.1, P.sub.2, . . . , P.sub.n. Transformation function maps .sub.1, 2, . . . , n to a shared symmetric cryptographic key and a shared authentication key among parties P.sub.1, P.sub.2, . . . , P.sub.n. Using encryption/decryption instructions 134, parties P.sub.1, P.sub.2, . . . , P.sub.n encrypt each vehicle's data and communications with the symmetric cryptographic key and sign the data and communications with the authentication key before sending them to the other self-driving vehicles via transmission path 110. FIG. 8 shows parties P.sub.1, P.sub.2, . . . , P.sub.n, represented as vehicles 1, 2, . . . , n1, n.

[0261] Although the invention(s) have been described with reference to specific embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the true spirit and scope of the invention. In addition, modifications may be made without departing from the essential teachings of the invention.

REFERENCES

[0262] [1] Dan Boneh, Craig Gentry and Brent Waters. Collusion Resistant Broadcast Encryption With Short Ciphertexts and Private Keys. [0263] [2] Simon Kochen and Ernst P. Specker. The Problem of Hidden Variables in Quantum Mechanics. Journal of Mathematics and Mechanics (now Indiana Univ. Math Journal) 17 No. 1, 59-87, 1967. [0264] [3] John Conway and Simon Kochen. The Strong Free Will Theorem. Notices of the American Mathematical Society. 56(2), 226-232, February 2009. [0265] [4] Alan M. Turing. On computable numbers, with an application to the Entscheidungsproblem. Proc. London Math. Soc. Series 2 42 (Parts 3 and 4), 230-265, 1936. A correction, ibid. 43, 544-546, 1937. [0266] [5] Wikipedia. Transmission Control Protocol/Internet Protocol. https://en.m.wikipedia.org/wiki/TCP_IP [0267] [6] Stephen Cook. The P VS NP Problem. http://www.claymath.org/sites/default/files/pvsnp.pdf [0268] [7] Klint Finley. Chinese Supercomputer Is Still the Worlds Most Powerful. Wired Magazine. Nov. 18, 2013. [0269] [8] A.. Webster and S. E. Tavares. On the Design of S-Boxes. Advances in Cryptology. CRYPTO 85 Proceedings. LNCS 218. Springer, 523-534, 1986. [0270] [9] Mihir Bellare, Ran Canetti and Hugo Krawczyk. Keying Hash Functions for Message Authentication. Advances in CryptologyCrypto 96 Proceedings. LNCS 1109, N. Koblitz ed., Springer, 1996. [0271] [10] Guido Bertoni, Joan Daemen, Michael Peeters, Gilles Van Assche. Keccak Reference 3.0 2011. http://keccak.noekeon.org/ http://en.wikipedia.org/wiki/Keccak [0272] [11] Jean-Philippe Aumasson, Samuel Neves, Zooko Wilcox-O'Hearn, Christian Winnerlein. BLAKE. https://131002.net/blake/ [0273] [12] Praveen Gauravaram, Lars Knudsen, Krystian Matusiewicz, Florian Mendel, Christian Rechberger, Martin Schlffer, and Sren S. Thomsen. Grstl a SHA-3 candidate. http://www.groestl.info [0274] [13] Hongjun Wu. The Hash Function JH. 2011. http://ehash.iaik.tugraz.at/wiki/JH http://www3.ntu.edu.sg/home/wuhj/research/jh/jh_round3.pdf [0275] [14] Niels Ferguson, Stefan Lucks, Bruce Schneier, Doug Whiting, Mihir Bellare, Tadayoshi Kohno, Jon Callas, Jesse Walker. The Skein Hash Function Family. 2010. https://www.schneier.com/skein1.3.pdf http://en.wikipedia.org/wiki/Skein_(hash_function) [0276] [15] NIST. FIPS-180-2: Secure Hash Standard, August 2002. http://www.itl.nist.gov/fipspubs/. [0277] [16] Mark Wegman and J. Lawrence Carter. New Hash Functions and Their Use in Authentication and Set Equality. Journal of Computer and System Sciences. 22, 265-279, 1981. [0278] [17] E. R. Berlekamp. Algebraic Coding Theory. New York, McGraw-Hill, 1968. [0279] [18] L. K. Grover. A fast quantum mechanical algorithm for database search. Proceedings of the 28th Annual ACM Symposium on the Theory of Computing. May 1996. [0280] [19] D. Bernstein. Grover vs. McEliece. Post-Quantum Cryptography. LNCS 6061, Springer, 73-80, 2010. [0281] [20] Robert J. McEliece. The Theory of Information and Coding. Reading, Mass., Addison-Wesley, 1977. [0282] [21] Robert J. McEliece. A public-key cryptosystem based on algebraic coding theory, JPL DSN Progress Report 42-44, pages 114-116, 1978. http://ipnpr.jpl.nasa.gov/progress_report2/42-44/44N.PDF [0283] [22] Sherman Stein and Sandor Szabo. Algebra and Tiling. Homomorphisms in the Service of Geometry. Mathematical Association of America, 1994. [0284] [23] R. L. Rivest, A. Shamir, and L. Adleman. A method for obtaining digital signatures and public-key cryptosystems. Communications of the ACM. 21, 120-126, 1978. [0285] [24] Joseph H. Silverman and John Tate. Rational Points on Elliptic Curves. Springer-Verlag, 1992. [0286] [25] Harold Edwards. A normal form for elliptic curves. Bulletin of the American Mathematical Society. 44: 393-422, April, 2007. [0287] [26] Peter Montgomery. Speeding the Pollard and Elliptic Curve Methods of Factorization. Mathematics of Computation 48 (177): 243-264, 1987. [0288] [27] A. J. Menezes, P. C. van Oorshot, and S. A. Vanstone. Handbook of Applied Cryptography. CRC Press, N Y, 1997. [0289] [28] Serge Vaudenay. Secure Communications over Insecure Channels Based on Short Authenticated Strings. Advances in CryptologyCRYPTO 2005. 309-326, 2005.

TABLE-US-00001 TABLE 1 McEliece hidden-Goppa-code public key cryptography Classical Quantum Size of Public Key (bits) Complexity Complexity b (b log.sub.2 b).sup.2 2.sup.b operations ()2.sup.b operations 128 (128 * 7).sup.2 = 802,816 .sup.3.4 10.sup.38 1.7 10.sup.38 256 (256 * 8).sup.2 = 4,194,304 1.16 10.sup.77 5.8 10.sup.76 512 (512 * 9).sup.2 = 21,233,664 1.34 10.sup.154 .sup.6.7 10.sup.153

Multiparty Key Exchange

Inventors

Cpc classification

Classification Explorer

H04W4/40

ELECTRICITY

Classification Explorer

H04L9/0861

ELECTRICITY

Classification Explorer

H04L9/085

ELECTRICITY

Classification Explorer

H04L63/0435

ELECTRICITY

Classification Explorer

H04L2209/46

ELECTRICITY

Classification Explorer

H04L9/14

ELECTRICITY

Classification Explorer

H04W12/0471

ELECTRICITY

Classification Explorer

H04L63/061

ELECTRICITY

Classification Explorer

H04L9/0841

ELECTRICITY

Classification Explorer

H04L9/304

ELECTRICITY

Classification Explorer

H04L9/0838

ELECTRICITY

Classification Explorer

H04L9/3093

ELECTRICITY

Classification Explorer

H04L9/3066

ELECTRICITY

Classification Explorer

H04L63/065

ELECTRICITY

Classification Explorer

H04W12/033

ELECTRICITY

Classification Explorer

H04L9/302

ELECTRICITY

Classification Explorer

H04L9/0852

ELECTRICITY

International classification

Classification Explorer

H04L29/06

ELECTRICITY

Classification Explorer

H04L9/08

ELECTRICITY

Classification Explorer

H04L9/30

ELECTRICITY

Classification Explorer

H04L9/14

ELECTRICITY

Abstract

Claims

Description