1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2025-02-25 15:50:05 +00:00

Compare commits

...

3 commits

Author SHA1 Message Date
Rohan Kumar
f33939444c
typo 2022-10-20 00:48:05 -07:00
Rohan Kumar
211dd4fb1f
New note: privacyguides email 2022-10-20 00:35:50 -07:00
Rohan Kumar
706d056fe4
Fix link margins 2022-10-20 00:19:04 -07:00
2 changed files with 20 additions and 0 deletions

View file

@ -296,6 +296,10 @@ 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 {

View file

@ -0,0 +1,16 @@
---
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).