add pgp notes
This commit is contained in:
68
active/security_pgp/pgp.md
Normal file
68
active/security_pgp/pgp.md
Normal file
@@ -0,0 +1,68 @@
|
||||
# PGP
|
||||
|
||||
- [PGP](#pgp)
|
||||
- [Searching for Keys](#searching-for-keys)
|
||||
- [Fedora KDE](#fedora-kde)
|
||||
- [Seahorse](#seahorse)
|
||||
- [Evolution Email](#evolution-email)
|
||||
- [Android](#android)
|
||||
- [OpenKeychain](#openkeychain)
|
||||
- [Fair Email](#fair-email)
|
||||
|
||||
## Searching for Keys
|
||||
|
||||
I publish all my keys to <https://keys.openpgp.org>
|
||||
|
||||
## Fedora KDE
|
||||
|
||||
### Seahorse
|
||||
|
||||
Taken from <https://riseup.net/en/security/message-security/openpgp/gpg-keys>
|
||||
|
||||
1. Launch Seahorse. It should be installed by default.
|
||||
2. Select GnuPG keys.
|
||||
3. Select the + sign to create a new key.
|
||||
4. Select PGP Key.
|
||||
5. Enter your email and the name you would like to be associated with the
|
||||
key. This doesn’t need to be your real name.
|
||||
6. Select advanced options.
|
||||
7. Encryption type should be RSA.
|
||||
8. Key strength should be 3072.
|
||||
9. Expiration date should be within less then two years. You can always
|
||||
extend the key expiration as long as you still have access to the key,
|
||||
even after it has expired. Why should I set an expiration -.
|
||||
10. Enter a strong password that you can remember. If you forget this
|
||||
password, it cannot be recovered and any encrypted data you have using it
|
||||
for, including emails, will be permanently inaccessible.
|
||||
11. The computer will now generate the key, which may take some time. After
|
||||
this, you will have an OpenPGP key pair that is ready to be used—Great!
|
||||
You can manage the key options, export the public key, change the
|
||||
password, delete and/or revoke the key, and perform other key adjustments
|
||||
through the Seahorse user interface or the command line.
|
||||
12. Optional: At this point, you can publish your public key to a key server
|
||||
where people can request it remotely to be able to send encrypted data
|
||||
and emails to you. Before you continue, please make sure you have
|
||||
selected a good keyserver. Once you are ready:
|
||||
1. Select the Key(s) you want to publish. Hold Ctrl and click to select
|
||||
more than one, or press Ctrl+A to select all keys.
|
||||
2. Navigate to Remote → Sync and Publish Keys…
|
||||
3. Press the Key Servers button.
|
||||
4. Publish the keys to any keyserver (select one if the “Sync” button was
|
||||
grayed out in the previous screen); they all synchronize with each
|
||||
other, so your key will be on each one.
|
||||
5. Recommended: Check the Automatically retrieve keys from key servers
|
||||
but do not check the Automatically synchronize modified keys with key
|
||||
servers check boxes. Instead, please consider using parcimonie.
|
||||
6. Press the Close button and then the Sync button to synchronize your
|
||||
keys.
|
||||
|
||||
Your public key is now published on the key servers and is accessible to
|
||||
others!
|
||||
|
||||
### Evolution Email
|
||||
|
||||
## Android
|
||||
|
||||
### OpenKeychain
|
||||
|
||||
### Fair Email
|
||||
Reference in New Issue
Block a user