updated section regarding gpg
All checks were successful
continuous-integration/drone/push Build is passing

This commit is contained in:
surtur 2020-03-18 04:23:18 +01:00
parent 48daa2888b
commit f962f4969c
Signed by: wanderer
GPG Key ID: 19CE1EC1D9E0486D
2 changed files with 18 additions and 21 deletions

@ -4,6 +4,19 @@ date: 2020-03-07T16:22:03+01:00
draft: false
---
always **verify** the fingerprint
```bash
$ curl -sS https://dotya.ml/store/0x28bd2388.asc | gpg --show-key --fingerprint -
```
you can import the [key](/store/0x28bd2388.asc) into your keyring, like so
```bash
$ curl -sS https://dotya.ml/store/0x28bd2388.asc | gpg --import -
```
if you don't know what to do with the key afterwards, just refer to the GnuPG manual (really, rtfm - as in "read the fine manual") or read the GnuPG [faq](https://www.gnupg.org/faq/gnupg-faq.html)
```bash
-----BEGIN PGP PUBLIC KEY BLOCK-----

@ -5,43 +5,27 @@ draft: false
---
\-- wanderer
## e-mail
```
< a_mirre AT utb DOT cz >
echo a_mirre.utb.cz | sed 's/\./@/'
```
## gpg
#### fingerprint:
fingerprint:
```bash
E860 AB3C D007 8D30 E86C DA74 7B28 D8DC 28BD 2388
```
\
the corresponding pubkey: [0x28bd2388](/28bd2388)
```bash
$ curl -sS https://dotya.ml/store/0x28bd2388.asc | gpg --show-key --keyid-format 0xlong -
```
you can import the [key](/store/0x28bd2388.asc) to your keyring, like so
```bash
$ curl -sS https://dotya.ml/store/0x28bd2388.asc | gpg --import -
```
always **verify** that the fingerprint matches [the one on this page](#gpg)
```bash
$ gpg --fingerprint 0x28bd2388
```
plain key file: [0x28bd2388.asc](/store/0x28bd2388.asc)
communication using gpg is *preferable*
## Privacy policy
Since I don't like such practices myself, this site *does* **not** collect
Since I don't like such practices myself, this site *does not* collect
*any* kind of user/browser/device/user agent/network identifier,
which - for simplicity's sake is - ANY data.\
Period.\