<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Strengthening the password authenticated key exchange protocols due to the use of asymmetric execution of cryptosystems</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Varfolomeev A.A</string-name>
          <email>a.varfolomeev@mail.ru</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of «Information Security» of Bauman Moscow State Technical University (BMSTU) Moscow</institution>
          ,
          <country country="RU">Russia</country>
        </aff>
      </contrib-group>
      <fpage>79</fpage>
      <lpage>82</lpage>
      <abstract>
        <p>- Protocols for generating high-entropy cryptographic session keys from long-term low-entropy keys or passwords (PAKE - Password Authenticated Key Exchange) are used to increase the security of information protection in information systems. The paper shows how to increase the security of the PAKE protocols themselves by using the concept of asymmetric execution of cryptosystems proposed by the author (see, for example, at SIBCON 2016, RusCrypto 2018).</p>
      </abstract>
      <kwd-group>
        <kwd>cryptography</kwd>
        <kwd>cryptographic protocols</kwd>
        <kwd>keys</kwd>
        <kwd>complexity</kwd>
        <kwd>resilience</kwd>
        <kwd>ЕКЕ protocol</kwd>
        <kwd>Diffie-Hellman key agreement protocol</kwd>
        <kwd>SESPAKE protocol</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>The proposed strengthening of cryptographic protocols is
especially relevant in the context of restrictions on the
parameters used in the primitives of cryptographic protocol.</p>
      <p>INTRODUCTION</p>
      <p>This work, in addition to independent significance, is a
continuation of a number of works by the author in the field of
strengthening the security of cryptosystems with short keys.
Short keys are understood as keys of symmetric and
asymmetric cryptosystems defined by the restriction for
unlicensed use introduced by the well-known Decree of the
Government of the Russian Federation dated 04.16.2012 No.
313. According to the Decree, without a license you can use a
“symmetric cryptographic algorithm that uses a cryptographic
key with a length not exceeding 56 bits, either an asymmetric
cryptographic algorithm based either on the method of
factoring integers whose size does not exceed 512 bits, or on
the method of calculating a discrete logarithms in a finite field
multiplicative group size not exceeding 512 bits, or a method
of computing discrete logarithms in another group of size not
exceeding 112 bits.. "</p>
      <p>The concept of low-entropy keys is often used in the
literature, compared with the 256-bit high-entropy keys, which
are typical for modern standard encryption algorithms. Short
keys can be classified as low-entropy, but a number of authors
attribute password words and even PIN-codes, whose entropy
is less than 56 bits, to low-entropy keys.</p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], for symmetric ciphers, it was proposed to introduce
asymmetry into the complexity of the work when encrypting
plaintext and when decrypting a ciphertext by legitimate users.
In this regard, such ciphers and cryptosystems were called
asymmetrically executed. The legitimate recipient of the
ciphertext in this case spent significantly more time decrypting,
since he had to try out a random binary vector by which the
short key used in encryption was increased, which was known
to the sender and recipient of the message. To find the
plaintext, the attacker had to try both the short key and the
random vector added by the sender to the key. Of course, at the
same time, it is assumed that the sender has a high-quality
generator of random binary sequences, and for the model of the
attacker, it is possible to use only the full testing method (brute
force attack) for decryption.
      </p>
      <p>
        To increase security, other methods were proposed in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ],
including preliminary conversion of plaintext such as AON
conversion. The use of new (in comparison with GOST
2814789) operating modes of block ciphers according to the GOST
34.13 standard turned out to be essential for the
implementation efficiency.
      </p>
      <p>
        Further, at the RusCrypto 2018 conference [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], the author
proposed to use the PAKE protocols to strengthen the strength
of ciphers with short keys, where a short key should be used as
a password word. For example, when using symmetric and
asymmetric ciphers with short keys in the EKE protocol [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ],
the complexity of decryption is not the sum of the complexity
of decryption of each of the ciphers, but is their product.
      </p>
      <p>This paper shows how the introduction of asymmetry in the
