Password Authenticated Key Exchange by Juggling

The Password Authenticated Key Exchange by Juggling (or J-PAKE) is a password-authenticated key agreement protocol, proposed by Feng Hao and Peter Ryan.[1] This protocol allows two parties to establish private and authenticated communication solely based on their shared (low-entropy) password without requiring a Public Key Infrastructure. It provides mutual authentication to the key exchange, a feature that is lacking in the Diffie–Hellman key exchange protocol.

## Contents

* 1 Description
* 2 Security properties
* 3 The protocol design
* 4 The implementation
* 5 Standardization
* 6 References
* 7 External links

## Description

Two parties, Alice and Bob, agree on a group [math]\displaystyle{ G }[/math] with generator [math]\displaystyle{ g }[/math] of prime order [math]\displaystyle{ q }[/math] in which the discrete log problem is hard. Typically a Schnorr group is used. In general, J-PAKE can use any prime order group that is suitable for public key cryptography, including Elliptic curve cryptography. Let [math]\displaystyle{ s }[/math] be their shared (low-entropy) secret, which can be a password or a hash of a password ([math]\displaystyle{ s \neq 0 }[/math]). The protocol executes in two rounds.

Round 1
Alice selects [math]\displaystyle{ x_1 \in_R [0, q-1] }[/math], [math]\displaystyle{ x_2 \in_R [1, q-1] }[/math] and sends out [math]\displaystyle{ g^{x_1} }[/math], [math]\displaystyle{ g^{x_2} }[/math] together with the Zero-knowledge proofs (using for example Schnorr non-interactive zero-knowledge proof as specified in RFC 8235) for the proof of the exponents [math]\displaystyle{ x_1 }[/math] and [math]\displaystyle{ x_2 }[/math]. Similarly, Bob selects [math]\displaystyle{ x_3 \in_R [0, q-1] }[/math], [math]\displaystyle{ x_4 \in_R [1, q-1] }[/math] and sends out [math]\displaystyle{ g^{x_3} }[/math], [math]\displaystyle{ g^{x_4} }[/math] together with the Zero-knowledge proofs for the proof of the exponents [math]\displaystyle{ x_3 }[/math] and [math]\displaystyle{ x_4 }[/math]. The above communication can be completed in one round as neither party depends on the other. When it finishes, Alice and Bob verify the received Zero-knowledge proofs and also check [math]\displaystyle{ g^{x_2}, g^{x_4} \neq 1 }[/math].

Round 2
Alice sends out [math]\displaystyle{ A = g^{(x_1 + x_3 + x_4) x_2 s} }[/math] and a Zero-knowledge proof for the proof of the exponent [math]\displaystyle{ x_2 s }[/math]. (Note Alice actually derives a new public key using [math]\displaystyle{ g^{x_1 + x_3 + x_4} }[/math] as the generator). Similarly, Bob sends out [math]\displaystyle{ B = g^{(x_1 + x_2 + x_3) x_4 s} }[/math] and a Zero-knowledge proof for the proof of the exponent [math]\displaystyle{ x_4 s }[/math].

After Round 2, Alice computes [math]\displaystyle{ K = (B/g^{x_2 x_4 s})^{x_2} = g^{(x_1 + x_3) x_2 x_4 s} }[/math]. Similarly, Bob computes [math]\displaystyle{ K = (A/g^{x_2 x_4 s})^ {x_4} = g^{(x_1 + x_3) x_2 x_4 s} }[/math]. With the same keying material [math]\displaystyle{ K }[/math], Alice and Bob can derive a session key using a Cryptographic hash function: [math]\displaystyle{ \kappa = H(K) }[/math].

The two-round J-PAKE protocol is completely symmetric. This helps significantly simplify the security analysis. For example, the proof that one party does not leak any password information in the data exchange must hold true for the other party based on the symmetry. This reduces the number of the needed security proofs by half.

In practice, it is more likely to implement J-PAKE in three flows since one party shall normally take the initiative. This can be done trivially without loss of security. Suppose Alice initiates the communication by sending to Bob: [math]\displaystyle{ g^{x_1}, g^{x_2} }[/math] and Zero-knowledge proofs. Then Bob replies with: [math]\displaystyle{ g^{x_3}, g^{x_4}, B = g^{(x_1 + x_2 + x_3) x_4 s} }[/math] and Zero-knowledge proofs. Finally, Alice sends to Bob: [math]\displaystyle{ A = g^{(x_1 + x_3 + x_4) x_2 s} }[/math] and a Zero-knowledge proof. Both parties can now derive the same session key.

Depending on the application requirement, Alice and Bob may perform an optional key confirmation step. There are several ways to do it. A simple method described in SPEKE works as follows: Alice sends to Bob [math]\displaystyle{ H(H(\kappa)) }[/math], and then Bob replies with [math]\displaystyle{ H(\kappa) }[/math].[2] Alternatively, Alice and Bob can realize explicit key confirmation by using the newly constructed session key to encrypt a known value (or a random challenge). EKE, Kerberos and Needham-Schroeder all attempt to provide explicit key confirmation by exactly this method.

