5 ms·
Some excuses: - It's somewhat complicated for a site to implement correctly - It mainly protects users who have already connected to a site once fr
by peterwwillis 11y ago
Some excuses:
- It's somewhat complicated for a site to implement correctly
- It mainly protects users who have already connected to a site once
from a secure location and whose browsers support HSTS and other "fixes"
- Circumvented easily via phishing
- Does not prevent nation states from MITMing connection
- Can only host one site per IP, without a wild-card or UCC cert
(which not all clients support)
- Makes caching difficult to impossible
- Adds performance overhead
- Potential for new attacks on the TLS layer
(SSL Strip, STARTTLS Command Injection, BEAST, POODLE, RC4, CRIME,
TIME, BREACH, Truncation, FREAK, Logjam, Heartbleed, BERserk,
Root cert forgery, ChangeCipherSpec injection, Protocol downgrade,
Certificate errors, Renegotiation, Triple Handshake,
Virtual Host confusion, DoS)
- General confusion by users as to what makes a connection secure
- drdaeman 11y ago> Can only host one site per IP Not really. SNI is about to be called "ancient". Well, it's not supported by IE on Windows XP, but good riddance.
- mhurron 11y ago> Can only host one site per IP https://en.wikipedia.org/wiki/Server_Name_Indication https://en.wikipedia.org/wiki/Server_Name_Indication The rest of the excuses are basically 'it's not 100% perfect some of the time so why bother any of the time.'
- peterwwillis 11y agoSomeone asked why somebody might not use HTTPS and i'm just saying what their excuses are. This isn't even a list of reasons why people cannot support HTTPS, which includes public agency policies, legacy support requirements, funding limitations and lack of resources.
- mhurron 11y agoI'm not saying that you were putting them forward as valid, I'm saying that list should be ignored.
- wtetzner 11y agoEven without SNI, you can just add SAN names for all of your sites.
- richm44 11y ago> - It's somewhat complicated for a site to implement correctly This is true, but the same thing was said about running a site at all not long ago. > - It mainly protects users who have already connected to a site once from a secure location and whose browsers support HSTS and other "fixes" The point of using a valid CA is to allow the first connection be secure. It's certainly true that you can secure subsequent connections more than the initial one though. > - Circumvented easily via phishing Phishing is attacking something completely different and is not something SSL/TLS can or should protect you against. It's like expecting a seat belt to protect you from being run over. > - Does not prevent nation states from MITMing connection Actually it does if HPKP is used, though not on the initial connection. > - Can only host one site per IP, without a wild-card or UCC cert (which not all clients support) This is supported via the server name indication extension, and additionally by using multiple subject alternative names. The former is better though since it allows each site to have its own key. > - Makes caching difficult to impossible True, but that's a feature. Caching on the client is still of course entirely based on what the client chooses to do. > - Adds performance overhead Not much, see https://istlsfastyet.com/ https://istlsfastyet.com/ > - Potential for new attacks on the TLS layer (SSL Strip, STARTTLS Command Injection, BEAST, POODLE, RC4, CRIME, TIME, BREACH, Truncation, FREAK, Logjam, Heartbleed, BERserk, Root cert forgery, ChangeCipherSpec injection, Protocol downgrade, Certificate errors, Renegotiation, Triple Handshake, Virtual Host confusion, DoS) Note that there are protections again those, and saying "because it might have a problem" is basically just burying your head in the sand of the problem you already have. > - General confusion by users as to what makes a connection secure True, but not a good reason since you as a site owner can do most of the work for them (in combination with their browser).
- LeoNatan25 11y ago- It's complicated to create a door lock - It's somewhat complicated to install it on your door - Government can kick your door down - It takes time to turn the key to open the door - Friendly neighbors can't just hop in whenever they like - Confusion if door is locked or unlocked by looking at it Hmm, let's keep our doors without locks then?