Dear UTA Working Group,
first I want to introduce myself. I am not an engineer, but
an IT-technician with special interest insecurity in general
and cryptography in special.
If yes,
I am suggesting the following Baseline Requirements. With the upcoming
publication of RFC 9846 (draft-ietf-tls-rfc8446bis-14 by Eric Rescorla),
I believe now is the perfect time to start a 9325bis effort to align the
operational Best Current Practices with this latest revision of the
protocol.
If yes,
I am suggesting following Baseline Requirements:
1. KEY EXCHANGE
Primarily ECDHE-X448 and ECDHE-X25519 should be required.
Backup: NIST P-256 (secp256r1).
All other mechanisms may be implemented but should be considered
optional.
2. SIGNATURE MECHANISMS
Primary Ed448 and Ed25519 shou7ld be used.
Backup ECDSA with NIST P-256 (secp256r1)
Legacy RSASSA-PSS to be deprecated.
3. DATA ENCRYPTION MECHANISMS
Baseline should exclusively consist of AEAD mechanisms:
Primarily AES-256-GCM and ChaCha20-Poly1305
Backup: AES-256-CCM and AES-128-GCM
I am proposing these changes specifically from a system administration
and risk management perspective. My goal is to reduce complexity and
focus on modern, robust defaults that are easy for auditors to verify in
practice. We should avoid carrying over legacy contradictions for the
sake of mere compatibility.
Please keep me in CC as I am not subscribed to this list.
Regards,
Timo Gerke
--
If you think technology can solve your security problems,
then you don't understand the problems and you don't
understand the technology.
Bruce Schneier, amerikanischer Kryptograph
_______________________________________________
Uta mailing list -- [email protected]
To unsubscribe send an email to [email protected]