complexity of operations performed by legitimate users of the
PAKE protocols themselves leads to an increase in the
complexity of solving cryptanalysis tasks for an attacker using
well-known protocols as an example.</p>
      <p>
        The concept of “asymmetric PAKE” was previously
considered in a number of works (see, for example, [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]),
but the reason for using the word “asymmetry” differs from
that described in this paper. Asymmetric PAKE is the same
PACK in the client-server architecture, where the server does
not store the password word itself, but the value of the one
way function from it. If the server is compromised, the
attacker will have to perform an additional off-line attack to
find the password word.
      </p>
      <p>
        The EKE protocol [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] is one of the first
passwordbased authentication key exchange protocols. The purpose of
the protocol is to safely transport a high-entropy key from one
user to another if they have a common low-entropy secret
(password). The EKE protocol has been patented. For
readability, we recall the steps and steps of the EКE protocol.
Let PW denote the password word known to users A and B.
      </p>
      <p>Key transportation stage.
• 1. A: sends the message [A, E (PW; PKa)]  B,
where E (PW; PKa) is the encryption transformation with a
symmetric cipher on the PW key, PKa is the public key of user
A for the asymmetric cipher.
• 2. B: produces a high-entropy key k and sends</p>
      <p>E (PW; E_PKa (k))  A.</p>
      <p>The step of confirming receipt of key k is “Request-response”.
• 3. A: From E (PW; E_PKa (k)) receives k, sends</p>
      <p>E (k; R_a)  B.
• 4. B: From E (k; R_a) it receives R_a, sends</p>
      <p>E (k; h (R_a) II R_b) A, here h is some hash function.
• 5. A: From E (k; h (R_a) II R_b) receives h (R_a) II R_b and
checks h (R_a) = ?, then sends E (k; h (R_b))  B.
• 6. B: From E (k; h (R_b)) receives and checks h (R_b) =?.</p>
      <p>According to the Dolev - Yao model, the attacker in
step 1 receives ciphertext E (PW; PKa) for off-line attacks.
Due to the relatively small number of options for choosing
PW, he can go through all of them and get options for the PKa
public key. But this key, which is clear text for E (PW; PKa),
has no structure and is similar to a random sequence of bits.
Therefore, he cannot isolate the true password word at this
step.</p>
      <p>In step 2, each selected PW option leads to the task of
finding the key k by the corresponding public key PKa from
step 1 and the ciphertext E_PKa (k) obtained by decrypting E
(PW; E_PKa (k)) to PW. Even if it is possible to test all the
secret keys of the asymmetric encryption algorithm, it is
impossible to determine the true key k, since it also has no
structure. With short public and secret keys of the asymmetric
algorithm (for example, 512 bits), a faster finding of k is
possible, but still among the options for PW.</p>
      <p>It follows that, to increase the complexity of finding the
key k by an attacker, it is necessary to increase the number of
options for PW.</p>
      <p>Here are options for enhancing the strength of the EKE
