5 ms·
It’s used for more than just email. For example, you can sign packages on for Pacman on Arch Linux with GPG (https://wiki.archlinux.org/title/Pacman/Package_sig
by noahtallen 2y ago
It’s used for more than just email. For example, you can sign packages on for Pacman on Arch Linux with GPG (https://wiki.archlinux.org/title/Pacman/Package_signing https://wiki.archlinux.org/title/Pacman/Package_signing), and they have you configure public key servers, which includes openpgp. Now, if I had set that up for package signing and other personal uses (like SSH keys, git commit signing, etc), that doesn’t mean I have my email set up to be encrypted.
You should 100% be able to set a flag on the key server what you are set up to automatically receive using the key.
- aborsy 2y agoThere is a key for encryption, signing, authentication and certification in OpenPGP. The flags are C, E, S, A. The use cases are separate. Perhaps another flag for automatic vs non automatic would help.
- jsjohnst 2y agoEncryption is not just for encrypted emails.
- soraminazuki 2y agoIn theory. In practice, published PGP encryption subkeys has only seen adoption in emails. Besides, is the criticism that people are using published keys for email? It seems people are outraged that they received encrypted data using keys that they themselves advertised. The specific medium for data transfer doesn’t seem to matter here.
- nulbyte 2y agoThere are separate flags for communications (like email) and storage (like files). https://datatracker.ietf.org/doc/html/rfc4880#section-5.2.3.21 https://datatracker.ietf.org/doc/html/rfc4880#section-5.2.3....
- Macha 2y agoGreat, but while the encryption vs signing choice is presented by common software (albeit in a way that does not make this consequence clear), it completely does not present the encrypt for communication and encrypt for storage options.