fiat-crypto VS age

> Both your comment here and some stuff FiloSottile implied in the comment above seem like they would be (largely) mitigated by what the "Go 1.20 Cryptography" post mentions about using formally verified primitives that are generated by "fiat-crypto".

> Beyond the curve primitive, wouldn't the majority of the code involved be shared/identical? These are closely related curves, not some oddball algorithm that requires a bespoke implementation.

Well, fiat-crypto only provides the curve implementations.

Each language, library, etc. that wants to support ed448 will need a SHAKE256 implementation too. That has historically not been a safe addition, in practice.

Also, I don't see Ed448 on here (but I do see P448?): https://github.com/mit-plv/fiat-crypto/tree/6e6809be8290a7d7...

I think this is a more interesting URL: https://github.com/mit-plv/fiat-crypto/issues/902

Hi, maintainer of the crate

The formal verification comes from [fiat-crypto](https://github.com/mit-plv/fiat-crypto), which generates the Rust code of the underlying Curve25519 field arithmetic. Correctness is checked by Coq.

Mention of fiat-crypto was included in the original posts on Reddit/Lobste.rs but seems it was missed in this cross-post.

Orion now supports X25519 (Diffie-Hellman over Curve25519), which uses formally-verified field arithmetic generated by fiat-crypto. Additionally, a lot of focus was put into hardening the CI/CD of the crate along with added support for serde. This work was championed by /u/vlmutolo.

I have great hopes for formal verification: - https://www.usenix.org/conference/usenixsecurity17/technical-sessions/presentation/bond - https://github.com/project-everest/hacl-star - https://github.com/mit-plv/fiat-crypto - https://saw.galois.com/

A list of projects using the code generated by fiat-crypto: https://github.com/mit-plv/fiat-crypto/issues/902

age

and echoing the result after converting to an age private key

I like that https://github.com/FiloSottile/age has small public keys.

> something fresh

It exists, it's called age..

Some random links

https://github.com/FiloSottile/age

https://www.reddit.com/r/crypto/comments/hr64hr/state_of_age...

https://github.com/FiloSottile/age/discussions/432

> (Acquiring keys, rotating keys, identifying compromised keys, and most importantly either reaches a large enough percentage of emails..

Oh nevermind, age doesn't do any of that. Indeed, it doesn't even do email https://github.com/FiloSottile/age/issues/93

Encrypted secrets thanks to SOPS and Age

I never heard of "Age" before this post. Thank you to share. If others are interested to learn more, here are two other interesting posts about Age:

https://github.com/FiloSottile/age/discussions/432

https://words.filippo.io/dispatches/age-authentication/

of all things I was able to resolve the issue via this github issue: https://github.com/FiloSottile/age/issues/370#issuecomment-1...

Why keep something secret on a public repo? Is that not an oxymoron?

Also, I’m terms of encryption something like age[0] makes it much easier to not shoot yourself in the foot.

[0] https://github.com/FiloSottile/age

Why RSA specifically? For backups, I recommend Tarsnap. But if you really don't want to pay for encrypted cloud hosting, then check out age encryption.