4 ms·
All comments so far seem to disagree with the author ("PGP remains the gold standard, and it's here to stay", "PGP is a failure because it has no critical mass,
by lucb1e 10y ago
All comments so far seem to disagree with the author ("PGP remains the gold standard, and it's here to stay", "PGP is a failure because it has no critical mass, so author writes ~1300 lines of C code that will never reach critical mass, reinventing gpg-zip", "why re-invent the wheel").
But there are two different things here: encrypted communications and archiving files. The author wrote software for the latter and just gave up on the former.
I don't think it's particularly nice to just drop PGP email support (more and more of my peers are using it), but the other part is still interesting. It uses memory-hard key derivation, elliptic curve cryptography, and some other details that make this thing very good (for its job, at least). This is all fairly state of the art: it has been around for years, but very few systems actually use memory-hard key derivation or elliptic curve crypto. Having more tools use this stuff exposes it more and works encouragingly to others who are also in a position to choose algorithms for new/upgrading projects. And it provides another alternative for those who wish to encrypt files for archiving.
- VLM 10y ago"encrypted communications and archiving files" Independent marketing plan, identical backend tech. If the goal was security should have just used gpg or openssl with a very small shell script wrapper around it instead of rolling his own. On the other hand if the goal was writing crypto obviously it achieved that, even if the spec isn't optimal.