pycryptodome VS age

PyCryptodome

Install pycryptodome instead, it's forked from pycrypto (which is dead) and is actively maintained by the same team.

The specific bug you are having is in this issue of PyCrypto. That said, tnote should move on as PyCrypto is no longer maintained.. Ideally, tnote could migrate to PyCryptodome which is a near drop in replacement for PyCrypto, so "potentially" a single line of code change.

Possibly not a termux only issue (see this).

I know what you mean and I understand your concern. As it currently stands, I can say with a high level of confidence (although not complete) that Picocrypt is very secure. That's because Picocrypt uses ChaCha20, which is a simple cipher to implement correctly and without errors. It's extensively documented. I have a solid understanding of cryptography and I carefully choose a Python cryptography library with over 1k stars do implement ChaCha20. I know that there's a lot of responsibility when making security software, which is why I'm accepting donations to get Picocrypt audited as soon as possible (ideally within a year). Thanks for your feedback, I appreciate it.

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.

I wouldn't use OpenSSL personally. If you just need simple but secure symmetric encryption, checkout the scrypt(1) encryption utility from Tarsnap. If you need support for public keys, check out age(1).