6 ms·
I would love to see this used in a FIPS-compliant variant of age[1] for archival file encryption use cases. We had banking industry auditors veto age for this u
by tatersolid 2y ago
I would love to see this used in a FIPS-compliant variant of age[1] for archival file encryption use cases. We had banking industry auditors veto age for this use case due to the use of ChaCha instead of AES (they were fine with the X25519 public key part of age which I think was somewhat recently approved by NIST).
I’ve no experience with golang but it seems like it should drop right in based on the age spec. I might give it a shot if time ever permits. I guess I should call it “cage” as in “compliant actually good encryption”
1: https://github.com/FiloSottile/age https://github.com/FiloSottile/age
- yencabulator 2y agobge, bureaucratic good encryption.
- jmprspret 2y ago> “compliant actually good encryption” an oxymoron, perhaps
- d-z-m 2y agoalso an unfortunate acronym
- candiddevmike 2y agoFWIW Go doesn't have an implementation of XAES in the stdlib yet, there's only the reference implementation in C2SP.
- 38 2y agoThank goodness. I am kind of sick of the constant churn in the crypto package. I get that you want to keep up to date with security, but the entire crypto tree is basically a playground for Filippo Valsorda at this point. Meanwhile stuff that I actually need like CMAC is "won't fix"
- tptacek 2y agoWhat's another language with a stdlib that includes CMAC?
- rdpintqogeogsaa 2y agoZig[1]. [1] https://ziglang.org/documentation/0.11.0/std/#A;std:crypto.auth.cmac https://ziglang.org/documentation/0.11.0/std/#A;std:crypto.a...
- ramchip 2y agoErlang / Elixir
- tptacek 2y agoLink? Does Elixir even have cryptography in the stdlib?
- 38 2y ago[flagged]
- kbolino 2y agoWhat churn does the crypto package get? It's part of the standard library and so bound by the compatibility promise, which basically freezes existing things in place.
- Retr0id 2y ago> they were fine with the X25519 public key part of age which I think was somewhat recently approved by NIST As far as I can tell, Ed25519 is approved (FIPS 186-5), but X25519 is still not (yet).