[ssh_x509] PQ Updates for x509

[ssh_x509 at roumenpetrov.info]

Hi Roumen,
It appears that OpenSSL 3.5 does have ml-dsa support (https://openssl-library.org/post/2025-04-08-openssl-35-final-release/) so I think that should be good to go when you are ready for it.

Thanks,
Alex





On Friday, June 27, 2025 at 01:57:58 AM EDT, <ssh_x509 at roumenpetrov.info> wrote: 





Hi Alex,

На 27.06.25 г. в 0:06 ч., ssh_x509 at roumenpetrov.info написа:
> Hi Roumen,
> Thank you for the clarifications. Do you have any plans to add any postquantum algorithms to the x509 based public key algorithms? Something like maybe x509v3-ssh-mldsa? I don't currently see such where I might expect (ssh-xkalg.c, etc) in your hybrid demo.

Please note that now "hybrid demo" is not active. It is based on 
compound key model from provider. New implementation will use "single" 
keytype with own compound.

ML-DSA X.509 requires support for crypto library and as of today I do 
not know OpenSSL implementation status.

Main priority is ensure full compatibility with 3.0 API. Remains 
serialisation of keys.
Another point is keys used in kex - serialisation and deserialisation. 
This part is related to post-quantum algorithms as well.
Maybe cost is to drop support for DH kex - based on some OpenSSL issues.

Remark: now code is fully OpenSSL 1.0-1.1.1 compatible. Also full 
compatibility with 3.0 API means use of FIPS validated provider.

My expectation is that after KEX we could think about implementation of 
new X.509 certificate based algorithms. Dunno what is status of 
functionality in OpenSSL 3.5+.


> 
> Thank you,
> Alex
> 
> 
> 
> 
> 
> 
> On Wednesday, June 25, 2025 at 01:45:40 PM EDT, <ssh_x509 at roumenpetrov.info> wrote:
> 
> 
> 
> 
> 
> Hi Alex,
> 
> На 25.06.25 г. в 1:47 ч., ssh_x509 at roumenpetrov.info написа:
>> Hi Roumen,
>> I noticed your experiments on PQ KEMs. Do you have any plans to add any postquantum to the x509 support?
> 
> First let me clarity that PQ is supported with current releases.
> It is not announced as model uses statically linked code. This code does
> not include any upstream patches .
> For protocol definition of ENABLE_KEX_SNTRUP761X25519 and
> ENABLE_KEX_MLKEM768X25519 as CPPFLAGS at configuration time will
> activate "static" implementation.
> 
> 
> Branch hybrid demo is different. It uses "encapsulation"(PQ algorithm)
> and "composite"(hybrid) key based on OQS provider.
> 
> 
> 
> Now next release is in progress.
> 
> After publication I will start with implementation based on
> cryptographic library. This is my next task.
> OpenSSL should be 3.5. Maybe OQS provider will be supported as well.
> Composite mode will be managed in ssh code.
> 
> 
> All 3 ML-KEM will be supported by default if provided by library.
> NTRU prime out of scope - support was removed from OQS-provider about
> two year ago. It could be supported by default only if someone write
> provider based implementation.
> 
>>
>> Thank you,
>> Alex
> 
> 
> Regards,
> Roumen Petrov
> 
> 
> 
> _______________________________________________
> ssh_x509 mailing list
> ssh_x509 at roumenpetrov.info
> http://roumenpetrov.info/mailman/listinfo/ssh_x509_roumenpetrov.info

> 
> _______________________________________________
> ssh_x509 mailing list
> ssh_x509 at roumenpetrov.info
> http://roumenpetrov.info/mailman/listinfo/ssh_x509_roumenpetrov.info


_______________________________________________
ssh_x509 mailing list
ssh_x509 at roumenpetrov.info
http://roumenpetrov.info/mailman/listinfo/ssh_x509_roumenpetrov.info