emolero commited on
Commit
d9ecf1a
·
verified ·
1 Parent(s): 073f60b

Add files using upload-large-folder tool

Browse files
This view is limited to 50 files because it contains too many changes.   See raw diff
Files changed (50) hide show
  1. marked/X/T-REC-X.1035-200702-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg +3 -0
  2. marked/X/T-REC-X.1035-200702-I_PDF-E/raw.md +276 -0
  3. marked/X/T-REC-X.1036-200711-I_PDF-E/06a0b232e7b8bfe4f0959385bd070526_img.jpg +3 -0
  4. marked/X/T-REC-X.1036-200711-I_PDF-E/187bba66c887c745c512add37a577c5e_img.jpg +3 -0
  5. marked/X/T-REC-X.1036-200711-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg +3 -0
  6. marked/X/T-REC-X.1036-200711-I_PDF-E/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg +3 -0
  7. marked/X/T-REC-X.1036-200711-I_PDF-E/6ae588a5d08c26852dba93c8664dfcaa_img.jpg +3 -0
  8. marked/X/T-REC-X.1036-200711-I_PDF-E/824fc4c9c20a95313a8e3a2842ad4b87_img.jpg +3 -0
  9. marked/X/T-REC-X.1036-200711-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg +3 -0
  10. marked/X/T-REC-X.1036-200711-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg +3 -0
  11. marked/X/T-REC-X.1036-200711-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg +3 -0
  12. marked/X/T-REC-X.1036-200711-I_PDF-E/cfb98c691c1af5befe32ff9442eea511_img.jpg +3 -0
  13. marked/X/T-REC-X.1037-201310-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg +3 -0
  14. marked/X/T-REC-X.1037-201310-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg +3 -0
  15. marked/X/T-REC-X.1037-201310-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg +3 -0
  16. marked/X/T-REC-X.1037-201310-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg +3 -0
  17. marked/X/T-REC-X.1037-201310-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg +3 -0
  18. marked/X/T-REC-X.1037-201310-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg +3 -0
  19. marked/X/T-REC-X.1037-201310-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg +3 -0
  20. marked/X/T-REC-X.1037-201310-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg +3 -0
  21. marked/X/T-REC-X.1042-201901-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg +3 -0
  22. marked/X/T-REC-X.1042-201901-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg +3 -0
  23. marked/X/T-REC-X.1042-201901-I_PDF-E/19a5f0db57a21a0e82a7f326083e96fd_img.jpg +3 -0
  24. marked/X/T-REC-X.1042-201901-I_PDF-E/1eadbbe42cfcac5c0023577110aec5e3_img.jpg +3 -0
  25. marked/X/T-REC-X.1042-201901-I_PDF-E/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg +3 -0
  26. marked/X/T-REC-X.1042-201901-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg +3 -0
  27. marked/X/T-REC-X.1042-201901-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg +3 -0
  28. marked/X/T-REC-X.1042-201901-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg +3 -0
  29. marked/X/T-REC-X.1042-201901-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg +3 -0
  30. marked/X/T-REC-X.1042-201901-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg +3 -0
  31. marked/X/T-REC-X.1042-201901-I_PDF-E/90ee16ccc0ad16aeca48087797d7b07f_img.jpg +3 -0
  32. marked/X/T-REC-X.1042-201901-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg +3 -0
  33. marked/X/T-REC-X.1042-201901-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg +3 -0
  34. marked/X/T-REC-X.1042-201901-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg +3 -0
  35. marked/X/T-REC-X.1042-201901-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg +3 -0
  36. marked/X/T-REC-X.1042-201901-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg +3 -0
  37. marked/X/T-REC-X.1042-201901-I_PDF-E/dd0f5301a5a6dd7c319701302110de88_img.jpg +3 -0
  38. marked/X/T-REC-X.1042-201901-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg +3 -0
  39. marked/X/T-REC-X.1042-201901-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg +3 -0
  40. marked/X/T-REC-X.1042-201901-I_PDF-E/fc0735d325f0ebd9214171975c68a888_img.jpg +3 -0
  41. marked/X/T-REC-X.1042-201901-I_PDF-E/raw.md +0 -0
  42. marked/X/T-REC-X.1044-201910-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg +3 -0
  43. marked/X/T-REC-X.1044-201910-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg +3 -0
  44. marked/X/T-REC-X.1045-201910-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg +3 -0
  45. marked/X/T-REC-X.1045-201910-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg +3 -0
  46. marked/X/T-REC-X.1045-201910-I_PDF-E/382a9c9e4816bd229191ab4591424dd8_img.jpg +3 -0
  47. marked/X/T-REC-X.1045-201910-I_PDF-E/4ff00a489baaa34a0c01070de1d613db_img.jpg +3 -0
  48. marked/X/T-REC-X.1045-201910-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg +3 -0
  49. marked/X/T-REC-X.1045-201910-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg +3 -0
  50. marked/X/T-REC-X.1045-201910-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg +3 -0
