News for hackers. Stuff that matters.
Re:S/MIME Version 4.0 Message Specification by yardstick on Wednesday May 01, 2019 @05:19AM (#19795620)
Is there a specific reason they have given for not supporting it? I’m a PGP fan myself but S/MIME is still useful.

I’ve found https://community.letsencrypt.org/t/s-mime-certificates/153 which seems to imply that it’s because they can’t validate emails securely enough in— although the comment wasn’t from LE staff. Maybe because email certs should last longer than a few months so it wouldn’t be as useful? I’m curious now!

Re:S/MIME Version 4.0 Message Specification by hannob on Wednesday May 01, 2019 @08:16AM (#19796361)
HTTPS is a mass feature and LE saw a need to make this available for free and with easier deployment and automation. And if implemented with state of the art technology it's a very robust and secure technology.

S/MIME is super niche. Even within the niche of email encryption it's a niche protocol. Also it suffers from loads of security problems and this RFC covers only a small fraction of them (and doesn't do a very good job due to backwards compatibility - it still has a "MUST support" the broken CBC modes).

Re:S/MIME Version 4.0 Message Specification by lol768 on Wednesday May 01, 2019 @08:23AM (#19796410)
>S/MIME is super niche. Even within the niche of email encryption it's a niche protocol

Compared to what, PGP? As far as I know, S/MIME has the most prevalent support out of the box in email software.

Re:S/MIME Version 4.0 Message Specification by hannob on Wednesday May 01, 2019 @09:25AM (#19796769)
It's been said that S/MIME has more implementations than users.

My guess would be there's more PGP users than S/MIME, but I could be wrong (and I doubt anyone has reliable numbers). In any case, everyone should agree that both are super niche.

Re:S/MIME Version 4.0 Message Specification by jcranmer on Wednesday May 01, 2019 @12:03PM (#19798419)
There's almost certainly more users of S/MIME than PGP. PGP keyservers can be well-analyzed for number of available keys, which is somewhere in the region of hundred thousands to millions, with the number of active users probably around a hundred thousand or so. S/MIME is known to be used by the DoD and CAC, which gives it several million users.
Re:S/MIME Version 4.0 Message Specification by jcranmer on Wednesday May 01, 2019 @09:03AM (#19796637)
To rough orders of magnitude, there's something on the order of a few million users of S/MIME, a few hundred thousand of PGP, and a few billion for DKIM, with DKIM happening for about half of email.
Re:S/MIME Version 4.0 Message Specification by lol768 on Wednesday May 01, 2019 @09:25AM (#19796770)
>and a few billion for DKIM, with DKIM happening for about half of email

I'm not sure I'd count DKIM in this category, since it's not user-facing.

Re:S/MIME Version 4.0 Message Specification by Chlorus on Wednesday May 01, 2019 @12:51PM (#19799015)
Also, does DKIM really provide the same sort of authentication that PGP / s/MIME would? All DKIMs verify is that the message was in fact authorized to emanate from that domain - PGP & S/MIME attempt to confirm that a particular identity belongs to a particular address.
Re:S/MIME Version 4.0 Message Specification by aaronmdjones on Wednesday May 01, 2019 @02:38PM (#19800254)
DKIM signs the message headers (including the From: header) and (a hash of) the message body. So you can validate that a message has not been tampered with, and is from the mailbox it says it is (assuming your mail provider rejects messages with an invalid signature, irrespective of e.g. DMARC).
Re:S/MIME Version 4.0 Message Specification by kevingrahl on Wednesday May 01, 2019 @06:21AM (#19795833)
Search the forum.

If I remember correctly it’s about validation and scalability. I don’t believe they ever gave a good reason not to.