<!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>Implementing post-quantum KEMs: Practical challenges and solutions ⋆</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Pavlo Vorobets</string-name>
          <email>pavlo.a.vorobets@lpnu.ua</email>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Oleksandr Vakhula</string-name>
          <email>oleksandr.p.vakhula@lpnu.ua</email>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andrii Horpenyuk</string-name>
          <email>andrii.y.horpeniuk@lpnu.ua</email>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Nataliia Korshun</string-name>
          <email>n.korshun@kubg.edu.ua</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Borys Grinchenko Kyiv Metropolitan University</institution>
          ,
          <addr-line>18/2 Bulvarno-Kudryavska str., 04053 Kyiv</addr-line>
          <country country="UA">Ukraine</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>CPITS-II 2024: Workshop on Cybersecurity Providing in Information and Telecommunication Systems II</institution>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Lviv Polytechnic National University</institution>
          ,
          <addr-line>12 Stepana Bandery str., 79013 Lviv</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
      </contrib-group>
      <fpage>212</fpage>
      <lpage>219</lpage>
      <abstract>
        <p>The paper provides an overview and analysis of the current state, problems, and prospects of post-quantum key encapsulation mechanisms. The essential cryptographic building blocks for implementing secure communication protocols are key-encapsulation mechanisms. KEMs enable two parties to securely establish a shared secret key over an insecure channel. This shared key can then be used for symmetric encryption of messages, ensuring confidentiality and integrity of the exchanged data. The National Institute of Standards and Technology (NIST) is actively working on standardizing post-quantum cryptography including KEMs. After the third round of the NIST PQC Standardization Process, NIST has identified the CRYSTALS-KYBER KEM algorithm for standardization. The four algorithms selected for a fourth round are BIKE, Classic McEliece, HQC, and SIKE. In this paper, we explore all these algorithms.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;post-quantum cryptography</kwd>
        <kwd>KEM</kwd>
        <kwd>standardization process</kwd>
        <kwd>NIST</kwd>
        <kwd>CRYSTALS-KYBER</kwd>
        <kwd>BIKE</kwd>
        <kwd>Classic McEliece</kwd>
        <kwd>HQC</kwd>
        <kwd>SIKE 1</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>As quantum computing advances, the implementation of
post-quantum Key Encapsulation Mechanisms (KEMs)
becomes critical for securing data against future threats.</p>
      <p>Quantum computing represents a paradigm shift in
computational power, capable of solving complex
mathematical problems much faster than classical
computers. This capability poses a significant threat to
current cryptographic systems, particularly those relying on
public-key algorithms like RSA and ECC, which are
vulnerable to quantum attacks. The most widely used key
exchange algorithms today are based on hard mathematical
problems, such as integer factorization and the discrete
logarithm problem. However, these problems can be
efficiently solved by a quantum computer [1].</p>
      <p>Key Encapsulation Mechanisms are cryptographic
protocols designed to securely exchange symmetric keys
over insecure channels. They are a cornerstone of many
secure communication systems, enabling the safe
transmission of encryption keys that can then be used for
symmetric encryption. In the quantum era, the security of
these key exchanges is paramount.</p>
      <p>To counteract the threat posed by quantum computing,
researchers are developing post-quantum cryptographic
algorithms, including post-quantum KEMs. These
mechanisms are based on mathematical problems believed
to be resistant to quantum attacks.
The transition to post-quantum cryptography, including
KEMs, is a proactive measure to secure communications
against future quantum threats. Standardization bodies like
the National Institute of Standards and Technology (NIST)
are actively working on evaluating and standardizing
postquantum cryptographic algorithms, including KEMs, to
provide clear guidelines and frameworks for adoption.</p>
      <p>As quantum computing advances, the cryptographic
landscape must evolve to ensure the continued security of
key exchanges and communications. Post-quantum Key
Encapsulation Mechanisms are at the forefront of this
evolution, offering new approaches to secure key exchange
that are resistant to quantum attacks. Understanding and
implementing these mechanisms will be crucial for
protecting sensitive information in the quantum era,
ensuring that cryptographic systems remain robust and
secure against emerging threats.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Literature review and problem statement</title>
      <p>Cryptography is an essential aspect of modern life,
providing the necessary security and trust in our digital
interactions, financial transactions, communication, and
data privacy. Its widespread use ensures the confidentiality,
integrity, and authenticity of information in various aspects
of our daily lives.
As quantum computing continues to advance, the threat it
poses to classical cryptographic systems becomes more
apparent. Quantum computers, once fully realized, will be
able to efficiently break commonly used cryptographic
schemes like RSA and ECC through Shor’s algorithm,
rendering traditional cryptographic infrastructure insecure.
In response to this looming threat, post-quantum
cryptography has emerged as a field focused on developing
cryptographic algorithms that are resistant to quantum
attacks. Key Encapsulation Mechanisms, which are used for
secure key exchange, are a key focus in this field [2].</p>
      <p>The National Institute of Standards and Technology
(NIST) launched its Post-Quantum Cryptography
Standardization project in 2017, aiming to identify and
standardize quantum-resistant cryptographic algorithms.
Many algorithms have been proposed, with a significant
portion focusing on KEMs due to their critical role in secure
communications [3].</p>
      <p>To address this, post-quantum key encapsulation
mechanisms are being developed to ensure the secure
exchange of encryption keys, even in the presence of
powerful quantum adversaries [4].</p>
    </sec>
    <sec id="sec-3">
      <title>3. Introduction to key encapsulation mechanisms in post-quantum cryptography</title>
      <p>A Key Encapsulation Mechanism (KEM) is a cryptographic
protocol used to securely exchange encryption keys
between two parties. The primary goal of KEMs is to
generate and securely encapsulate a random key, which can
then be used for further cryptographic operations, such as
symmetric encryption.</p>
      <p>A KEM typically consists of three main phases:</p>
      <p>Key Generation: The sender generates a pair of keys