marked/X/T-REC-X.1035-200702-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg ADDED

Git LFS Details

  • SHA256: 11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3
  • Pointer size: 129 Bytes
  • Size of remote file: 4.34 kB
marked/X/T-REC-X.1035-200702-I_PDF-E/raw.md ADDED
@@ -0,0 +1,276 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+
2
+
3
+ I n t e r n a t i o n a l   T e l e c o m m u n i c a t i o n   U n i o n
4
+
5
+ # ITU-T
6
+
7
+ TELECOMMUNICATION
8
+ STANDARDIZATION SECTOR
9
+ OF ITU
10
+
11
+ # X.1035
12
+
13
+ (02/2007)
14
+
15
+ SERIES X: DATA NETWORKS, OPEN SYSTEM
16
+ COMMUNICATIONS AND SECURITY
17
+
18
+ Telecommunication security
19
+
20
+ # --- Password-authenticated key exchange (PAK) protocol
21
+
22
+ ITU-T Recommendation X.1035
23
+
24
+ # ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS, OPEN SYSTEM COMMUNICATIONS AND SECURITY
25
+
26
+ | | |
27
+ |-----------------------------------------------|----------------|
28
+ | <b>PUBLIC DATA NETWORKS</b> | |
29
+ | Services and facilities | X.1–X.19 |
30
+ | Interfaces | X.20–X.49 |
31
+ | Transmission, signalling and switching | X.50–X.89 |
32
+ | Network aspects | X.90–X.149 |
33
+ | Maintenance | X.150–X.179 |
34
+ | Administrative arrangements | X.180–X.199 |
35
+ | <b>OPEN SYSTEMS INTERCONNECTION</b> | |
36
+ | Model and notation | X.200–X.209 |
37
+ | Service definitions | X.210–X.219 |
38
+ | Connection-mode protocol specifications | X.220–X.229 |
39
+ | Connectionless-mode protocol specifications | X.230–X.239 |
40
+ | PICS proformas | X.240–X.259 |
41
+ | Protocol Identification | X.260–X.269 |
42
+ | Security Protocols | X.270–X.279 |
43
+ | Layer Managed Objects | X.280–X.289 |
44
+ | Conformance testing | X.290–X.299 |
45
+ | <b>INTERWORKING BETWEEN NETWORKS</b> | |
46
+ | General | X.300–X.349 |
47
+ | Satellite data transmission systems | X.350–X.369 |
48
+ | IP-based networks | X.370–X.379 |
49
+ | <b>MESSAGE HANDLING SYSTEMS</b> | X.400–X.499 |
50
+ | <b>DIRECTORY</b> | X.500–X.599 |
51
+ | <b>OSI NETWORKING AND SYSTEM ASPECTS</b> | |
52
+ | Networking | X.600–X.629 |
53
+ | Efficiency | X.630–X.639 |
54
+ | Quality of service | X.640–X.649 |
55
+ | Naming, Addressing and Registration | X.650–X.679 |
56
+ | Abstract Syntax Notation One (ASN.1) | X.680–X.699 |
57
+ | <b>OSI MANAGEMENT</b> | |
58
+ | Systems Management framework and architecture | X.700–X.709 |
59
+ | Management Communication Service and Protocol | X.710–X.719 |
60
+ | Structure of Management Information | X.720–X.729 |
61
+ | Management functions and ODMA functions | X.730–X.799 |
62
+ | <b>SECURITY</b> | X.800–X.849 |
63
+ | <b>OSI APPLICATIONS</b> | |
64
+ | Commitment, Concurrency and Recovery | X.850–X.859 |
65
+ | Transaction processing | X.860–X.879 |
66
+ | Remote operations | X.880–X.889 |
67
+ | Generic applications of ASN.1 | X.890–X.899 |
68
+ | <b>OPEN DISTRIBUTED PROCESSING</b> | X.900–X.999 |
69
+ | <b>TELECOMMUNICATION SECURITY</b> | <b>X.1000–</b> |
70
+
71
+ *For further details, please refer to the list of ITU-T Recommendations.*
72
+
73
+ ## ITU-T Recommendation X.1035
74
+
75
+ # Password-authenticated key exchange (PAK) protocol
76
+
77
+ ## Summary
78
+
79
+ ITU-T Recommendation X.1035 specifies a protocol, which ensures mutual authentication of both parties in the act of establishing a symmetric cryptographic key via Diffie-Hellman exchange. The use of Diffie-Hellman exchange ensures the *perfect forward secrecy* – a property of a key establishment protocol that guarantees that compromise of a session key or long-term private key after a given session does not cause the compromise of any earlier session. With the proposed authentication method, the exchange is protected from the *man-in-the-middle* attack. The authentication relies on a pre-shared secret (e.g., password), which is protected (i.e., remains unrevealed) to an eavesdropper preventing an off-line dictionary attack. Thus, the protocol can be used in a wide variety of applications where pre-shared secrets based on the possibly weak password exist.
80
+
81
+ ## Source
82
+
83
+ ITU-T Recommendation X.1035 was approved on 13 February 2007 by ITU-T Study Group 17 (2005-2008) under the ITU-T Recommendation A.8 procedure.
84
+
85
+ # FOREWORD
86
+
87
+ The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
88
+
89
+ The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
90
+
91
+ The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
92
+
93
+ In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
94
+
95
+ ## NOTE
96
+
97
+ In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
98
+
99
+ Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
100
+
101
+ # INTELLECTUAL PROPERTY RIGHTS
102
+
103
+ ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
104
+
105
+ As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at <http://www.itu.int/ITU-T/ipr/>.
106
+
107
+ © ITU 2007
108
+
109
+ All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
110
+
111
+ # CONTENTS
112
+
113
+ | | <b>Page</b> |
114
+ |------------------------------------|-------------|
115
+ | 1 Scope ..... | 1 |
116
+ | 2 References..... | 1 |
117
+ | 3 Definitions ..... | 1 |
118
+ | 4 Abbreviations and acronyms ..... | 1 |
119
+ | 5 Conventions ..... | 1 |
120
+ | 6 Protocol description ..... | 2 |
121
+ | 7 Security considerations..... | 3 |
122
+ | Bibliography ..... | 4 |
123
+
124
+ # Introduction
125
+
126
+ The *Diffie-Hellman* key exchange, although it provides the *perfect forward secrecy*, is vulnerable to the *man-in-the-middle* attack, as is well known. There are several methods of mitigating such attacks; some of them rely on public key cryptography, while others rely on shared secrets (passwords). This Recommendation specifies a protocol of the latter kind.
127
+
128
+ Specifically, with the proposed authentication method, the exchange is protected from the *man-in-the-middle* attack. The authentication relies on a potentially weak pre-shared secret, which is concealed (i.e., remains unrevealed) from an eavesdropper preventing an off-line dictionary attack. Thus, the protocol can be used in a wide variety of applications where pre-shared secrets (such as password-based ones) are employed.
129
+
130
+ PAK advantages are listed below:
131
+
132
+ - Provides strong key exchange with weak passwords;
133
+ - Foils the man-in-the-middle attack;
134
+ - Provides explicit mutual authentication;
135
+ - Ensures perfect forward secrecy.
136
+
137
+ Additional information on PAK is provided in the documents that are listed in the Bibliography.
138
+
139
+ ## ITU-T Recommendation X.1035
140
+
141
+ ### Password-authenticated key exchange (PAK) protocol
142
+
143
+ # 1 Scope
144
+
145
+ This Recommendation provides description of the password-authenticated key exchange (PAK) protocol that meets the following requirements:
146
+
147
+ - Provides mutual authentication based on a pre-shared password;
148
+ - Provides protection against a man-in-the-middle and against offline dictionary attacks.
149
+
150
+ This Recommendation also provides guidance on the selection of the parameters for Diffie-Hellman key exchange.
151
+
152
+ # 2 References
153
+
154
+ The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
155
+
156
+ [TIA 683-D] TIA Standard TIA-683-D (2006), *Over-the-Air Service Provisioning of Mobile Stations in Spread Spectrum Systems*.
157
+
158
+ # 3 Definitions
159
+
160
+ None.
161
+
162
+ # 4 Abbreviations and acronyms
163
+
164
+ This Recommendation uses the following abbreviations and acronyms:
165
+
166
+ | | |
167
+ |------|-------------------------------------|
168
+ | PAK | Password-Authenticated Key Exchange |
169
+ | PW | Password |
170
+ | SHA | Secure Hash Algorithm |
171
+ | WLAN | Wireless Local Area Network |
172
+
173
+ # 5 Conventions
174
+
175
+ The following conventions are used in this Recommendation:
176
+
177
+ - $a \bmod b$ denotes the least non-negative remainder when $a$ is divided by $b$ ;
178
+ - $H_i(u)$ denotes an agreed-on hash function (e.g., based on *SHA-1*) computed over a string $u$ , where $i = 1, 2, 3, \dots$ . The various $H_i()$ act as independent random functions. The use of different random functions in PAK protocol is recommended in order to strengthen the protocol's security.
179
+ - $s|t$ denotes concatenation of the strings $s$ and $t$ .
180
+
181
+ # 6 Protocol description
182
+
183
+ Diffie-Hellman key agreement requires that both the sender and recipient of a message create their own secret random numbers and exchange the exponentiation of their respective numbers. By raising the exchanged value with its secret random number, both parties can compute the same shared secret Diffie-Hellman key.
184
+
185
+ There are two communicating parties in PAK, $A$ and $B$ , which share a secret password $PW$ . The global Diffie-Hellman publicly known constants, a prime $p$ and a generator $g$ are carefully selected so that
186
+
187
+ - 1) a safe prime $p$ is large enough to make the computation of discrete logarithm infeasible; and
188
+ - 2) powers of $g$ modulo $p$ cover the entire range of $p-1$ integers from 1 to $p-1$ .
189
+
190
+ Initially, $A$ selects a secret exponent $R_A$ and computes $g^{R_A} \bmod p$ ; $B$ selects a secret exponent $R_B$ and computes $g^{R_B} \bmod p$ . For efficiency purposes, short exponents could be used for $R_A$ and $R_B$ provided they have a certain minimum size. In the following steps, all multiplication operations should be done mod $p$ , so all values that are being exchanged between the communicating parties are not larger than $p$ . Consequently, all division operations should also be done mod $p$ .
191
+
192
+ Then:
193
+
194
+ - 1) $A$ initiates the exchange by picking a random $R_A$ and sending the quantity $X = H_1(A|B|PW) \cdot (g^{R_A} \bmod p)$ to $B$ ;
195
+
196
+ - 2) $B$ , upon receiving that quantity, verifies that $X$ is not a zero and then divides it by $H_1(A|B|PW)$ to recover $g^{R_A} \bmod p$ . Then $B$ picks a random $R_B$ and computes
197
+
198
+ $$S_1 = H_3(A|B|PW | \frac{X}{H_1(A|B|PW)} | g^{R_B} \bmod p | \left\{ \left( \frac{X}{H_1(A|B|PW)} \right)^{R_B} \bmod p \right\}) \quad \text{and}$$
199
+
200
+ $Y = H_2(A|B|PW) \cdot (g^{R_B} \bmod p)$ . $B$ sends to $A$ a message that contains both quantities $S_1$ and $Y$ .
201
+
202
+ - 3) Upon receiving that message and verifying that $Y$ is not zero, $A$ can authenticate $B$ by recovering what should be $g^{R_B} \bmod p$ and computing $S_1$ itself. If the result is equal to the received value, $A$ computes the key
203
+
204
+ $$K = H_5(A|B|PW | g^{R_A} \bmod p | \frac{Y}{H_2(A|B|PW)} | \left\{ \left( \frac{Y}{H_2(A|B|PW)} \right)^{R_A} \bmod p \right\}) \quad . \quad \text{To}$$
205
+
206
+ authenticate itself and complete the exchange, $A$ also computes the quantity
207
+
208
+ $$S_2 = H_4(A|B|PW | g^{R_A} \bmod p | \frac{Y}{H_2(A|B|PW)} | \left\{ \left( \frac{Y}{H_2(A|B|PW)} \right)^{R_A} \bmod p \right\}) \quad \text{and sends}$$
209
+
210
+ it to $B$ .
211
+
212
+ - 4) $B$ authenticates $A$ by computing $S_2$ itself and checking it against the value received from $A$ . If both values are the same, $B$ also computes the key
213
+
214
+ $$K = H_5(A|B|PW | \frac{X}{H_1(A|B|PW)} | g^{R_B} \bmod p | \left\{ \left( \frac{X}{H_1(A|B|PW)} \right)^{R_B} \bmod p \right\}) \quad .$$
215
+
216
+ If any of the above verifications fails, the protocol halts; otherwise, both parties have authenticated each other and established the key.
217
+
218
+ The summary of the above steps is illustrated by Figure 1, where $P$ denotes $A|B|PW$ ( $P = A|B|PW$ ) and some formulas have been simplified.
219
+
220
+ | Party A | | Party B |
221
+ |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
222
+ | $X = H_1(P) \cdot (g^{R_A} \bmod p)$ | $\xrightarrow{X}$ | Verify that received value is not 0<br>$\frac{H_1(P) \cdot (g^{R_A} \bmod p)}{H_1(P)} = g^{R_A} \bmod p$ |
223
+ | $S_1 = H_3(P g^{R_A} \bmod p g^{R_B} \bmod p $<br>$g^{R_A R_B} \bmod p)$<br>Calculate $S_1$ and verify that it is equal to the received value for $S_1$ from $B$ | $\xleftarrow{S_1, Y}$ | $S_1 = H_3(P g^{R_A} \bmod p g^{R_B} \bmod p $<br>$g^{R_A R_B} \bmod p)$<br>$Y = H_2(P) \cdot (g^{R_B} \bmod p)$ |
224
+ | $S_2 = H_4(P g^{R_A} \bmod p g^{R_B} \bmod p $<br>$g^{R_A R_B} \bmod p)$ | $\xrightarrow{S_2}$ | $S_2 = H_4(P g^{R_A} \bmod p g^{R_B} \bmod p $<br>$g^{R_A R_B} \bmod p)$<br>Calculate $S_2$ and verify that it is equal to the received value for $S_2$ from $A$ |
225
+ | $K = H_5(P g^{R_A} \bmod p g^{R_B} \bmod p $<br>$g^{R_A R_B} \bmod p)$ | | $K = H_5(P g^{R_A} \bmod p g^{R_B} \bmod p $<br>$g^{R_A R_B} \bmod p)$ |
226
+
227
+ **Figure 1 – Description of the PAK protocol**
228
+
229
+ # 7 Security considerations
230
+
231
+ This clause considers security aspects of PAK. Specifically, it provides guidance on the selection of the Diffie-Hellman parameters.
232
+
233
+ Only previously agreed-upon values for parameters $p$ and $g$ should be used in the PAK protocol. This is necessary to protect against an attacker sending bogus $p$ and $g$ values and thus tricking the other communicating party in improper Diffie-Hellman exponentiation. The use of the parameters $p$ and $g$ that do not meet the requirements described in this Recommendation may result in a compromise of the password. A proper 1024-bit value for $p$ and an appropriate value for $g$ are published in [TIA 683-D].
234
+
235
+ In addition, if short exponents are used for Diffie-Hellman parameters $R_A$ and $R_B$ , then they should have a minimum size of 384 bits (assuming 128-bit session keys are used) as also required in [TIA 683-D].
236
+
237
+ The independent random functions $H_1$ and $H_2$ should have output 1152 bits each, assuming prime $p$ is 1024 bits long and session keys $K$ are 128 bits long. The random functions $H_3$ , $H_4$ , and $H_5$ should have output 128 bits.
238
+
239
+ EXAMPLE: The use of the [b-FIPS 180-2] SHA-1 hashing function could be recommended for instantiation of the random functions $H_i()$ as described in [b-TIA 1050]. However, it should be noted that NIST is encouraging the use of SHA-256 as a more secure alternative to SHA-1.
240
+
241
+ # Bibliography
242
+
243
+ - [b-TIA 1050] TIA 1050-100, Project Number 3-0174-000, *Wireless Local Area Network (WLAN) Interworking*.
244
+ - [b-FIPS 180-2] NIST Federal Information Processing Standards, Publication FIPS 180-2 (2002), *Secure Hash Standard*.
245
+ - [b-EUROCRYPT] BOYKO (V.), MACKENZIE (P.), PATEL (S.): Provably Secure Password-Authenticated Key Exchange Using Diffie-Hellman, EUROCRYPT 2000.
246
+ - [b-IEEE P1363.2] IEEE P1363.2 (Sept. 2006), *Standard Specifications for Password-Based Public-Key Cryptographic Techniques*.
247
+
248
+
249
+
250
+ # SERIES OF ITU-T RECOMMENDATIONS
251
+
252
+ | | |
253
+ |-----------------|---------------------------------------------------------------------------------------------|
254
+ | Series A | Organization of the work of ITU-T |
255
+ | Series D | General tariff principles |
256
+ | Series E | Overall network operation, telephone service, service operation and human factors |
257
+ | Series F | Non-telephone telecommunication services |
258
+ | Series G | Transmission systems and media, digital systems and networks |
259
+ | Series H | Audiovisual and multimedia systems |
260
+ | Series I | Integrated services digital network |
261
+ | Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
262
+ | Series K | Protection against interference |
263
+ | Series L | Construction, installation and protection of cables and other elements of outside plant |
264
+ | Series M | Telecommunication management, including TMN and network maintenance |
265
+ | Series N | Maintenance: international sound programme and television transmission circuits |
266
+ | Series O | Specifications of measuring equipment |
267
+ | Series P | Telephone transmission quality, telephone installations, local line networks |
268
+ | Series Q | Switching and signalling |
269
+ | Series R | Telegraph transmission |
270
+ | Series S | Telegraph services terminal equipment |
271
+ | Series T | Terminals for telematic services |
272
+ | Series U | Telegraph switching |
273
+ | Series V | Data communication over the telephone network |
274
+ | <b>Series X</b> | <b>Data networks, open system communications and security</b> |
275
+ | Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
276
+ | Series Z | Languages and general software aspects for telecommunication systems |
marked/X/T-REC-X.1036-200711-I_PDF-E/06a0b232e7b8bfe4f0959385bd070526_img.jpg ADDED

