Keyoxide PGP

[dngray]

Discussed in https://github.com/privacyguides/privacyguides.org/discussions/326

^{Originally posted by ignoramous November 16, 2021}

Keyoxide allows you to prove "ownership" of accounts on websites, domain names, IM, etc., regardless of your username.

That last part is important: You could, for example, be alice on Lobste.rs, but @alice24 on Twitter. And if your website is thatcoder.tld, how are people supposed to know that all that online property is yours?

The Keyoxide project is licensed under AGPL-3.0-or-later.

https://docs.keyoxide.org/getting-started/what-is-keyoxide/

[dngray]

I'm thinking this could be an interesting addition with #1686.

I think this does somewhat relate to privacy, particularly when using self hosted services, you'd need some sort of method to tie those credentials together. In the past we used Keybase, however the future of that is unlikely.

Most people opt to simply list credentials on their blog or website, but that doesn't have any cryptographic check.

[jonaharagon]

Most people opt to simply list credentials on their blog or website, but that doesn't have any cryptographic check.

To be honest, I'm not sure what value a cryptographic signature provides in this particular case.

[privacyguides-bot]

This issue has been mentioned on Privacy Guides. There might be relevant details there:

https://discuss.privacyguides.net/t/keyoxide-keybase-alternative/9564/9

[dngray]

Thread moved to https://discuss.privacyguides.net/t/keyoxide-keybase-alternative/9564/9