protocol only for the key transportation phase, omitting the
second stage for brevity.</p>
    </sec>
    <sec id="sec-2">
      <title>1 option for protocol amplification.</title>
      <p>• 1. A: [A, E (PW-Ra; PKa II h (PKa)]  B, where Ra is a
random vector selected by user A and not known to user B.
• 2. B iterates over Ra and searches for Pka by the criterion for
plaintext. Then it sends E (PW; E_PKa (k))  A.</p>
      <p>In step 1, a hash code from it was added to the plaintext
PKa in order to structure this plaintext so that user B could
find the true public key PKa of user A. Decryption time for B
was increased by 2 ^ IRaI, where IRaI is the size vectors Ra.</p>
      <p>
        But the criterion for plaintext also gets the attacker.
Thus, this case is similar to the case of transmitting ciphertext
obtained by encrypting structural plaintext on the PW key
(text structure of the form PKa II h (PKa) is chosen for
clarity). To enhance the strength of encryption in this case, the
recommendations of previous works [
        <xref ref-type="bibr" rid="ref1 ref2">1-2</xref>
        ] can be applied.
      </p>
    </sec>
    <sec id="sec-3">
      <title>Option 2 protocol amplification.</title>
      <p>At the first step, a certain set of public keys of user A is
encrypted: PKa1, PKa2, ..., PKaN.</p>
      <p>• 1. A: [A, E (PW; PKa1, PKa2, ..., PKaN)]  B.</p>
      <p>• 2. B: After decrypting the ciphertext E (PW; PKa1, PKa2,
..., PKaN) and receiving the set of public keys {PKa1, PKa2,
..., PKaN}, user B randomly chooses one of them - the PKaJ
key.</p>
      <p>• Next, B generates a high-entropy key k and sends
message A to user A (PW; E_PKaJ (k II h (k))  A.</p>
      <p>• 3. A, knowing the password word PW, decrypts E (PW;
E_PKaJ (k II h (k)) and restores E_PKaJ (k II h (k), iterates
over its public keys PKa1, PKa2, ..., PKaN, looks for PKaJ and
key k. The criterion for finding the true key k is finding the key
k with the correct value h (k) attached.</p>
      <p>User A in this option works more than B. In step 3, he
must sort through all N sent to the user B public keys PKa1,
PKa2, ..., PKaN.</p>
      <p>In step 1, as before, the sequence PKa1, PKa2, ...,
PKaN is not structured, which does not allow an attacker to
recover the password word PW from the ciphertext E (PW;
PKa1, PKa2, ..., PKaN)] even with full testing.</p>
      <p>At step 2, we have E_PKaJ (k II h (k)) - the ciphertext
obtained by encrypting the text (k II h (k)) on the public key
PKaJ of user A. It has no structure, which does not allow the
attacker to find PW from the ciphertext E (PW ; E_PKaJ (k II
h (k)) even by full testing.</p>
      <p>After step 1, an attacker can have IPWI variants of the
set of public keys {PKa1, PKa2, ..., PKaN}, where IPWI is the
number of possible variants of the word PW.</p>
      <p>After 2 steps, the attacker has IPWI * N decryption
tasks for the ciphertext E_PKaJ (k II h (k). To assess the
complexity of decryption, one must proceed from the strength
of the asymmetric algorithm used.</p>
    </sec>
    <sec id="sec-4">
      <title>3 option for protocol amplification.</title>
      <p>• 1. A: [A, E (PW - Ra; PKa1, PKa2, ..., PKaN, h (*))]  B.
• 2. B: Iterates over Ra and looks for a true set of public keys.
The criterion is the structure of the text [PKa1, PKa2, ...,
PKaN, h (*)]. Selects one PKaJ key of user A.
• E (PW-Ra; E_PKaJ (k II h (k))  A, k is a high-entropy key.
• 3. A: iterates over its public keys PKa1, PKa2, ..., PKaN (Ra
- knows), searches for PKaJ and key k. The criterion is finding
the key k with the correct value h (k) attached.</p>
    </sec>
    <sec id="sec-5">
      <title>4 option protocol amplification.</title>
      <p>• 1. A: [A, E (PW - Ra; PKa1, PKa2, ..., PKaN, h (*))]  B.
• 2. B: Iterates over Ra and looks for a true set of public keys.
The criterion is the structure of the text [PKa1, PKa2, ...,
PKaN, h (*)]. Selects one PKaJ key of user A.
• E (PW-Rb; E_PKaJ (k II h (k))  A, k is a high-entropy
key.
• 3. A: iterates over its public keys PKa1, PKa2, ..., PKaN and
Rb, searches for PKaJ and key k. The criterion is finding the
key k with the correct value h (k) attached.</p>
      <p>In the fourth embodiment, the complexity of the user A
increases due to the unknown vector Rb and the choice of one
of N public keys by the user B, and the complexity of the user
B increases due to the unknown vector Ra.</p>
      <p>In option 3, the vector is Rb = Ra and is known to user
A.</p>
      <p>But in all these cases, the complexity of the decryption
task for the attacker also increases.</p>
    </sec>
    <sec id="sec-6">
      <title>Diffie-Hellman cryptographic key agreement protocol and suggestions for enhancing its strength.</title>
      <p>
        Another type of key installation protocols, in addition
to key transportation protocols, are key agreement protocols
[
        <xref ref-type="bibr" rid="ref7 ref8">7-8</xref>
        ]. In the key agreement protocol, none of the participants
knows in advance which key will be installed for
communication with other participants. This key will be
generated as a result of the exchange of some information
between the participants in the interaction. The most famous
example of a key agreement protocol is the Diffie and
Hellman protocol [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>Recall it for the case of using a group of points of
elliptic curves.</p>
      <p>A, B - participants in the protocol.</p>
      <p>P is the base point of the elliptic curve. 112 bits is a
security setting.</p>
      <p>Xa is the secret key of participant A, a natural number.
Ya = Xa * P - public key of A  B.</p>
      <p>Xb is the secret key of participant B, a natural number.
Yb = Xb * P - public key of B  A.</p>
      <p>A: calculates the shared key K = Xa * Yb = (Xa * Xb)
B: computes the shared key K = Xb * Ya = (Xb * Xa) *
* P
P</p>
      <p>It is known that for the safe use of this protocol, it is
necessary to add an authentication channel to it in order to
exclude a “man in the middle” attack. In particular, the
password word is also used for this. There are many ways to
do this.</p>
      <p>But first, we will demonstrate how to strengthen this
protocol using asymmetric operations, but to modify the
Diffie-Hellman protocol to the transport protocol.</p>
    </sec>
    <sec id="sec-7">
      <title>Gain option.</title>
      <p>Participant A sends a set of {Ya1, ..., YaL} public keys
to Participant B.</p>
      <p>Participant B sends a set of {Yb1, ..., YbL} public keys
to Participant A.</p>
      <p>For clarity, the power sets of public keys are selected
the same. In general, these capacities may be different.</p>
      <p>Participant A randomly selects the public key YbJ and
his private key XaS, builds a key of the form K = XaS * YbJ.</p>
      <p>Then he can use this key, for example, to encrypt some
plaintext OT on the key K and send it to participant B:</p>
      <p>C = E (K, OT)  B.</p>
      <p>Participant B, in order to find K and decrypt C, must sort
through L variants of his secret and L variants of Participant A
public keys. The criterion for the correct choice is the criterion
for clear text. The complexity for B is in order equal to the
number L ^ 2 times the complexity of the operation of
decryption and application of the plain text criterion. For an
attacker who also has all the public keys of the participants, the
task is to solve L ^ 2 discrete logarithm problems (albeit with a
parameter of 112 bits).</p>
      <p>In the proposed variant of protocol amplification, we lose in
the so-called communication complexity of the protocol when
transmitting sets of public keys L ^ 2 times. The complexity of
the decryption process for participant B also increases by the
same amount. The security parameter is 112 bits, selected by
license restriction, it suggests that plaintext and key can in
principle be found, but at very high computational costs. The
choice of the parameter L may complicate this possibility.</p>
    </sec>
    <sec id="sec-8">
      <title>SESPAKE cryptographic protocol and suggestions for enhancing its strength.</title>
      <p>An authentication channel for the Diffie-Hellman
protocol can be provided using digital signatures or a shared
secret (password). Many options are suggested for this.
Consider the SESPAKE protocol, where participants are
supposed to have a common secret word PW.</p>
      <p>
        Recall the main steps of this protocol. Details can be
found in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. This protocol also uses a group of points of an
elliptic curve (In our consideration, the security parameter is
112 bits).
      </p>
      <p>A is the client, B is the server. Both store L points {Q_1, ...,
Q_L} and point P of the elliptic curve. Participant B
additionally stores:</p>
      <p>number ind from the set {1, ..., L}, string salt, point
Q_pw = int (f (PW, salt)) * Q_ind. Password words PW may
not be stored.</p>
      <p>1. B  A: ind, salt.
2. A computes Qa_pw = int (f (PW, salt) * Q_ind. (=</p>
      <sec id="sec-8-1">
        <title>Q_pw of server B).</title>
        <p></p>
        <p>A B: Ya = Xa * P - Qa_pw. (= Xa * P - Q_pw)
= Xa * P)
</p>
        <p>B A: Yb = Xb * P + Q_pw.
4. A: Qa = Yb - Qa_pw = Xb * P + Q_pw - Qa_pw = Xb * P.
</p>
        <p>Xa * Xb * P gets Ka,</p>
        <p>Ka = Kb.</p>
        <p>(Here it is omitted how specifically Ka and Kb are
obtained, it is enough that the relation Xa * Xb * P = Xb * Xa
* P is fulfilled).</p>
        <p>It can be seen from the above description that the
SESPAKE protocol is a variant of the Diffie-Hellman protocol
with public keys, distorted by the function of the password
word PW, known only to legitimate participants.</p>
      </sec>
    </sec>
    <sec id="sec-9">
      <title>Option with asymmetric execution.</title>
      <p>The basic idea is not to pass the number ind. Participant
A randomly selects ind from the set {1, ..., L} and computes
Ya, but participant B sends L public keys.</p>
      <p>A is the client, B is the server. Both store L points
{Q_1, ..., Q_L} and point P of the elliptic curve. Participant B
additionally stores: string salt, points Q_pw1 = int (f (PW,
salt)) * Q_1, ...,. Q_pwL = int (f (PW, salt)) * Q_L. The
password word PW may not be stored.</p>
      <p>
1. B A: salt.
2. A computes for random Qa_pwJ = int (f (PW, salt)) * Q_J.</p>
      <p>
A B: YaJ = Xa * P - Qa_pwJ.</p>
      <p>
3. B A: Yb1 = Xb + Q_pw1, ..., YbL = Xb + Q_pwL.
A: chose YbJ and Qa = YbJ - Qa_pwJ = (Xb * P + Q_pwJ)
Qa_pwJ = Xb * P.</p>
      <p>B calculates Qb1 = YaJ + Q_pw1, ..., QbL = YaJ + Q_pwL.</p>
      <sec id="sec-9-1">
        <title>Among them, with the right Q_pwJ.</title>
        <p>QbJ = YaJ + Q_pwJ = (Xa * P - Qa_pwJ) + Q_pwJ = Xa * P.</p>
      </sec>
      <sec id="sec-9-2">
        <title>4. A: The Ka key is used to encrypt plaintext OT.</title>
        <p>This work does not provide specific parameters for
enhancing durability, since in many respects they depend on
the computing power of the attacker and the computing power
of the legitimate participants in the interaction, as well as on
the requirement for the speed of obtaining information, which
in turn can be dictated by the necessary level of security in
each specific case.</p>
        <p>CONCLUSIONS</p>
        <p>The technology of asymmetric execution of
cryptosystems in the PAKE protocol can increase the security
of these protocols. In this paper, this is demonstrated on three
protocols. For each of them, specific methods for asymmetric
execution are proposed.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Varfolomeev</surname>
            <given-names>А.А.</given-names>
          </string-name>
          <article-title>Nekotorye rekomendacii po povysheniyu stojkosti shifra s malym razmerom klyucha k metodu polnogo oprobovaniya</article-title>
          .
          <source>Voprosy kiberbezopasnosti [Cybersecurity issues]</source>
          ,
          <year>2015</year>
          , No
          <volume>5</volume>
          (
          <issue>13</issue>
          ), pp.
          <fpage>60</fpage>
          -
          <lpage>62</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Varfolomeev</given-names>
            <surname>А.А</surname>
          </string-name>
          .
          <article-title>O nekotoryh predvaritel'nyh preobrazovaniyah otkrytogo teksta tipa «All-Or-Nothing» dlya usileniya stojkosti shifra k metodu polnogo oprobovaniya</article-title>
          .
          <source>SIBCON</source>
          <year>2016</year>
          . http://ni.spbstu.ru/wp-content/uploads/2016/05/SibCon-2016- programa.pdf .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Varfolomeev</surname>
            <given-names>А.А.</given-names>
          </string-name>
          <article-title>Ob asimmetrichno vypolnimyh simmetrichnyh kriptosistemah (shifrah)</article-title>
          .
          <source>RusKripto</source>
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Bellovin</surname>
            ,
            <given-names>S. M.</given-names>
          </string-name>
          ;
          <string-name>
            <given-names>M.</given-names>
            <surname>Merritt</surname>
          </string-name>
          (May
          <year>1992</year>
          ).
          <article-title>Encrypted Key Exchange: Password-Based Protocols Secure Against Dictionary Attacks</article-title>
          .
          <source>Proceedings of the I.E.E.E. Symposium on Research in Security and Privacy. Oakland</source>
          . p.
          <volume>72</volume>
          . doi:
          <volume>10</volume>
          .1109/RISP.
          <year>1992</year>
          .213269. ISBN 978-0-
          <fpage>8186</fpage>
          -2825-2.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Jareck</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krawczyk</surname>
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Xu</surname>
            <given-names>J</given-names>
          </string-name>
          . (
          <year>2018</year>
          ).
          <article-title>OPAQUE: An Asymmetric PAKE Protocol Secure Against Pre-Computation Attacks</article-title>
          .
          <source>Advances in Cryptology. Lecture Notes in Computer Science</source>
          .
          <volume>10822</volume>
          . pp.
          <fpage>456</fpage>
          -
          <lpage>486</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>319</fpage>
          -78372-7_
          <fpage>15</fpage>
          .
          <string-name>
            <surname>ISBN</surname>
          </string-name>
          978-3-
          <fpage>319</fpage>
          -78371- 0.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>RFC</given-names>
            <surname>8133. The Security Evaluated Standardized PasswordAuthenticated Key Exchange (SESPAKE) Protocol</surname>
          </string-name>
          . https://tools.ietf.org/html/rfc8133
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7] Slovar' kriptograficheskih terminov. / Pod red. B.
          <string-name>
            <surname>A. Pogorelova</surname>
            i
            <given-names>V. N.</given-names>
          </string-name>
          <string-name>
            <surname>Sachkova</surname>
          </string-name>
          . - М.: МЦНМО,
          <year>2006</year>
          . -
          <fpage>94</fpage>
          с.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Menezes</surname>
            A.,
            <given-names>van Oorschot P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vanstone</surname>
            <given-names>S.</given-names>
          </string-name>
          , (
          <year>1997</year>
          ). Handbook of Applied Cryptography, Boca Raton,
          <source>CRC Press. ISBN 0-8493- 8523-7</source>
          . (Available online)
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Diffie</surname>
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hellman</surname>
            <given-names>M.</given-names>
          </string-name>
          , New Directions in Cryptography,
          <source>IEEE Transactions on Information Theory</source>
          , vol. IT-22, Nov.
          <year>1976</year>
          , pp:
          <fpage>644</fpage>
          -
          <lpage>654</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Smyshlyaev</surname>
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Oshkin</surname>
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Alekseev</surname>
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ahmetzyanova</surname>
            <given-names>L.</given-names>
          </string-name>
          (
          <year>2015</year>
          ).
          <article-title>"On the Security of One Password Authenticated Key Exchange Protocol"</article-title>
          .
          <source>Cryptology ePrint Archive (Report</source>
          <year>2015</year>
          /1237).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>