Git LFS Details

  • SHA256: 7f6abbd60e7badf42befe19bbeb548698e88724dfd8b91a1a71c1499f9332bae
  • Pointer size: 129 Bytes
  • Size of remote file: 1.19 kB
marked/X/T-REC-X.1036-200711-I_PDF-E/187bba66c887c745c512add37a577c5e_img.jpg ADDED

Git LFS Details

  • SHA256: c2b5f50588cceeec6d9771908a4c811cd0bccb3f312e035ee40fd9173297bd4a
  • Pointer size: 130 Bytes
  • Size of remote file: 45 kB
marked/X/T-REC-X.1036-200711-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg ADDED

Git LFS Details

  • SHA256: 4f4bbaa7900d2b5f5c3d75d949247121167be7d669c7948170665b8ff76d3055
  • Pointer size: 130 Bytes
  • Size of remote file: 23.1 kB
marked/X/T-REC-X.1036-200711-I_PDF-E/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg ADDED

Git LFS Details

  • SHA256: ce23c63a86c29ff3e6320ec22838e6e00a5f9f93b9acdbe5c578c7e43abdcd60
  • Pointer size: 130 Bytes
  • Size of remote file: 23.9 kB
marked/X/T-REC-X.1036-200711-I_PDF-E/6ae588a5d08c26852dba93c8664dfcaa_img.jpg ADDED

