3 ms·
Actually you could implement it rather easily using a wildcard cert and a CA provider that provides unlimited signings (like DigiCert). The user goes to "https:
by MichaelGG 13y ago
Actually you could implement it rather easily using a wildcard cert and a CA provider that provides unlimited signings (like DigiCert). The user goes to "https://myuser.whatever.com" https://myuser.whatever.com", and you use SNI to select the private key.
It might be a pain to manage, and you'd need to get your wildcard cert resigned for each private key, but that's just logistics.
- MagicWishMonkey 13y agoIt would be a nightmare to manage, and you would have to explain to all 400k of your customers how connect to the smtp/imap endpoint for that particular user. Completely and totally unrealistic for an email provider. The support costs alone would bankrupt the company.
- MichaelGG 13y agoReally? Server: <username>.provider.com. Anyways, I'm just pointing out that it is possible to provide per-user certificates.
- jlgreco 13y agoThat would cause any particular user to leak what user on the site they were. In other words, if I connect with https to lavabit normally, anyone watching my connection knows I went to lavabit, but don't know what account I am associated with. If I have to hit a subdomain specific to my user, then they know.