mirror of
https://git.sr.ht/~seirdy/seirdy.one
synced 2024-12-28 11:02:10 +00:00
New note: privacyguides email
This commit is contained in:
parent
706d056fe4
commit
211dd4fb1f
1 changed files with 16 additions and 0 deletions
16
content/notes/re-privacyguides-email-security.md
Normal file
16
content/notes/re-privacyguides-email-security.md
Normal 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 combining 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).
|
||||
|
Loading…
Reference in a new issue