Git LFS Details

  • SHA256: 36d26caa78703c7cc2b40453d77e5a3ff41841d0494393fc53f749341f9e1da7
  • Pointer size: 128 Bytes
  • Size of remote file: 772 Bytes
marked/X/T-REC-X.1036-200711-I_PDF-E/824fc4c9c20a95313a8e3a2842ad4b87_img.jpg ADDED

Git LFS Details

  • SHA256: f73cac8db5ecbecb8b5b7e3713e95ab3ce46f7e2923a7412fb2408117539c07e
  • Pointer size: 128 Bytes
  • Size of remote file: 932 Bytes
marked/X/T-REC-X.1036-200711-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg ADDED

Git LFS Details

  • SHA256: 73c7056b7c804bddd7ec35f726212ee332aafddb90ac4775c5b890b23b579069
  • Pointer size: 129 Bytes
  • Size of remote file: 6.75 kB
marked/X/T-REC-X.1036-200711-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg ADDED

Git LFS Details

  • SHA256: 9791785f120a0fa32bb1b490e4ac084a9e68fe3b812ec127a1c02681e5e5b828
  • Pointer size: 130 Bytes
  • Size of remote file: 75.2 kB
marked/X/T-REC-X.1036-200711-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg ADDED

Git LFS Details

  • SHA256: 20f81941a454c313e42839fe9c7c9d16a97014d02878a5846a87e42a5729ce4b
  • Pointer size: 130 Bytes
  • Size of remote file: 82.2 kB
