Compare commits

..

No commits in common. "87092964745d10d84b523c5da428c9854c45f75c" and "2b72f9d247975b990d8d1bde45ec7e46531775b9" have entirely different histories.

1 changed files with 0 additions and 15 deletions

View File

@ -40,21 +40,6 @@ control what people do with the signatures from this repository).
* `me/me.asc` is just my key and place where I try to keep all signatures it * `me/me.asc` is just my key and place where I try to keep all signatures it
has received. Symlinks are legacy reasons and other me's are also me. has received. Symlinks are legacy reasons and other me's are also me.
## Places to check for keys
* GitHub, Gitea and GitLab expose user public keys when you append a `.gpg`
after their profile page (`.keys` for SSH).
* [The Internet Archive's Waybackmachine](https://web.archive.org/) is always
a good place too especially when using together with official websites.
* Some people have similar projects or webpages for this purpose
* [Artemis' verify page](https://artemislena.eu/services/verify.html)
* [Jonah Aragon's Third Party Public Keys page](https://jonaharagon.com/verify/)
## Mirrors
* main: [git.blesmrt.net/Mikaela/pgp-alt-wot](https://gitea.blesmrt.net/mikaela/pgp-alt-wot/)
* [git.piraattipuolue.fi/Mikaela/pgp-alt-wot](https://git.piraattipuolue.fi/mikaela/pgp-alt-wot)
## See also ## See also
* [Qubes OS: On Digital Signatures and Key Verification](https://www.qubes-os.org/security/verifying-signatures/) * [Qubes OS: On Digital Signatures and Key Verification](https://www.qubes-os.org/security/verifying-signatures/)