Ic mceliece is the large size of its public keys However, there are techniques hat typical internet applications can use to share the cost of each public key across many ciphertexts This document specifies how classic mceliece key encapsulation mechanism (kem) is used to generate keys in the internet key exchange version 2 (ikev2) protocol. “a public key cryptosystem based on algebraic coding theory”. The public key sizes (261 kb for mceliece348864) would however be problematic in current (e)sims My understanding is that the mceliece348864 parameters were chosen to maximize security.
If you want your program to be portable with stack allocation and not unexpectedly crash, you should probably run the entire key exchange in a dedicated thread with a large enough stack size. With mceliece348864, we have a level 1 security level with a public key size of 261,120 bytes, a private key size of 6,492 bytes, and a cipher text size of 128 bytes Mceliece460896 has a level 3 security level with a public key size of 524,160 bytes, a private key size of 13,608 bytes, and a cipher text size of 188 bytes For applications with cryptographic performance constraints Classic mceliece has very large public keys but very small ciphertexts
WATCH