marked/X/T-REC-X.1036-200711-I_PDF-E/cfb98c691c1af5befe32ff9442eea511_img.jpg ADDED

Git LFS Details

  • SHA256: 5408b6959d95458c3bed5c7c680bd07ba0ab5d2098c89644da45bd9bb0912846
  • Pointer size: 130 Bytes
  • Size of remote file: 89.3 kB
marked/X/T-REC-X.1037-201310-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg ADDED

Git LFS Details

  • SHA256: 333e518c0ce31daac49fa96dd6e95d39928dcfe2c6cf4aaa630fdd5b26a64bab
  • Pointer size: 130 Bytes
  • Size of remote file: 27.8 kB
marked/X/T-REC-X.1037-201310-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg ADDED

Git LFS Details

  • SHA256: 6d23d6060c79b12a0e729242078e9fb4728df772d62809e251380d86e50c9490
  • Pointer size: 130 Bytes
  • Size of remote file: 59.7 kB
marked/X/T-REC-X.1037-201310-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg ADDED

Git LFS Details

  • SHA256: 75b1a48611f7a9e9362cfd295ab0ef6b7a68e43f42bbcee9f346bb7314bdfa34
  • Pointer size: 130 Bytes
  • Size of remote file: 33.9 kB
marked/X/T-REC-X.1037-201310-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg ADDED

