-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In message <[email protected] il.com>, Wei Chuang <[email protected]> writes
>FWIW I looked into BoringSsl ><https://boringssl.googlesource.com/boringssl/+/main/pki/signature_algorithm.h>, >BouncyCastle ><https://www.bouncycastle.org/documentation/specification_interoperability/#algo >rithms-and-key-types> >and Tink ><https://boringssl.googlesource.com/boringssl/+/main/pki/signature_algorithm.h> >signature >algorithms and I don't see hybrid support on their official sanctioned >support pages. (There are hints in commit comments that there might be >support in the future) Proponents suggest creating one's own hybrid >implementation, but my worry is that it still involves implementing your >own crypto, which presents an interoperability and security risks. There is a little more to composite algorithms beyond just splitting a key into two parts and then gluing the output strings back together again, but not all that much ! How to do it is covered in <https://datatracker.ietf.org/doc/html/draft-ietf-lamps-pq-composite- sigs-19> If you really wish to stick with your favourite crypto library (rather than one that provides what you need) then impleenting the mechanisms from the LAMPS draft is hardly, in my view "implementing your own crypto" especially since, in the email context, I do not see side- channel timing attacks as ever being of concern. - -- richard @ highwayman . com "Nothing seems the same Still you never see the change from day to day And no-one notices the customs slip away" -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1 iQA/AwUBatVltmHfC/FfW545EQLoNwCgjOb51SF28OhByiWQtatj0RaculoAn0xm QFLakBRPgSELoxIM3j6zhwyw =OeKN -----END PGP SIGNATURE----- _______________________________________________ Ietf-dkim mailing list -- [email protected] To unsubscribe send an email to [email protected]
