You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the real PGP, you can have someone's PGP public key which contains cool metadata such as email address. For some reason, people thing sharing a PGP public key is hard. But people don't think ssh-keys are hard.
This omits many of the cool parts of PGP. So a key is never signed, so there is no trust model. There is also no public key metadata.
The times I seen PGP used in practice, one person creates a key on the spot, and sends their publickey over email. The PGP trust model does not exist here either.
So the idea is like PGP but remove all the bits that make it hard to use and understand. People always use it wrong anyway.
gpg -ear [email protected] < input-file
will also encrypt a file with a recipient's public key. Does this do something different?The text was updated successfully, but these errors were encountered: