|
Actions:
|
2024-10-21 16:18 AEST by Arthur Barrett - Quantum safe encryption (openssl 3.x).
This could be as 'simple' as support for post-quantum key exchange and authentication and ciphersuites in
the TLS protocol.
https://openquantumsafe.org/applications/tls.html
Through to SSH:
https://openquantumsafe.org/applications/ssh.html
Digitally sign versions with Cryptographic Message Syntax similarly to how S/MIME encrypts and signs MIME
data.
https://openquantumsafe.org/applications/smime.html
and
https://en.wikipedia.org/wiki/Cryptographic_Message_Syntax
here is someones attempt at this:
https://github.com/exaexa/codecrypt
I've bad this bug 'windows' focussed, as I guess I just assume linux or unix has the responsibility of updating
their libraries to handle this, but on Windows, as long as we provide our own openssl this is more our
responsibility? There is a bug that we should STOP this - and this would be a good reason for it. see bug
7851 "win: native windows sserver protocol? why do we use openssl not schannel (ssl)?"
But for general encryption or signing then maybe it's not a windows specific thing?
see:
bug 6141 enh: signing - as in digital signatures stored as revision property
bug 7095 win: enh: IFS/kernel: a driver to write encrypted files
bug 7096 client: encrypt on checkout
bug 7505 encrypt repository files
bug 7868 enh: win: rm: zip and encrypt/password protect |