(public and private keys). The public key is shared with the
recipient.</p>
      <p>Encapsulation: The sender uses the public key to
generate a random secret and encapsulates it. The
encapsulated secret is sent to the recipient.</p>
      <p>Decapsulation: The recipient uses their private key to
recover the original secret from the encapsulated data.</p>
      <p>The most widely used key exchange algorithms today
are based on hard mathematical problems, such as integer
factorization and the discrete logarithm problem. But these
problems can be efficiently solved by a quantum computer.</p>
      <p>KEMs are generally designed to be non-interactive,
meaning they only require a single communication round
(i.e., one message from the sender to the recipient).</p>
      <p>The main security goal of a KEM is to prevent attackers
from gaining any useful information about the shared
secret. These goals are formalized using security definitions,
often based on the IND-CCA (Indistinguishability under
Chosen Ciphertext Attack) security model [5].</p>
      <p>A KEM can be seen as similar to a Public Key Encryption
(PKE) scheme since both use a combination of public and
private keys. In a PKE, one encrypts a message using the
public key and decrypts using the private key. In a KEM, one
uses the public key to create an “encapsulation”—giving a
randomly chosen shared key—and one decrypts this
“encapsulation” with the private key.</p>
      <p>Public key encryption is often used to transmit symmetric
encryption keys, which are then used to encrypt the
originally intended plain-text content needing encryption
protection. Symmetric keys are faster and stronger (for
smaller key sizes) than asymmetric encryption, and so PKEs
are often just used as a secure transport vehicle for the
symmetric keys that do all the direct encryption work. PKEs
have worked great for decades, but they have at least one
big inherent flaw [6].</p>
      <p>When the public key is longer than the content being
encrypted (such as is usually the case with the symmetric
key in key exchanges), it allows attackers a very easy way
to derive the original private key. To prevent this scenario,
when the message content to be encrypted (e.g., the
symmetric key) is shorter than the asymmetric private key
used to do the encryption, PKEs will usually add additional
“padding” to the message to be encrypted (e.g., the
symmetric key) to remove the vulnerability.</p>
      <p>Key encapsulation methods, also known as key
encapsulation schemes, are a type of asymmetric encryption
technique designed to improve the secure transmission (or
generation) of symmetric keys because they don’t need
random padding added to short messages to stay secure.
Many postquantum cryptographic algorithms are especially
conducive to creating KEMs and because postquantum
algorithms often have even longer asymmetric keys, you
will see many quantum-resistant teams offering KEMs
instead of PKEs. Also, some post-quantum cryptographic
algorithms will offer both PKE and KEM versions [7].</p>
      <sec id="sec-3-1">
        <title>3.1. Types of KEMs in post-quantum cryptography</title>
        <p>In the post-quantum world, the security of KEMs must rely
on quantum-resistant mathematical problems. Here are the
key post-quantum techniques used for designing KEMs:
</p>
        <p>
          Lattice-based cryptography—uses lattices and
