Time to start disabling Legacy TLS on some of my own sites and it's as easy as clicking a button in my @Cloudflare dashboard!pic.twitter.com/xMxYkzFRpj
U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više
Just flicked the switch in my @Cloudflare dashboard and scanned again with @ssllabs, now up to an A+ again! https://www.ssllabs.com/ssltest/analyze.html?d=scotthelme.co.uk&s=2606%3a4700%3a3031%3a0%3a0%3a0%3a6818%3a61be&latest …pic.twitter.com/OHeaRdUXAv
Is there actually a risk to supporting legacy TLS versions? Downgrade prevention already exists so modern clients should be unaffected; setting a minimum version seems like it locks out legacy clients for no real reason.
Risk is how you define it. If you must continue to support 1.0 then you take the risk. The support of old clients may be required but you can mitigate the risks in other ways.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.