Git LFS Details

  • SHA256: 96e7fce5dbee46c9c26571474f082a0cb2096826c7699ea280f8090578193f0a
  • Pointer size: 130 Bytes
  • Size of remote file: 47.2 kB
marked/X/T-REC-X.1037-201310-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg ADDED

Git LFS Details

  • SHA256: bccdc46b58c56f5c972bcf3f456ec06944a03590b1b04cd6e0518c01ea831fac
  • Pointer size: 129 Bytes
  • Size of remote file: 3.95 kB
marked/X/T-REC-X.1037-201310-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg ADDED

Git LFS Details

  • SHA256: a7a7e2856afc7de5f7573c4f9c83c79a817681980462152e891430e611c23533
  • Pointer size: 130 Bytes
  • Size of remote file: 57.5 kB
marked/X/T-REC-X.1037-201310-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg ADDED

Git LFS Details

  • SHA256: fee206cd830eeb5181571d395bb479b5a172e65c8c2ee39b5b8cecae4cc5c9f3
  • Pointer size: 130 Bytes
  • Size of remote file: 95.5 kB
marked/X/T-REC-X.1037-201310-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg ADDED

Git LFS Details

  • SHA256: b0828a66a7f743fc884997fd2b997f3264f5efebd6eb8cb39549adc3ba776232
  • Pointer size: 130 Bytes
  • Size of remote file: 57.4 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg ADDED

