Sequoia 1.3

Good to see this project make progress -- well done to the development team. Whatever you think about pgp, it's not going away anytime soon, and a new implementation is an opportunity to brush away some cobwebs and even improve the ecosystem[1].

[1] https://sequoia-pgp.org/holistic-approach/

It's not a tutorial in the classic sense, but as the CLI is rather simple, and as there are examples, I'd point you at the official docs (man page like):

https://docs.sequoia-pgp.org/sq/index.html

The sub commands feel like they are pretty much self-explanatory to me, e.g., encrypt, decrypt, verify are pretty clear in what they will do, and the options for those sub-commands seem not to cryptic either to me, but that's naturally a bit opinionated.

Besides that the initial release news article of the sq tool has some quick demo: https://sequoia-pgp.org/blog/2021/01/26/202101-sq-release/

What would be your use cases for sq?

Great!

Perhaps coincidentally, on PGP 30th birthday!

With all the great encryption utilities like age[0], Signal, or Veracrypt, can anyone please tell me what the point is in using pgp anymore? It's old, it's clunky, it requires careful use to be safe.

Why not use something more modern?

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

I'm not sure where that's the case, but it's certainly not the case with cryptography, where "clunky" means "mired in design decisions made before the era of authenticated cryptography".

To me, "old and clunky" also tends to imply "memory unsafe", or "written in Perl so old that a pipe filter in the wrong place in the input coughs up a shell", or "better make sure nobody's name is O'Connor because that includes SQL metadata", or "lol remember temp file races". But I'm prepared to concede that there may be places where the old stuff is better than the new, and eager to hear examples.