## Security properties

Given that the underlying Schnorr non-interactive zero-knowledge proof is secure, the J-PAKE protocol is proved to satisfy the following properties:[3]

1. Off-line dictionary attack resistance - It does not leak any password verification information to a passive/active attacker.
2. Forward secrecy \- It produces session keys that remain secure even when the password is later disclosed.
3. Known-key security - It prevents a disclosed session key from affecting the security of other sessions.
4. On-line dictionary attack resistance - It limits an active attacker to test only one password per protocol execution.

In 2015, Abdalla, Benhamouda and MacKenzie conducted an independent formal analysis of J-PAKE to prove its security in a random oracle model assuming algebraic adversaries.[4]

## The protocol design

The J-PAKE protocol is designed by combining random public keys in such a structured way to achieve a vanishing effect if both parties supplied exactly the same passwords. This is somehow similar to the Anonymous veto network protocol design. The essence of the idea, however, can be traced back to David Chaum's original Dining Cryptographers network protocol,[5] where binary bits are combined in a structured way to achieve a vanishing effect.

## The implementation

J-PAKE has been implemented in OpenSSL and OpenSSH as an experimental authentication protocol. It was removed from the OpenSSH source code at the end of January 2014.[6] It has also been implemented in Smoke Crypto Chat Messenger,[7] in NSS and was used by Firefox Sync version 1.1 but discontinued in 1.5 which uses a different key exchange and storage method.[8] Mozilla's J-PAKE server was shut down along with the Sync 1.1 storage servers on 30 September 2015.[9] Pale Moon continues to use J-PAKE as part of its Sync service.[10] Since February 2013, J-PAKE has been added to the lightweight API in Bouncycastle (1.48 and onwards). J-PAKE is also used in the Thread (network protocol)[11]

## Standardization

J-PAKE was included in ISO/IEC 11770-4 (2017) as an international standard.[12] It is also published in RFC 8236.

## References

1. ↑ F. Hao, P. Ryan. Password Authenticated Key Exchange by Juggling. Proceedings of the 16th International Workshop on Security Protocols, 2008.
2. ↑ Jablon, David (October 1996). "Strong Password-Only Authenticated Key Exchange". ACM SIGCOMM Computer Communication Review 26 (5): 5–26. doi:10.1145/242896.242897. http://www.jablon.org/passwordlinks.html#Jab96.
3. ↑ F. Hao, P. Ryan. J-PAKE: Authenticated Key Exchange Without PKI. Springer Transactions on Computational Science XI, Special Issue on Security in Computing, Part II, Vol. 6480, pp. 192-206, 2010.
4. ↑ M. Abdalla, F. Benhamouda, P. MacKenzie Security of the J-PAKE Password-Authenticated Key Exchange Protocol.
5. ↑ Chaum, David (1988). "The dining cryptographers problem: Unconditional sender and recipient untraceability". Journal of Cryptology 1: 65–75. doi:10.1007/BF00206326. https://dx.doi.org/10.1007/BF00206326.
6. ↑ "CVS log for src/usr.bin/ssh/Attic/jpake.c". http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/Attic/jpake.c. Retrieved 17 November 2023.
7. ↑ Moonlander, Casio (2020). Smoke - An Android Echo Chat Software Application:: Personal Chat Messenger / Open Source Technical Website Reference Documentation. Norderstedt: BOD. pp. 44. ISBN 9783752691993.
8. ↑ "Firefox Sync's New Security Model". 30 April 2014. https://blog.mozilla.org/services/2014/04/30/firefox-syncs-new-security-model/.
9. ↑ "Shutting down the legacy Sync service". 31 July 2015. https://blog.mozilla.org/services/2015/07/31/shutting-down-the-legacy-sync-service/.
10. ↑ "Pale Moon updated to 25.7.3! - Pale Moon forum". https://forum.palemoon.org/viewtopic.php?f=1&t=9854.
11. ↑ "Archived copy". http://threadgroup.org/Portals/0/documents/whitepapers/Thread Commissioning white paper_v2_public.pdf.
12. ↑ "ISO/IEC 11770-4:2017(en)". https://www.iso.org/obp/ui/#iso:std:67933:en.

## External links

* J-PAKE RFC 8236
* A Java prototype of J-PAKE using the finite field
* A Java prototype of J-PAKE using the elliptic curve
* A C implementation of Elliptic Curve J-PAKE in ARM mbed
* A Java implementation of J-PAKE in Bouncycastle
* J-PAKE: From Dining Cryptographers to Jugglers

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Password Authenticated Key Exchange by Juggling. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Password_Authenticated_Key_Exchange_by_Juggling&oldid=3369428"