their associated mathematical properties to
provide security. A lattice is a set of points in a
multi-dimensional space that form a regular
gridlike structure. Lattice-based cryptography is one of
the most promising post-quantum techniques
because it provides strong security guarantees and
relatively efficient operations. It is based on the
hardness of problems like Learning with Errors
and Short Integer Solution [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. Lattice-based KEMs
are attractive due to their relatively small key sizes
and fast operations, making them suitable for
practical implementations [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ].
        </p>
        <p>
          Code-based cryptography—relies on error-correcting
codes to provide security. The security of these



schemes is based on the hardness of decoding certain
structured codes, making them resistant to quantum
attacks. Code-based cryptography uses the difficulty
of decoding random linear codes, particularly
generalized Goppa codes. One of the oldest forms of
post-quantum cryptography, it offers a high level of
security but often comes with larger key sizes [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ].
Hash-based cryptography—built upon cryptographic
hash functions. These schemes are based on the
hardness of finding collisions in the hash function,
offering a potential post-quantum solution.
Hashbased cryptography’s fundamental benefit is that it is
a commonly used, well-researched technique that
ensures great resistance to quantum assaults, making
it a candidate for long-term security in the
postquantum period (as a long enough key is utilized).
While primarily used in signature schemes,
hashbased cryptography can also be adapted for KEM.
These rely on the difficulty of finding preimages or
collisions in cryptographic hash functions.
        </p>
        <p>
          Multivariate polynormal cryptography—relies on
algebraic equations with multivariate polynomials.
Although secure, the size of the public and private
keys can be large [
          <xref ref-type="bibr" rid="ref11 ref12">11, 12</xref>
          ].
        </p>
        <p>
          Isogeny-based cryptography—based on the
mathematics of elliptic curves and isogenies. These
schemes rely on constructing mappings between
elliptic curves. It offers some of the smallest key sizes
of any post-quantum cryptosystem but is relatively
slow [
          <xref ref-type="bibr" rid="ref13 ref14 ref15 ref16">13–16</xref>
          ].
        </p>
        <p>
          During the transition to post-quantum cryptography,
hybrid KEMs are being used. These combine classical
cryptographic methods (like RSA or ECC) with
postquantum methods. For example, a hybrid KEM could
simultaneously run both a lattice-based KEM (for
postquantum security) and an RSA-based KEM (for classical
security), ensuring safety from both quantum and classical
attacks [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ].
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Practical challenges in implementing post-quantum KEMs</title>
        <p>Implementing post-quantum Key Encapsulation
Mechanisms in real-world systems presents several
practical challenges.</p>
        <p>Many post-quantum KEMs, especially those based on
lattice and code-based cryptography, involve much larger
key sizes compared to classical systems. For example,
codebased KEMs like Classic McEliece have public keys that are
several hundred kilobytes in size, which is significantly
larger than RSA or ECC public keys. Larger key sizes
increase the bandwidth needed for key exchange, which can
slow down communication, particularly in low-bandwidth
environments such as mobile networks, IoT devices, or
satellite communications.</p>
        <p>Post-quantum cryptographic schemes often require
more computational power than traditional cryptographic
algorithms.</p>
        <p>
          For instance, lattice-based schemes like CRYSTALS-KYBER
are efficient in terms of security but may still require more
CPU cycles compared to classical systems. Implementing
these algorithms on resource-constrained devices (e.g., IoT
devices) can be difficult, as they may not have the
processing power required to handle the increased
computational load. The increased computation can
introduce latency in key exchange processes. This can be a
significant issue for real-time systems (e.g., VoIP, video
conferencing), where even small delays in establishing
secure connections can degrade user experience [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ].
        </p>
        <p>
          Many existing security protocols (e.g., TLS, SSH, IPsec)
are based on classical cryptographic primitives like RSA and
ECC. Implementing post-quantum KEMs requires either
significant changes to these protocols or hybrid systems
that combine classical and post-quantum techniques.
Modifying or extending widely used protocols to support
post-quantum KEMs can be complex [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ]. It requires not
only software updates but also widespread adoption to
ensure that all parties in a communication system can use
the new algorithms [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
        </p>
        <p>
          One solution to this challenge is the use of hybrid
cryptography, where both classical and post-quantum
algorithms are used together in a key exchange process.
However, this increases the complexity of the system and
can further slow down performance. Hybrid methods can
add overhead, as two cryptographic algorithms (classical
and post-quantum) are run in parallel, increasing
computational and communication costs [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ].
        </p>
        <p>
          Many post-quantum algorithms, especially those based
on lattice cryptography, are vulnerable to side-channel
attacks such as timing attacks, power analysis, and fault
injection attacks. These attacks exploit the physical
characteristics of a system to recover secret keys. Protecting
implementations of post-quantum KEMs from side-channel
attacks requires additional countermeasures, such as
constant-time implementations or masking techniques.
These countermeasures can increase the complexity and
reduce the performance of the system [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ].
        </p>
        <p>While NIST is in the process of standardizing
postquantum algorithms, the field is still evolving.
Organizations face uncertainty when selecting which
postquantum algorithm to implement, as premature adoption
could lead to interoperability issues or the need for future
upgrades. Additionally, ensuring interoperability between
different implementations of post-quantum KEMs remains
a challenge. After careful consideration during the third
round of the NIST PQC Standardization Process, NIST has
identified a candidate algorithm for standardization. NIST
will recommend the primary KEM algorithm to be
implemented for most use cases: CRYSTALS-KYBER. The
four algorithms selected for this fourth round are BIKE,
Classic McEliece, HQC, and SIKE. Many industries rely on
cryptographic standards and certifications to ensure
security (e.g., FIPS 140-2/3). Post-quantum cryptographic
systems will need to go through extensive certification
processes to be widely adopted in regulated environments,
which can be time-consuming.</p>
        <p>While post-quantum KEMs are designed based on
problems thought to be hard for quantum computers (e.g.,
lattice problems, isogenies, etc.), there is still some
uncertainty about the long-term security of these
algorithms. It is possible that future mathematical
breakthroughs or quantum algorithms could weaken these
assumptions. Building trust in the security of post-quantum
KEMs is essential for their widespread adoption. However,
businesses may be reluctant to deploy post-quantum
solutions until there is a high level of confidence in their
security. There is also resistance to change in the industry.
Many organizations have deeply entrenched cryptographic
infrastructures that rely on RSA or ECC, and the cost of
transitioning to post-quantum cryptography may be
prohibitive in the short term.</p>
        <p>During the transition to post-quantum cryptography,
systems will need to support both classical and
quantumsafe algorithms simultaneously. This creates additional
complexity in terms of key management, negotiation of
algorithms, and ensuring that both parties in a
communication can agree on a common cryptographic
approach. Implementing dual cryptographic systems can
lead to security risks if not done properly, such as potential
downgrade attacks where an adversary forces the use of
weaker, classical algorithms.</p>
        <p>
          The transition to post-quantum KEMs is necessary to
ensure long-term security in the face of quantum computing
advancements, but it comes with practical challenges related
to efficiency, key sizes, integration, and trust. Overcoming
these challenges will require advances in both cryptographic
research and engineering, as well as widespread industry
adoption of post-quantum standards [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ].
        </p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Overview of post-quantum KEM algorithms</title>
      <p>
        NIST has selected several KEMs for standardization,
including CRYSTAL-Kyber and BIKE, Classic McEliece,
HQC, and SIKE. These algorithms represent some of the
most promising candidates for post-quantum Key
Encapsulation Mechanisms that have emerged from the
NIST Post-Quantum Cryptography Standardization project.
Each one is based on different hard mathematical problems,
providing diverse approaches to ensuring security in the
post-quantum era [
        <xref ref-type="bibr" rid="ref22 ref23 ref24">22–24</xref>
        ].
      </p>
      <sec id="sec-4-1">
        <title>4.1. CRYSTALS-Kyber</title>
        <p>
          CRYSTALS-Kyber (Cryptographic Suite for Algebraic
Lattices) is one of the most prominent lattice-based KEMs and
was selected as a NIST finalist due to its efficiency, security,
and small key and ciphertext sizes. It is based on the Module
Learning With Errors (Module-LWE) problem, a variant of
the Learning With Errors (LWE) problem, which is widely
regarded as hard for quantum computers to solve [
          <xref ref-type="bibr" rid="ref25">25</xref>
          ].
        </p>
        <p>The construction of Kyber follows a two-stage
approach: first introduce an INDCPA-secure public-key
encryption scheme encrypting messages of a fixed length of
32 bytes, which is called Kyber.CPAPKE. Then use a slightly
tweaked Fujisaki–Okamoto (FO) transform to construct the
IND-CCA2-secure KEM, which is called Kyber.CCAKEM.</p>
        <p>Kyber defines three parameter sets, which we call
Kyber512, Kyber768, and Kyber1024. The parameters are
listed in Table 2.</p>
        <p>Designation
Kyber512
Kyber768
Kyber1024
n is set to 256 because the goal is to encapsulate keys with
256 bits of entropy (i.e., use a plaintext size of 256 bits in
Kyber.CPAPKE.Enc). Smaller values of n would require
encoding multiple key bits into one polynomial coefficient,
which requires lower noise levels and therefore lowers
security. Larger values of n would reduce the capability to
easily scale security via parameter k.</p>
        <p>q as a small prime satisfying n | (q-1); this is required to
enable fast NTT-based multiplication. There are two smaller
primes for which this property holds, namely 257 and 769.
However, for those primes we would not be able to achieve
the negligible failure probability required for CCA security,
so was chosen the next largest, i.e., q = 3329.</p>
        <p>k is selected to fix the lattice dimension as a multiple of n;
changing k is the main mechanism in Kyber to scale security
(and as a consequence, efficiency) to different levels.
Kyber offers a good balance between key/ciphertext size
and performance. It is more efficient in both space and speed
compared to many other post-quantum candidates.</p>
        <p>Public Key Size: Ranges from 736 bytes (Kyber512) to
1,568 bytes (Kyber1024).</p>
        <p>Ciphertext Size: Ranges from 800 bytes (Kyber512) to
1,568 bytes (Kyber1024).</p>
        <p>Kyber’s computational efficiency makes it suitable for a
wide range of applications, including low-power devices
such as IoT and mobile devices. Kyber provides a very
efficient encapsulation and decapsulation process,
particularly when compared to other post-quantum KEMs.
4.2. BIKE
BIKE (Bit-Flipping Key Encapsulation) is a code-based
cryptographic system that uses Quasi-Cyclic
ModerateDensity Parity-Check (QC-MDPC) codes. It’s designed to
offer efficient key encapsulation while relying on the
hardness of decoding random linear codes, a
wellestablished hard problem in cryptography.</p>
        <p>BIKE is based on the decoding of QC-MDPC codes,
which involves error correction methods. This problem has
been studied for decades, and no quantum or classical
efficient algorithms are known to solve it. The core
cryptographic mechanism is the decoding process for
MDPC codes, which involves flipping bits to correct errors
in a way that only the legitimate parties can succeed.</p>
        <p>
          BIKE’s first building block is a public key encryption
scheme based on a variant of the Niederreiter framework.
The plaintext is represented by the sparse vector (e0, e1),
and the ciphertext by its syndrome. The decryption is
performed with a decoding procedure. Next, this PKE is
converted into an IND-CCA KEM with the application of
the Fujisaki-Okamoto transformation. For the scheme to be
truly IND-CCA, there must be conditions on the decoding
failure rate (also called DFR), which is the case here with the
chosen decoder [
          <xref ref-type="bibr" rid="ref26 ref27">26, 27</xref>
          ].
        </p>
        <p>As defined in the specifications, the parameters should
satisfy several constraints. The block length r should be a
prime number, and 2 should be primitive modulo r. The
parameter w should be such that w = 2d ≈ √n with d being
odd. In addition, the error weight should be such that t ≈ √n.
Instantiated parameters are present in Table 3.
While BIKE offers relatively compact ciphertext sizes, it
tends to require larger public keys compared to lattice-based
KEMs like Kyber.</p>
        <p>Public Key Size: Ranges from 1,254 bytes to 4,140
bytes, depending on the security level.</p>
        <p>Ciphertext Size: Approximately 154 bytes to 284 bytes.</p>
        <p>BIKE is relatively efficient in the key encapsulation
process due to the use of fast bit-flipping decoding
algorithms, although it can be slower than some
latticebased systems in some use cases. The reliance on
errorcorrecting codes is a tried-and-tested approach, giving
confidence in its long-term security against both classical
and quantum attacks.</p>
      </sec>
      <sec id="sec-4-2">
        <title>4.3. Classic McEliece</title>
        <p>
          Classic McEliece is one of the oldest and most established
post-quantum cryptosystems, first proposed in 1978. It
relies on the hardness of decoding random Goppa codes, a
task that has resisted efficient attacks for over four decades.
Classic McEliece has gained attention due to its
longstanding security record and robust resistance to quantum
attacks [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ].
        </p>
        <p>The original purpose is to encode data and transmit it on a
noisy channel, allowing the receiver to remove the errors to
get the correct message. If the decoder is kept secret and
cannot be deduced from the encoder, it makes encoding with
errors a one-way trapdoor function: the sender encodes with
the public encoder and adds as many errors as the decoder
can remove. The receiver with the decoder is then the only
one who can remove the errors and read the message.</p>
        <p>
          The public key size grows substantially from 261120
bytes at NIST level 1 to 1357824 bytes at NIST level 5c. The
private key size also sees a significant increment from 6492
bytes at level 1 to 14120 bytes at level 5c. These increases
align with the general principle that larger key sizes
translate into stronger security, making the system more
resilient against cryptographic attacks. The ciphertext size
and the session key size also increase as the NIST level
progresses, pointing to stronger security and larger
communication overheads [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ]. However, the session key
size remains consistent at 32 bytes, as its primary role is to
ensure confidentiality and integrity during a session,
regardless of the NIST level.
        </p>
        <p>Public key, bytes
261120
524160
1044992
1047319
1357824</p>
        <p>Private key, bytes
6492
13608
13932
13948
14120</p>
        <p>Ciphertext, bytes
96
156
208
194
208</p>
        <p>Session key, bytes
32
32
32
32
32
Classic McEliece is known for its very large public key sizes,
which are its primary drawback, but it has very small
ciphertext sizes and extremely fast decapsulation.</p>
        <p>Public Key Size: Up to 1 MB or more for higher
security levels.</p>
        <p>Ciphertext Size: 208 bytes.</p>
        <p>Although the public keys are large, the small ciphertext
size and fast decryption process make McEliece suitable for
high-performance applications where the size of the public
key is not a critical issue. The major disadvantage of
McEliece is the size of its public keys, which can be as large
as several hundred kilobytes to over a megabyte. This makes
it less practical for systems with bandwidth or storage
limitations.
4.4. HQC
HQC (Hamming Quasi-Cyclic) is another code-based
cryptographic system that uses Quasi-Cyclic codes to
achieve secure key encapsulation. HQC is based on the
hardness of decoding random linear codes but uses a
different type of code construction compared to Classic
McEliece and BIKE.</p>
        <p>HQC is built on the difficulty of decoding random linear
codes, which is believed to be a hard problem both for
classical and quantum computers.</p>
        <p>
          HQC uses SHAKE256 for multiple purposes e.g., as a
PRNG for fixed weight vector generation and random vector
generation in Key Generation, as a PRNG for fixed weight
vector generation in Encryption, and for hashing in
encapsulation and decapsulation. HQC-KEM uses
polynomial multiplication in various stages of its operation.
In HQC, the fundamental mathematical structure involves
cyclic codes, and polynomial operations over finite fields
play a crucial role in both the encryption and decryption
processes [
          <xref ref-type="bibr" rid="ref30">30</xref>
          ].
        </p>
        <p>Polynomial Multiplication is used in the public key
generation stage. The public key involves a codeword that
HQC’s key sizes are intermediate between those of McEliece
and BIKE, but its ciphertexts are generally larger.</p>
        <p>Public Key Size: Ranges from 2,249 bytes to 7,245
bytes.</p>
        <p>Ciphertext Size: Approximately 7,245 bytes to 7,870
bytes.</p>
        <p>HQC provides security levels aligned with NIST’s
requirements, targeting 128-bit and 256-bit classical security
levels.</p>
        <p>HQC is more efficient in terms of key generation and
encapsulation compared to Classic McEliece, while still
offering strong security guarantees. As a code-based
system, HQC benefits from decades of cryptographic
research, giving confidence in its resistance to quantum and
classical attacks. Compared to other post-quantum KEMs,
HQC produces relatively large ciphertexts, which may be a
disadvantage in bandwidth-constrained applications.
is derived from the multiplication of two polynomials, one
of which is a secret, and another is a random element. The
process relies on encoding the secret key, which consists of
small random polynomials, and performing multiplication
in a finite field to produce part of the public key.</p>
        <p>During the encapsulation process, the key encapsulator
generates a random message and encodes it using a public
codeword. The encoding procedure involves polynomial
multiplication between the message (represented as a
polynomial) and the public key polynomial. The ciphertext
is generated as the sum of a product of polynomials
(including the random polynomials and the public key)
along with some error terms. These multiplications are done
in a ring of polynomials, where coefficients are taken
modulo a prime number.</p>
        <p>On the receiver’s side, the decryption process also
involves polynomial multiplication. The receiver uses their
private key to multiply it with part of the ciphertext. By
multiplying the ciphertext polynomial by the private key
and removing the error components, the original message
can be recovered. The structure of the private key, being
sparse (i.e., consisting mostly of small entries), ensures that
this operation is efficient despite the potential for larger
polynomials.</p>
        <p>In all cases, these polynomial multiplications are
performed in a finite ensuring that the polynomials remain
manageable in size and that the modular arithmetic
preserves the structure of the quasi-cyclic codes.
Polynomial multiplication in HQC is typically implemented
using efficient algorithms such as the Number Theoretic
Transform (NTT), which is a variant of the Fast Fourier
Transform (FFT) for polynomials over finite fields, to speed
up the process of large polynomial multiplications. Thus,
polynomial multiplication is a critical and recurring
operation in the key generation, encryption, and decryption
steps of HQC-KEM.</p>
        <p>Public key, bytes
2249
4522
7245
4.5. SIKE</p>
        <p>Private key, bytes
56
64
72</p>
        <p>Ciphertext, bytes
4497
9042
14485</p>
        <p>SIKE (Supersingular Isogeny Key Encapsulation) is based on
isogeny-based cryptography, a relatively new and
promising post-quantum cryptographic approach. SIKE
uses the difficulty of finding isogenies (mappings) between
elliptic curves. While elliptic curve cryptography (ECC) is
vulnerable to quantum attacks, isogeny-based systems
remain secure.</p>
        <p>
          SIKE is protected by the computational supersingular
isogeny (CSSI) problem and allows for an IND-CCA2 key
establishment between two parties [
          <xref ref-type="bibr" rid="ref31">31</xref>
          ].
        </p>
        <p>The underlying hard problem for SIKE, the
Computational Supersingular Isogeny problem, involves
finding a secret isogeny (a specific type of function between
elliptic curves) between two given supersingular elliptic
curves. This is believed to be computationally infeasible,
even for quantum computers, making it a good foundation
for post-quantum security. SIKE provides IND-CCA2
security, which is a strong form of security for encryption
schemes. This means that even if an attacker can request
decryptions of ciphertexts of their choice, they cannot learn
any useful information about the encryption of a different
message. This ensures that the key establishment process
between two parties is secure even against active attackers
who can manipulate and intercept communications.</p>
        <p>SIKE primes are carefully chosen to optimize both
performance and security in the context of supersingular
elliptic curves and the supersingular isogeny problem. SIKE
uses a prime number  of a particular form to define the
finite field Fp over which elliptic curves are constructed. The
form of these primes allows efficient isogeny computations
and ensures that the curves used are supersingular.</p>
        <p>SIKE primes are of the form:</p>
        <p>p=2a*3b*f-1
where a and b are large integers.</p>
        <p>f is a small cofactor, typically set to 1 in many cases.</p>
        <p>The prime is of a size that ensures 128-bit, 192-bit, or
256-bit security levels, depending on the target.</p>
        <p>Designation
SIKEp434
SIKEp503
SIKEp610
SIKEp751</p>
        <p>Public key, bytes
330
378
462
564</p>
        <p>Private key, bytes
374
434
524
644
SIKE offers one of the smallest key and ciphertext sizes of
any other post-quantum cryptosystem, making it
particularly attractive for use in bandwidth-constrained
environments. However, it tends to have slower
performance compared to other post-quantum KEMs.</p>
        <p>Public Key Size: As small as 330 bytes.</p>
        <p>Ciphertext Size: Ranges from 346 to 596 bytes.</p>
        <p>SIKE’s compact key and ciphertext sizes make it one of
the most bandwidth-efficient post-quantum cryptosystems,
making it attractive for specific use cases where data size
and storage are a concern, despite its slower performance
compared to other schemes.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusions</title>
      <p>Cryptographers, researchers, and industry experts are
working together to develop and test these algorithms to
ensure their security and efficiency in real-world
applications. These algorithms are being evaluated for their
ability to resist both classical and quantum attacks as part
of the NIST Post-Quantum Cryptography Standardization
process. The goal is to identify cryptosystems that will be
secure in a future where quantum computers could break
existing cryptography, while also being efficient in
realworld applications.</p>
      <p>
        KEMs are critical for secure key exchange in
cryptographic protocols, enabling two parties to securely
establish a shared secret over an insecure channel. In
postquantum cryptography, various KEMs are being explored
for their security and practicality in terms of key sizes,
speed, and resilience against quantum attacks [
        <xref ref-type="bibr" rid="ref32">32</xref>
        ].
      </p>
      <p>The development of these KEMs involves close
collaboration between academia, industry, and government
organizations. The NIST process, for example, has provided
a platform where researchers can submit their
cryptographic algorithms for rigorous evaluation by the
global cryptographic community. This collaboration
ensures that these algorithms are tested for:</p>
      <p>Security: To withstand both classical and quantum
attacks.</p>
      <p>Performance: In terms of speed, key size, and memory
usage in practical applications.</p>
      <p>
        Real-World Implementation: Testing includes both
hardware and software implementations to ensure that the
algorithms are suitable for a range of use cases, from small
devices (like IoT) to high-performance systems (like cloud
servers) [
        <xref ref-type="bibr" rid="ref33 ref34">33, 34</xref>
        ].
      </p>
      <p>The ongoing development of post-quantum KEMs like
Crystal-Kyber, BIEK, HQC, Classic McEliece, SIKE, and
others is crucial to ensuring secure communication in a
quantum future. Each of these algorithms brings unique
advantages in terms of performance, security, and
efficiency, and the NIST competition is helping to refine
these technologies for eventual standardization and
widespread adoption.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <surname>L. K. Grover</surname>
            ,
            <given-names>A Fast</given-names>
          </string-name>
          <string-name>
            <surname>Quantum</surname>
          </string-name>
          <article-title>Mechanical Algorithm for Database Search</article-title>
          ,
          <source>Proceedings of the 28th Annual ACM Symposium on Theory of Computing</source>
          (
          <year>1996</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <surname>D. J. Bernstein</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Buchmann</surname>
          </string-name>
          , E. Dahmen, Code-based
          <string-name>
            <surname>Cryptography</surname>
          </string-name>
          (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <surname>Horpenyuk</surname>
            ,
            <given-names>I. Opirskyy</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Vorobets</surname>
          </string-name>
          ,
          <article-title>Analysis of Problems and Prospects of Implementation of PostQuantum Cryptographic Algorithms</article-title>
          , in: Classic, Quantum, and
          <string-name>
            <surname>Post-Quantum</surname>
            <given-names>Cryptography</given-names>
          </string-name>
          , vol.
          <volume>3504</volume>
          (
          <year>2023</year>
          )
          <fpage>39</fpage>
          -
          <lpage>49</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <string-name>
            <surname>Bernhardt</surname>
          </string-name>
          , Quantum Computing for Everyone, Cambridge, MA: MIT Press (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <string-name>
            <given-names>V.</given-names>
            <surname>Cini</surname>
          </string-name>
          , et al.,
          <string-name>
            <surname>CCA-Secure</surname>
          </string-name>
          (
          <article-title>Puncturable) KEMs from Encryption with Non-Negligible Decryption Errors</article-title>
          ,
          <source>Advances in Cryptology - ASIACRYPT 2020. Lecture Notes in Computer Science</source>
          , vol.
          <volume>12491</volume>
          . (
          <year>2020</year>
          ). doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>030</fpage>
          -64837-
          <issue>4</issue>
          _
          <fpage>6</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <string-name>
            <surname>Woodward</surname>
          </string-name>
          ,
          <source>Will Quantum Computers Be the End of Public Key Encryption? J. Cyber Secur. Technol</source>
          .
          <volume>1</volume>
          (
          <issue>1</issue>
          ) (
          <year>2016</year>
          ).
          <fpage>1</fpage>
          -
          <lpage>22</lpage>
          . doi:
          <volume>10</volume>
          .1080/23742917.
          <year>2016</year>
          .
          <volume>1226650</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          <string-name>
            <given-names>L.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <source>Cryptography Standards in Quantum Time: New Wine in an Old Wineskin? IEEE Security &amp; Privacy</source>
          <volume>15</volume>
          (
          <issue>4</issue>
          ) (
          <year>2017</year>
          )
          <fpage>51</fpage>
          -
          <lpage>57</lpage>
          . doi:
          <volume>10</volume>
          .1109/MSP.
          <year>2017</year>
          .
          <volume>3151339</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>P.</given-names>
            <surname>Hauke</surname>
          </string-name>
          , et al.,
          <source>Perspectives of Quantum Annealing: Methods and Implementations, Reports on Progress in Physics</source>
          <volume>83</volume>
          (
          <issue>5</issue>
          ) (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>J.</given-names>
            <surname>Bernstein</surname>
          </string-name>
          ,
          <article-title>Visualizing Size-Security Tradeoffs for Lattice-Based Encryption</article-title>
          , IACR Cryptol, ePrint
          <string-name>
            <surname>Arch</surname>
          </string-name>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>M.</given-names>
            <surname>Baldi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Santini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Cancellieri</surname>
          </string-name>
          .
          <article-title>Post-Quantum Cryptography based on Codes: State of the Art and Open Challenges</article-title>
          , AEIT International Annual Conference. (
          <year>2017</year>
          ). doi:
          <volume>10</volume>
          .23919/aeit.
          <year>2017</year>
          .
          <volume>8240549</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Casanova</surname>
            , et al.,
            <given-names>A Great</given-names>
          </string-name>
          <string-name>
            <surname>Multivariate Short Signature</surname>
          </string-name>
          , Submission to NIST (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>R. A.</given-names>
            <surname>Grimes</surname>
          </string-name>
          , Cryptography
          <string-name>
            <surname>Apocalypse</surname>
          </string-name>
          (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>A.</given-names>
            <surname>Bessalov</surname>
          </string-name>
          , et al.,
          <article-title>Implementation of the CSIDH Algorithm Model on Supersingular Twisted and Quadratic Edwards Curves</article-title>
          ,
          <source>in: Workshop on Cybersecurity Providing in Information and Telecommunication Systems</source>
          , vol.
          <volume>3187</volume>
          , no.
          <issue>1</issue>
          (
          <year>2022</year>
          )
          <fpage>302</fpage>
          -
          <lpage>309</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>A.</given-names>
            <surname>Bessalov</surname>
          </string-name>
          , et al.,
          <string-name>
            <surname>Modeling</surname>
            <given-names>CSIKE</given-names>
          </string-name>
          <article-title>Algorithm on Non-Cyclic Edwards Curves</article-title>
          ,
          <source>in: Workshop on Cybersecurity Providing in Information and Telecommunication Systems</source>
          , vol.
          <volume>3288</volume>
          (
          <year>2022</year>
          )
          <fpage>1</fpage>
          -
          <lpage>10</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>A.</given-names>
            <surname>Bessalov</surname>
          </string-name>
          , et al.,
          <string-name>
            <surname>Multifunctional</surname>
            <given-names>CRS</given-names>
          </string-name>
          <article-title>Encryption Scheme on Isogenies of NonSupersingular Edwards Curves</article-title>
          , in: Workshop on Classic, Quantum, and
          <source>PostQuantum Cryptography</source>
          , vol.
          <volume>3504</volume>
          (
          <year>2023</year>
          )
          <fpage>12</fpage>
          -
          <lpage>25</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>A.</given-names>
            <surname>Bessalov</surname>
          </string-name>
          , et al.,
          <article-title>CSIKE-ENC Combined Encryption Scheme with Optimized Degrees of Isogeny Distribution</article-title>
          ,
          <source>in: Workshop on Cybersecurity Providing in Information and Telecommunication Systems</source>
          , vol.
          <volume>3421</volume>
          (
          <year>2023</year>
          )
          <fpage>36</fpage>
          -
          <lpage>45</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>V.</given-names>
            <surname>Pastushenko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Kronberg</surname>
          </string-name>
          ,
          <article-title>Improving the Performance of Quantum Cryptography by Using the Encryption of the Error Correction Data</article-title>
          ,
          <source>Entropy</source>
          <volume>25</volume>
          (
          <issue>956</issue>
          ) (
          <year>2023</year>
          ). doi:
          <volume>10</volume>
          .3390/e25060956.
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>U.</given-names>
            <surname>Banerjee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Das</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. P.</given-names>
            <surname>Chandrakasan</surname>
          </string-name>
          ,
          <article-title>Accelerating Post-Quantum Cryptography using an EnergyEfficient TLS Crypto-Processor</article-title>
          ,
          <source>IEEE International Symposium on Circuits and Systems</source>
          (
          <year>2020</year>
          ). doi:
          <volume>10</volume>
          .1109/iscas45731.
          <year>2020</year>
          .
          <volume>9180550</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>M.</given-names>
            <surname>Kumar</surname>
          </string-name>
          .
          <article-title>Post-Quantum Cryptography Algorithm's Standardization and Performance Analysis</article-title>
          , Array,
          <volume>15</volume>
          (
          <year>2022</year>
          ). doi:
          <volume>10</volume>
          .1016/j.array.
          <year>2022</year>
          .
          <volume>100242</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>F.</given-names>
            <surname>Borges</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. R.</given-names>
            <surname>Reis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Pereira</surname>
          </string-name>
          .
          <article-title>A Comparison of Security and Its Performance for Key Agreements in Post-Quantum Cryptography</article-title>
          , IEEE Access,
          <volume>8</volume>
          (
          <year>2020</year>
          )
          <fpage>142413</fpage>
          -
          <lpage>142422</lpage>
          . doi:
          <volume>10</volume>
          .1109/access.
          <year>2020</year>
          .
          <volume>3013250</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <surname>Bellizia</surname>
          </string-name>
          , et al.,
          <string-name>
            <surname>Post-Quantum</surname>
            <given-names>Cryptography</given-names>
          </string-name>
          :
          <article-title>Challenges and Opportunities for Robust and Secure HW Design, IEEE International Symposium on Defect and fault tolerance in VLSI and Nanotechnology systems</article-title>
          (DFT) (
          <year>2021</year>
          )
          <fpage>1</fpage>
          -
          <lpage>6</lpage>
          . doi:
          <volume>10</volume>
          .1109/DFT52944.
          <year>2021</year>
          .
          <volume>9568301</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <given-names>L.</given-names>
            <surname>Chen</surname>
          </string-name>
          , et al.,
          <source>Report on Post-Quantum Cryptography, NIST Publications</source>
          (
          <year>2016</year>
          ). doi:
          <volume>10</volume>
          .6028/NIST.IR.
          <volume>8105</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <given-names>G.</given-names>
            <surname>Alagic</surname>
          </string-name>
          , et al.,
          <source>Status Report on the Second Round of the NIST Post-Quantum Cryptography Standardization Process, NIST Publications</source>
          (
          <year>2020</year>
          ). doi:
          <volume>10</volume>
          .6028/NIST.IR.
          <volume>8309</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <given-names>G.</given-names>
            <surname>Alagic</surname>
          </string-name>
          , et al.,
          <source>Status Report on the Third Round of the NIST Post-Quantum Cryptography Standardization Process, NIST Publications</source>
          (
          <year>2022</year>
          ). doi:
          <volume>10</volume>
          .6028/NIST.IR.
          <volume>8413</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <given-names>J.</given-names>
            <surname>Bos</surname>
          </string-name>
          , et al.,
          <string-name>
            <surname>CRYSTALS - Kyber: A CCA-Secure Module-Lattice-based</surname>
            <given-names>KEM</given-names>
          </string-name>
          ,
          <source>2018 IEEE European Symposium on Security</source>
          and
          <string-name>
            <surname>Privacy (EuroS&amp;P)</surname>
          </string-name>
          (
          <year>2018</year>
          )
          <fpage>353</fpage>
          -
          <lpage>367</lpage>
          . doi:
          <volume>10</volume>
          .1109/EuroSP.
          <year>2018</year>
          .
          <volume>00032</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <given-names>L.</given-names>
            <surname>Demange</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Rossi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A Provably</given-names>
            <surname>Masked</surname>
          </string-name>
          <article-title>Implementation of BIKE Key Encapsulation Mechanism</article-title>
          , Cryptology ePrint Archive (
          <year>2024</year>
          ). doi:
          <volume>10</volume>
          .62056/aesgvua5v.
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [27]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Lia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. -P.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <article-title>Security Analysis of the Classic McEliece, HQC and BIKE Schemes in Low Memory</article-title>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Inf</surname>
          </string-name>
          .
          <source>Secur. Appl</source>
          .
          <volume>79</volume>
          (
          <year>2023</year>
          ). doi:
          <volume>10</volume>
          .1016/j.jisa.
          <year>2023</year>
          .
          <volume>103651</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          [28]
          <string-name>
            <given-names>O.</given-names>
            <surname>Kuznetsov</surname>
          </string-name>
          , et al.,
          <article-title>Trade-offs in Post-Quantum Cryptography: A Comparative Assessment of BIKE, HQC, and Classic McEliece</article-title>
          , in: Classic, Quantum, and
          <string-name>
            <surname>Post-Quantum</surname>
            <given-names>Cryptography</given-names>
          </string-name>
          , vol.
          <volume>3504</volume>
          (
          <year>2023</year>
          )
          <fpage>12</fpage>
          -
          <lpage>25</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          [29]
          <string-name>
            <given-names>C.</given-names>
            <surname>Nugier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Migliore</surname>
          </string-name>
          ,
          <article-title>Acceleration of a Classic McEliece Postquantum Cryptosystem with Cache Processing</article-title>
          , in: IEEE Micro,
          <volume>44</volume>
          (
          <issue>1</issue>
          ) (
          <year>2024</year>
          )
          <fpage>59</fpage>
          -
          <lpage>68</lpage>
          . doi:
          <volume>10</volume>
          .1109/MM.
          <year>2023</year>
          .
          <volume>3304425</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          [30]
          <string-name>
            <given-names>R.</given-names>
            <surname>Azarderakhsh</surname>
          </string-name>
          , et al.,
          <source>Hardware Deployment of Hybrid PQC, Cryptology ePrint Archive</source>
          (
          <year>2021</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          [31]
          <string-name>
            <given-names>R.</given-names>
            <surname>Elkhatib</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Koziel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Azarderakhsh</surname>
          </string-name>
          , Faster Isogenies for
          <string-name>
            <surname>Quantum-Safe</surname>
            <given-names>SIKE</given-names>
          </string-name>
          , Topics in Cryptology - CT
          <string-name>
            <surname>-RSA</surname>
          </string-name>
          (
          <year>2022</year>
          )
          <fpage>49</fpage>
          -
          <lpage>72</lpage>
          . doi:
          <volume>10</volume>
          .1007/978- 3-
          <fpage>030</fpage>
          -95312-
          <issue>6</issue>
          _
          <fpage>3</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          [32]
          <string-name>
            <surname>M. Raavi1</surname>
          </string-name>
          , et al.,
          <article-title>Security Comparisons and Performance Analyses of Post-Quantum Signature Algorithms</article-title>
          , ACNS 2021:
          <article-title>Applied Cryptography and Network Security (</article-title>
          <year>2021</year>
          )
          <fpage>424</fpage>
          -
          <lpage>447</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>030</fpage>
          -78375-4_
          <fpage>17</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          [33]
          <string-name>
            <given-names>O. I.</given-names>
            <surname>Harasymchuk</surname>
          </string-name>
          , et al.,
          <source>Generator of Pseudorandom Bit Sequence with Increased Cryptographic Security, Metallurgical and Mining Industry: Sci. Tech. J. 5</source>
          (
          <year>2014</year>
          )
          <fpage>25</fpage>
          -
          <lpage>29</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          [34]
          <string-name>
            <given-names>V.</given-names>
            <surname>Maksymovych</surname>
          </string-name>
          , et al.,
          <source>Combined Pseudo-Random Sequence Generator for Cybersecurity, Sensors</source>
          <volume>22</volume>
          (
          <year>2022</year>
          ). doi:
          <volume>10</volume>
          .3390/s22249700.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>