Reversing 'France Identité': The New French Digital ID

Re:Reversing 'France Identité': The New French Digital ID by runeks on Friday October 06, 2023 @10:09AM (#37791001)

I agree that runtime algorithm negotiation makes sense to avoid sometimes. So just make a spec that factors out the algorithm, and make the choice of algorithm a compile-time thing.

Then there's no need to hardcode anything in the spec, you can just say you're using the protocol RFC-12345-ChaCha20Poly1305 — with RFC-12345 being the spec that leaves out the algorithm.

[ Parent | on HN ]

Re:Reversing 'France Identité': The New French Digital ID by qweqwe14 on Friday October 06, 2023 @11:13AM (#37791863)

Yes, that's pretty much what I meant by "standardized". You'd be able to pick AEAD cipher, KDF, signature algorithm, KEX algorithm etc., while the spec would only describe the protocol itself without enforcing specific algorithms. Noise Protocol pretty much does this already: you provide a string that describes the set of algorithms you will be using, e.g. "Noise_NN_25519_ChaChaPoly_BLAKE2s"

[ Parent | on HN ]