Hey Crypto Twitterland. #Kubernetes prefers AES CBC (without HMAC!!) over AES GCM for encryption at rest (probably the fear the AES GCM forbidden attack, see the rotation note). Do you agree? https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/ …
-
-
then make the default xsalsa and say "if you need a lower security level for fips compliance reasons chose this" for gcm.
-
I suggest asking
@smarterclayton who to talk to about it. I am surprised XSalsa is even an option in the first place (near-zero interoperability or compliance benefit), and I can't reverse-engineer the rationale for the other options provided either.
End of conversation
New conversation -
-
-
How to grease the regulatory wheels to get X{Salsa20/20,ChaCha20}-Poly1305 + X25519 + Ed25519 approved for use in FIPS-140?
-
Curve25519/448 is already in approval process, and X25519/448 "will be considered". NIST is aware of these algorithms, it's just a very slow process.https://csrc.nist.gov/News/2017/Transition-Plans-for-Key-Establishment-Schemes …
-
I wonder if that includes Ed25519 support
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.