fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2025-02-25 15:50:05 +00:00
Code Issues Projects Releases Wiki Activity

Compare commits

..

No commits in common. "f33939444cc3354be0791ae092d3b6cabf50037f" and "04600cb92be153bbfb0d8b2e9fc1febd0d4ea559" have entirely different histories.
f33939444c ... 04600cb92b

2 changed files with 0 additions and 20 deletions

4
assets/css/main.css
View file

@ -296,10 +296,6 @@ html {
margin-left: -.25em; margin-left: -.25em;
} }
h1 + ul > li > a {
margin-left: 0;
}
/* Increase tap-target size of title links. */ /* Increase tap-target size of title links. */
h2 > a { h2 > a {

16
content/notes/re-privacyguides-email-security.md
View file

@ -1,16 +0,0 @@
---
title: "Re: Privacy Guides email security"
date: 2022-10-20T00:35:50-07:00
replyURI: "https://www.privacyguides.org/basics/email-security/"
replyTitle: "Email Security"
replyType: "TechArticle"
replyAuthor: "Privacy Guides"
replyAuthorType: "Organization"
replyAuthorURI: "https://www.privacyguides.org/"
---
Key management guides should also cover key distribution.
Secure distribution happens over at least two bands with two different sources of trust. Having my own domain name lets me combine DANE (trust the DNS trust anchors) and Web Key Directory (trust the WebPKI and CA system). Clients can fetch keys both ways and ensure they match. Prospective senders may also request public keys over modern encrypted messengers.
This guide covers the client side. Users need providers and name servers to adopt email security standards (DKIM, SPF, DMARC, ARC, DANE, MTA-STS).