logo

blog

My little blog can’t be this cute!
commit: 962b24de307f8786a30b2bd18aba4da88b8c4d1b
parent: d654fa3729cfdcdb4d11964307b1842fbba33362
Author: Haelwenn (lanodan) Monnier <contact@hacktivis.me>
Date:   Wed,  9 Jan 2019 04:27:46 +0100

articles/I’m removing defaults to eternal cryptographic signatures.xhtml: update Fediverse note

Diffstat:

Marticles/I’m removing defaults to eternal cryptographic signatures.xhtml2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/articles/I’m removing defaults to eternal cryptographic signatures.xhtml b/articles/I’m removing defaults to eternal cryptographic signatures.xhtml @@ -4,7 +4,7 @@ <ul> <li>git: Remove commit.gpgSign (user-wide it’s <code>~/.gitconfig</code>, repo-wide it’s <code>.git/config</code> or <code>config</code> on bare repos). To strip existing commits run <code>git filter-branch</code> on the repositories.</li> <li>Email: Disable OpenPGP Signatures in your client if you did (also avoid Protonmail), make sure DKIM is non-existent, you may have to self-host your email</li> - <li>Fediverse: Move away from Mastodon and use something like Pleroma, which doesn’t have JSON-LD Signatures.</li> + <li>Fediverse: With Mastodon 2.7.0 (upcoming release as of 2019-01-09) you should use non-public statuses by default (See <a href="https://github.com/tootsuite/mastodon/pull/9659">Pull Request #9659</a>). Otherwise you can use Pleroma which doesn’t have JSON-LD Signatures.</li> <li>XMPP: Not sure, I’ll check later on how OTRv3/v4 and OMEMO works</li> </ul> <h2>Why?</h2>