2 ms·
> For email, the way you can demonstrate control is in being able to read and send emails originating from an address... but the point of S/MIME is to secure ag
by zokier 9y ago
> For email, the way you can demonstrate control is in being able to read and send emails originating from an address... but the point of S/MIME is to secure against other people who can also do that.
It's not exactly obvious how this situation is significantly different from the web side of things.
> So the only people who can access your email in the first place are the people who can access your email account, namely you, anyone you give access to, and administrators on your email server
What I think you are going after here is that shared/managed hosting style setups have only limited security, but that is equally true for web as it is for email.
- jcranmer 9y ago> It's not exactly obvious how this situation is significantly different from the web side of things. SSL protects against people who can casually monitor or intercept network connections. The attacker threat model is generally "coffee-shop wifi." In order to demonstrate control for Let's Encrypt, you need to ensure that some URL on your server delivers a specified byte content (the content given over a different channel). In essence, this kind of certificate says "I'm satisfied that the person who requested this certificate can arbitrarily modify the content on the website."