logo

blog

My website can't be that messy, right? git clone https://hacktivis.me/git/blog.git
commit: 8c6eef0da2c321e5b5395e54af7059eebe7302fb
parent 8ead68f0db6587473d531037f8af0cafa916212e
Author: Haelwenn (lanodan) Monnier <contact@hacktivis.me>
Date:   Thu,  7 Mar 2019 02:54:33 +0100

articles/Pretty Bad Privacy: Add note on keybase

Diffstat:

Marticles/Pretty Bad Privacy.xhtml1+
Mfeed.atom2+-
2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/articles/Pretty Bad Privacy.xhtml b/articles/Pretty Bad Privacy.xhtml @@ -15,6 +15,7 @@ <p>There is no forward secrecy</p> <h2>OpenPGP in real life</h2> <p>Real Name policy and other stuff that should be optionnal in the Public Key Verification process (An ID card? Seriously?).</p> +<p>Quite a lot of people are trusting <a href="https://keybase.io/">keybase.io</a> to kinda fix a part of the Web-of-Trust, I do not like this one, it seems to basically be a social-media keyserver where you give it a lot of information for “verification”, and of couse the software is proprietary and it’s centralised. I think putting your fingerprint everywhere you can and putting you minimal public key on your blog is a much better way, and it can be automatised a bit (OPENPGPKEY DNS record, IndieWeb <code>rel="openpgp"</code>, …).</p> <h2>See also</h2> <ul> <li><a href="https://blog.patternsinthevoid.net/pretty-bad-protocolpeople.html">Pretty Bad {Protocol,People}</a></li> diff --git a/feed.atom b/feed.atom @@ -14,7 +14,7 @@ <link rel="alternate" type="text/html" href="/articles/Pretty%20Bad%20Privacy"/> <id>https://hacktivis.me/articles/Pretty%20Bad%20Privacy</id> <published>2019-03-07T01:00:04Z</published> - <updated>2019-03-07T01:14:11Z</updated> + <updated>2019-03-07T01:54:33Z</updated> <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <!--#include file="/articles/Pretty Bad Privacy.xhtml"--> </div></content>