forked from open-quantum-safe/openssh
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This aligns the algorithms supported by the OQS OpenSSH fork with the algorithms available in liboqs. - Added support for ML-KEM-IPD using the ML-KEM alias and the names/curves documented by the [PQ SSH draft RFC](https://datatracker.ietf.org/doc/draft-kampanakis-curdle-ssh-pq-ke/). - Added support for ML-DSA-IPD using the ML-DSA alias following the conventions from the Dilithium implementation. The Dilithium signatures have been disabled. - Updated from BIKE Round 3 to Round 4. This adds a new parameter set for BIKE-L5. - Added support for the Falcon PADDED format. It is disabled by default to preserve entries in the bit-mask. - Added support for MAYO. The level 1 variant is left disabled. The KEX algorithms specified by the draft RFC do not match the security level pairing convention followed by Kyber so we chose to prefer the pairings specified in the document. There were no proposed parameter sets for ML-KEM-512 so we defaulted to the conventional parameters. x25519 hybrids are currently not handled by the oqs-openssh fork so we've omitted `mlkem768x25519-sha256` support for now. This does not add support for sntrup761 as that requires handling the conflict with the upstream OpenSSH implementation. Related to Issue open-quantum-safe#163 Signed-off-by: gcr <gcr@amazon.com>
Showing
29 changed files
with
1,665 additions
and
415 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.