Git LFS Details

  • SHA256: fed04c4a83f96fdab005c2a44cbf4c4bd69658f6c99f6b12f7fcd0097a868880
  • Pointer size: 130 Bytes
  • Size of remote file: 94.9 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg ADDED

Git LFS Details

  • SHA256: f5a5181407216d035f79590e56aec9a16d90fff38afd14731b2addf225d041a7
  • Pointer size: 129 Bytes
  • Size of remote file: 4.1 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/19a5f0db57a21a0e82a7f326083e96fd_img.jpg ADDED

Git LFS Details

  • SHA256: 099ff6f8d40f80b95af8597668b7349dcd03bf09047acbf05cfac6160aa4d6fd
  • Pointer size: 130 Bytes
  • Size of remote file: 69.4 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/1eadbbe42cfcac5c0023577110aec5e3_img.jpg ADDED

Git LFS Details

  • SHA256: ac801cddf75d086d2ea5bdd3f519f3c3fcccc3896408367fd5e13eb3bb1e939b
  • Pointer size: 130 Bytes
  • Size of remote file: 58.1 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg ADDED

Git LFS Details

  • SHA256: 850a1684afc9d5eab094de7777be0103bec122742b291e3a52671547bb840dae
  • Pointer size: 131 Bytes
  • Size of remote file: 116 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg ADDED

Git LFS Details

  • SHA256: 549df4b69b69e998a5ca01fa2f91f0dc00541340b7311a508c24aa9deb20ef09
  • Pointer size: 130 Bytes
  • Size of remote file: 30.1 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg ADDED

Git LFS Details

  • SHA256: bef6c82ead2a6fd73ea72ba2adc25114413a7e008ca79bccf954cdef9c2c4e4b
  • Pointer size: 130 Bytes
  • Size of remote file: 83.1 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg ADDED

Git LFS Details

  • SHA256: 5ccb74cdf72af4fc28cfff7eca3d3ecfced1eb129b78dd6488b1662cd8a708f1
  • Pointer size: 131 Bytes
  • Size of remote file: 105 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg ADDED

Git LFS Details

  • SHA256: 9889364181fd49365f61e1951ef62d1fee835917c4df2dbf2c46b5223d263060
  • Pointer size: 130 Bytes
  • Size of remote file: 58 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg ADDED

Git LFS Details

  • SHA256: 3d34f63c6d74b87c82c5fd20ca74a88417550d6afcd950a7730a9c0eb9edf246
  • Pointer size: 130 Bytes
  • Size of remote file: 62.7 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/90ee16ccc0ad16aeca48087797d7b07f_img.jpg ADDED

Git LFS Details

  • SHA256: 526cc210c786edc02add0f9d617a26b0ca65bc64007cb435568142d87d00f499
  • Pointer size: 130 Bytes
  • Size of remote file: 33.1 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg ADDED

Git LFS Details

  • SHA256: 587eba1f1977545a0850bea895ca51f882d2bc1ee2a21a673b9aed3be52bbd13
  • Pointer size: 130 Bytes
  • Size of remote file: 49.8 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg ADDED

Git LFS Details

  • SHA256: 3b6f71c523de911c98ca3c9c84be2d3b87fe5a4e2485f2d6f69544e99f30a929
  • Pointer size: 130 Bytes
  • Size of remote file: 48.4 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg ADDED

