From f73935944ca78418c4912413e0dc140bc57cf4d7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Wxcaf=C3=A9=20=28Cl=C3=A9ment=20Hertling=29?= Date: Sat, 24 Dec 2016 00:46:33 +0100 Subject: [PATCH] email security --- content/email-security.md | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 content/email-security.md diff --git a/content/email-security.md b/content/email-security.md new file mode 100644 index 0000000..46e2347 --- /dev/null +++ b/content/email-security.md @@ -0,0 +1,29 @@ +Title: Email Security +Date: 2016-12-24T00:24+01:00 +Author: Wxcafé +Category: +Slug: email-security + +So, nowadays, everyone knows emails are **not** secure. If you didn't know that, +you should. Emails are to be treated like postcards : everyone between you and +the person you're talking to can read them. Don't write military secrets in +them. Back in the good old days, when the protocols they rely on were devised, +the people creating them didn't really need to secure them (and they didn't have +computers powerful enough to do encryption. Emails are **old**. Like, really +old. Like older than I am. By decades.) + +There are, of course, a few methods to "secure" email. I'm ready to bet at this +point over 75% of the people reading this are at least thinking very hard "PGP". +Some might be thinking "S/MIME". Maybe a few of you who didn't think I was +talking about encryption by the user are thinking about STARTTLS in SMTP, or +SPF/DKIM/DMARC. + +If this previous paragraph confused you, at least a bit, there's a very good +summary about these things over in the latest issue of *the IP Journal*, +[here](http://ipj.dreamhosters.com/wp-content/uploads/issues/2016/ipj19-3.pdf) +(pdf). I also am going to start mirroring the issues of that journal over on +[https://wxcafe.net/pub/IPJ/](https://wxcafe.net/pub/IPJ/). I encourage you to +subscribe to the paper version of the IP Journal, it's **free** and the content +is generally very good and informative. + +That was all, see ya