lk/data/gpg.md

120 lines
1.9 KiB
Markdown
Raw Normal View History

2022-01-16 18:20:39 +00:00
---
title: "gpg"
tags: [ "Documentation", "data" ]
---
2020-02-07 23:06:49 +00:00
# Making keys
2020-01-02 00:04:35 +00:00
Generate keys:
```bash
gpg --gen-key
```
2020-01-02 00:04:35 +00:00
Follow the guide.
# Encrypting a file
```bash
gpg -r malinfreeborn@posteo.net -e file
```
2020-01-02 00:04:35 +00:00
`-r` specifies the recipient.
Check you have an encrypted version of your file.
# Changing Expiration Dates
gpg --list-keys
... and then use the second part of 'pub', which is the ID. But that's not appearing here so... on with gpg2?
# Making encrypted files with a local password
Make a password with a password (cypher encryption).
```bash
gpg -c --output passwords.txt
```
2020-01-02 00:04:35 +00:00
or
```bash
gpg -c > passwords.txt
```
2020-01-02 00:04:35 +00:00
Put in a password.
Write message then stop with Ctrl+d.
Get the message back out the file with:
```bash
gpg -d passwords.txt
```
2020-01-02 00:04:35 +00:00
2021-10-21 19:46:03 +00:00
# Circles of Trust
Search for a key at any key store:
```bash
gpg --search-keys nestorv
```
2021-10-21 19:46:03 +00:00
Once you've made a decision about someone:
```bash
gpg --list-keys
```
2021-10-21 19:46:03 +00:00
You get something like this:
```
pub rsa3072 2021-08-15 [SC] [expires: 2023-08-15]
CD30421FD825696BD95F1FF644C62C57B790D3CF
uid [ultimate] Malin Freeborn <malinfreeborn@posteo.net>
sub rsa3072 2021-08-15 [E] [expires: 2023-08-15]
```
Notice the long, ugly, string - CD30421FD825696BD95F1FF644C62C57B790D3CF - and how horribly ugly it is.
This is a fingerprint.
You can now decide the trust level (this stays on your computer).
```bash
gpg --edit-key *CD30421FD825696BD95F1FF644C62C57B790D3CF*
```
2021-10-21 19:46:03 +00:00
2021-10-21 19:48:22 +00:00
Once you're in the interface, type `trust`.
2021-10-21 19:46:03 +00:00
```bash
gpg --sign-key alice@posteo.net
```
2021-10-21 19:46:03 +00:00
2021-11-09 01:36:24 +00:00
Then send those trusted keys up to a server, so people can see you have verified them:
```bash
gpg --send-keys *024C6B1C84449BD1CB4DF7A152295D2377F4D70F*
```
2021-11-09 01:36:24 +00:00
2021-10-21 19:46:03 +00:00
# Refresh Keys
```bash
gpg --refresh-keys
```
2021-10-21 19:46:03 +00:00
2022-05-01 18:53:16 +00:00
# Export
2023-04-04 15:35:17 +00:00
Your public key:
```bash
gpg --output *me*.gpg --armor --export
```
2022-05-01 18:53:16 +00:00
2023-04-04 15:35:17 +00:00
or
```bash
gpg --export -a *person@email.tld* > *my_key*.pub
```
2023-04-04 15:35:17 +00:00