3 ms·
Except it is INSECURE: > However, insecure downgrades are called insecure for a reason. Client downgrades are triggered by a specific type of network failure, o
by jve 9y ago
Except it is INSECURE:
> However, insecure downgrades are called insecure for a reason. Client downgrades are triggered by a specific type of network failure, one that can be easily spoofed. From the client’s perspective, there’s no way to tell if this failure was caused by a faulty server or by an attacker who happens to be on the path of the connection network. This means that network attackers can inject fake network failures and trick a client into connecting to a server with SSLv3, even if both support a newer protocol. At this point, there were no severe publicly-known vulnerabilities in SSLv3, so this didn’t seem like a big problem. Then POODLE happened.
- wav-part 9y agoOfcourse CL should never downgrade to non-secure versions. SSLv3 is discouraged so CL wont try this. But 1.2 still ok.
- majewsky 9y agoThat's what they said about SSL 3 some time ago.
- wav-part 9y agoIf a client and server both dont upgrade to secure version and still use old now-broken version, there is nothing to be done. This thread is just now getting repeatitive.
- syncsynchalt 9y agoTLS 1.2 is insecure. Prove me wrong. So I guess we can't downgrade to it, and we should make 1.3 work without re-negotiation.