Git LFS Details

  • SHA256: 8047267c6ae140e7b3ab21dac89c7e047de4077116bc13e2b17f87b9ee4dbfc0
  • Pointer size: 130 Bytes
  • Size of remote file: 68.5 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg ADDED

Git LFS Details

  • SHA256: d0d02926bd29a7df3f809ffe2842c7f3e650dc92c75227ed175f93311a9ea653
  • Pointer size: 130 Bytes
  • Size of remote file: 63.6 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg ADDED

Git LFS Details

  • SHA256: cd609abd22fe6b957c17c4762149e18a4bbf4d225e629eeea4c3453fd701c58e
  • Pointer size: 131 Bytes
  • Size of remote file: 116 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/dd0f5301a5a6dd7c319701302110de88_img.jpg ADDED

Git LFS Details

  • SHA256: f2ce3c5470a3f081981047615763538b950f29dbfbe4bd9aef1a654999a74dff
  • Pointer size: 131 Bytes
  • Size of remote file: 135 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg ADDED

Git LFS Details

  • SHA256: 285f2647d23aedffc0a4af4083dca5edd6008617123acc706725e4e1d636c779
  • Pointer size: 130 Bytes
  • Size of remote file: 45.3 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg ADDED

Git LFS Details

  • SHA256: ff93a4df4467644bb1f017c784d21a5871c02e1118cd570093d8dd49f50bca94
  • Pointer size: 130 Bytes
  • Size of remote file: 59.9 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/fc0735d325f0ebd9214171975c68a888_img.jpg ADDED

Git LFS Details

  • SHA256: b889fd294922bc62f817be7457a3a5d55e85d953238a6c959cd7aa94cde04dfa
  • Pointer size: 130 Bytes
  • Size of remote file: 63.8 kB
marked/X/T-REC-X.1042-201901-I_PDF-E/raw.md ADDED
The diff for this file is too large to render. See raw diff
 
marked/X/T-REC-X.1044-201910-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg ADDED

Git LFS Details

  • SHA256: 2c9b7b18abc74122045766d61821af23146bd727c67f0a51af7f5dc1dd1a8e76
  • Pointer size: 129 Bytes
  • Size of remote file: 6.84 kB
marked/X/T-REC-X.1044-201910-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg ADDED

Git LFS Details

  • SHA256: 040e6a0d75a7b1da44eeb454e530f357a786c6a826a068cac798153fe9a8176e
  • Pointer size: 131 Bytes
  • Size of remote file: 177 kB
marked/X/T-REC-X.1045-201910-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg ADDED

Git LFS Details

  • SHA256: ff7ab331427fd94e1cc19b9c53bfa64e1121cb0da41cce0fadcd33cef6616a93
  • Pointer size: 130 Bytes
  • Size of remote file: 86.3 kB
marked/X/T-REC-X.1045-201910-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg ADDED

Git LFS Details

  • SHA256: c63d1328487df5dbee950a537b1ef13f12a94c22dd52cb69a699aef2a0a049c8
  • Pointer size: 131 Bytes
  • Size of remote file: 100 kB
marked/X/T-REC-X.1045-201910-I_PDF-E/382a9c9e4816bd229191ab4591424dd8_img.jpg ADDED

Git LFS Details

  • SHA256: dfcef3efbe249a7927bf62e5306fa37e5670a1c517136e0cbb46e526f5575097
  • Pointer size: 130 Bytes
  • Size of remote file: 80.2 kB
marked/X/T-REC-X.1045-201910-I_PDF-E/4ff00a489baaa34a0c01070de1d613db_img.jpg ADDED

Git LFS Details

  • SHA256: f2d054fd1ea8866010a1bb3590d00ff6d7ee01ecf55657d852e262d04f1f2fb1
  • Pointer size: 130 Bytes
  • Size of remote file: 53.4 kB
marked/X/T-REC-X.1045-201910-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg ADDED

Git LFS Details

  • SHA256: bc18faa0338eea6b5c75d1747d2b66e667004ab428f74200c29b277d1090b805
  • Pointer size: 131 Bytes
  • Size of remote file: 122 kB
marked/X/T-REC-X.1045-201910-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg ADDED

Git LFS Details

  • SHA256: 15639a8ef30bb4f61606efd4e3669a2660ad5ea021fd2f6e10ae5ac9364dde1a
  • Pointer size: 131 Bytes
  • Size of remote file: 116 kB
marked/X/T-REC-X.1045-201910-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg ADDED

Git LFS Details

  • SHA256: 1478af40ae182a2fcef7d1a6a31d458987e3ff9eec8cac0879d2fac228fa6e11
  • Pointer size: 131 Bytes
  • Size of remote file: 132 kB