3 ms·

The reason is that encrypted websites are a bit harder to hack and inject malicious code into. In particular MITM attacks are much harder to pull off - such as

The reason is that encrypted websites are a bit harder to hack and inject malicious code into. In particular MITM attacks are much harder to pull off - such as those by airport/mall free wifis. Using the latest version of TLS makes us safe from hacking.

throw0101a 6y ago
Using TLS in general, regardless of version, makes us safe(r) from hacking as it prevent injection. What how does disabling 1.0 specifically do?
- abdullahkhalids 6y ago
  Good question. Because it is an old protocol, vulnerabilities have been discovered in it over time [1]. Got to keep things updated! [1] https://www.acunetix.com/blog/articles/tls-vulnerabilities-attacks-final-part/ https://www.acunetix.com/blog/articles/tls-vulnerabilities-a...
- tialaramex 6y ago
  The RFC that tells people who weren't paying attention to stop using TLS 1.0 and TLS 1.1 will explain this, here's the current draft of that document: https://tools.ietf.org/html/draft-ietf-tls-oldversions-deprecate-06 https://tools.ietf.org/html/draft-ietf-tls-oldversions-depre... Examples of things mentioned: SHA-1 sucks, this hash is too short by modern standards and we know it's flawed even though collision (the exciting headline making flaw) isn't especially relevant to TLS. But in TLS 1.0 SHA-1 is either the only hash permitted (in some places) or it's the best option left (MD5 is allowed but that's worse). TLS 1.0 doesn't explain the necessity of guarding against padding oracles or how to do so. Now, of course it also doesn't ban you from guarding against them. But wait, if you're going back to upgrade your software to mitigate padding oracle attacks on TLS 1.0 why aren't you just upgrading to TLS 1.2 ? The stacks we're confident have effective mitigations all... offer TLS 1.2 anyway. TLS 1.0 specifically requires you can do 3DES (in the terminology it's "Mandatory to implement" or MTI). But 3DES sucks, it's very slow and not as secure as a modern cipher. So you would never want to actually use 3DES, but it's mandatory in TLS 1.0 so now you're implementing a cipher that's very bad and you never want to use, just so you can support an obsolete protocol version. Or we can deprecate that protocol version and tell people to just use a newer protocol.

throw0101a 6y ago

Using TLS in general, regardless of version, makes us safe(r) from hacking as it prevent injection. What how does disabling 1.0 specifically do?

abdullahkhalids 6y ago
Good question. Because it is an old protocol, vulnerabilities have been discovered in it over time [1]. Got to keep things updated! [1] https://www.acunetix.com/blog/articles/tls-vulnerabilities-attacks-final-part/ https://www.acunetix.com/blog/articles/tls-vulnerabilities-a...
tialaramex 6y ago
The RFC that tells people who weren't paying attention to stop using TLS 1.0 and TLS 1.1 will explain this, here's the current draft of that document: https://tools.ietf.org/html/draft-ietf-tls-oldversions-deprecate-06 https://tools.ietf.org/html/draft-ietf-tls-oldversions-depre... Examples of things mentioned: SHA-1 sucks, this hash is too short by modern standards and we know it's flawed even though collision (the exciting headline making flaw) isn't especially relevant to TLS. But in TLS 1.0 SHA-1 is either the only hash permitted (in some places) or it's the best option left (MD5 is allowed but that's worse). TLS 1.0 doesn't explain the necessity of guarding against padding oracles or how to do so. Now, of course it also doesn't ban you from guarding against them. But wait, if you're going back to upgrade your software to mitigate padding oracle attacks on TLS 1.0 why aren't you just upgrading to TLS 1.2 ? The stacks we're confident have effective mitigations all... offer TLS 1.2 anyway. TLS 1.0 specifically requires you can do 3DES (in the terminology it's "Mandatory to implement" or MTI). But 3DES sucks, it's very slow and not as secure as a modern cipher. So you would never want to actually use 3DES, but it's mandatory in TLS 1.0 so now you're implementing a cipher that's very bad and you never want to use, just so you can support an obsolete protocol version. Or we can deprecate that protocol version and tell people to just use a newer protocol.