noise_spec VS age

Because I always want to identify the solution when we point to the problem:

https://doc.libsodium.org/

http://noiseprotocol.org/

If you're not looking to share files but instead need a full communications protocol, the question gets more complex. TLS is the most commonly used encryption layer, and lots of other protocols use TLS to encrypt their traffic. In the rare cases where it's not suitable, the Noise Protocol Framework works to design a secure protocol for the necessary uses.

TLS Client Authentication formalizes this, as do several patterns in the Noise protocol framework.

As you now know, I have implemented a whole cryptographic library with a similar API to Libsodium’s. In addition I’ve worked on authenticated key exchange (similar to Noise), as well as PAKE (symmetric and augmented). And I’ve realised that the whole NaCl family of libraries, including NaCl, Libsodium, TweetNaCl, and Monocypher, are all too low-level for regular people to use safely.

Many other messaging apps use a separate client/server encryption protocol for this purpose. Several use TLS. The WhatsApp Security Whitepaper notes they use the Noise protocol when the client is a mobile device.

What are real world implementations of the Noise Protocol? https://github.com/noiseprotocol/noise_spec/blob/v34/noise.m...

Quick search shows WireGuard protocol, but I am not sure if how much of the WireGuard protocol is the same as the Noise Protocol.

https://www.wireguard.com/formal-verification/

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.