News for hackers. Stuff that matters.
Re:TLS 1.0, 1.1 officially deprecated by lazyweb on Tuesday March 23, 2021 @05:20PM (#26560559)
On a related note, thinking of setting my personal site to TLS 1.3 only. It's still allowing for TLS 1.2 with strong chipers, but except for shutting out anyone using older smartphones or operating systems, what's the harm? Could I fall out of favour with Google & co due to compliance reasons?

Thinking of SSL scan tools like this one [1] which gave me an "F" for how I configure my SSH servers, only allowing for very modern ciphers and kex without backward compatibility.

[1] https://github.com/rbsec/sslscan

Re:TLS 1.0, 1.1 officially deprecated by shaicoleman on Tuesday March 23, 2021 @05:59PM (#26560889)
> thinking of setting my personal site to TLS 1.3 only

I wouldn't recommend doing that. You might end up blocking users using a proxy (e.g. for privacy reasons), people on corporate networks, people in China [1], and many other non-traditional browsers (e.g. browsers for the blind, game consoles), users on older versions of curl/wget/lynx, older mobile phones, etc.

TLS 1.2 when correctly configured is still perfectly fine. And users with modern browsers will connect with TLS 1.3. TLS 1.3 also has protections against downgrade attacks.

Another good scanner for SSL is Qualys SSL Server Test [2]. Getting an A+ score there doesn't require disabling TLS 1.2

For secure configuration, you can use Mozilla SSL Configuration Generator [3]

1. https://www.zdnet.com/article/china-is-now-blocking-all-encr...

2. https://www.ssllabs.com/ssltest/

3. https://ssl-config.mozilla.org/

Re:TLS 1.0, 1.1 officially deprecated by staticassertion on Tuesday March 23, 2021 @06:06PM (#26560956)
> perfectly secure.

I think you're trying to use 'perfectly secure' here the way one might say 'perfectly fine', which changes the reading a lot from a first pass.

That said, I agree, there is a subset of TLS 1.2 that is suitable.

Re:TLS 1.0, 1.1 officially deprecated by shaicoleman on Tuesday March 23, 2021 @06:08PM (#26560967)
Agreed, updated that
Re:TLS 1.0, 1.1 officially deprecated by laurent92 on Tuesday March 23, 2021 @08:04PM (#26561939)
Honest question but no deep answer requested, why do we have to choose the ciphers?

Not only it adds 2^(number of ciphers) ways to misconfigure the server with a gaping security leak, but names are obscure and strings are NEVER the same between nginx and the SSLlabs website which advises what is correct, plus who knows whether SSLLabs is a trustworthy website. Also, 6 months later the ciphers might not be up to date. Why do I have to even choose ciphers? Why isn’t this TLS 1.2.1, then 1.2.2, and so on?

It’s like going to Amazon, choosing n resistors by guessing their value, going to m people asking them if it’s 12 ohms, most of them having no clue what they are talking about, and using it for an airport security device that can put people in jail.

Re:TLS 1.0, 1.1 officially deprecated by lmm on Wednesday March 24, 2021 @02:08AM (#26564082)
Back when TLS (or rather SSL) was originally designed, people were very aware of cipher vulnerabilities - there was a lot of academic attention on them, there was a recent history of ciphers being broken, and US export restrictions forced international programs to support a known-weak cipher (DES). People were much less aware of protocol vulnerabilities - security protocols were nowhere near as widespread and weren't really the subject of academic study. So at the time people expected to need to upgrade ciphers relatively often but upgrade the protocol rarely, if at all, and designing the majority of the protocol to be fixed with the ciphers as a pluggable, swappable part made sense.
Re:TLS 1.0, 1.1 officially deprecated by shaicoleman on Tuesday March 23, 2021 @08:50PM (#26562224)
Different ciphers have different tradeoffs (security/vulnerablities/performance/hardware acceleration/compatibility/newness/etc.).

Indeed, more choice means more ways to mess things up, more complexity, more bugs and more vulnerabilities.

That's why TLS 1.3 reduces the cipher suite choice to 5 ciphers, down from 37 from TLS 1.2 (in previous versions there were 319 in total) [1]

1. https://owasp.org/www-chapter-london/assets/slides/OWASPLond...

Re:TLS 1.0, 1.1 officially deprecated by tialaramex on Wednesday March 24, 2021 @02:45AM (#26564224)
In some ways this is OpenSSL's fault. So the first answer is, your tooling decided to make you answer this question instead of picking its own answer based on the expertise of the authors. A 1990s TV could have a UI where you need to explicitly configure which pins of a SCART connector have what signals on them, but that would be crazy so the TV just worked with the usual SCART pins as defined and if your pin-out is weird it won't work. The TLS 1.2 standard itself doesn't say "Make the user or administrator pick from this huge list". You can make cipher suite decisions like this in SSH too, but you probably mostly don't because the defaults are fine.

Now, the technical answer as to why there's something to pick from at all goes like this:

TLS is a negotiated protocol. Some HN regulars are convinced negotiation is a bad idea, and indeed they will point to TLS as an example. But the idea is that with a vast population of servers and clients on the Internet it isn't actually practical to hold a flag day (replacing all software on clients and servers immediately) to upgrade TLS. Different clients and servers may have different priorities, so we'd like them to be able to agree each time on something they're both content with. For example on your general purpose laptop there is hardware AES, so AES ciphers are fast and secure, but some cheap devices don't have that, so for them AES is annoyingly slow/ power hungry. As a result they'd prefer ChaCha20 if possible.

How did the list get so long? There's a point around the turn of the century when countries realise oh, this Internet thing is important, and you get a rash of "cryptographic nationalism" where a government that likes to think of itself as important notices the US government made things like DES and it decides it can do that too, resulting in vanity ciphers which are less analysed, less popular, and basically have no reason to exist. TLS 1.2 doesn't explicitly discourage you from supporting these, and OpenSSL is a stamp collector's library, if a cipher exists and you can implement it, why not? So you get this unwieldy list nobody actually needs, and then apps present it to non-experts like "Pick from this list or be doomed".

You can get advice on how to configure web servers from Mozilla, https://ssl-config.mozilla.org/

For other types of TLS server you should seek advice from experts in the appropriate protocol.

In TLS 1.3 they learned from this mistake and discourage cryptographic nationalism, you have a literal handful of choices, all of them are currently believed to be safe, some are likely poor (slow, power hungry) choices on simple hardware, some would be weak if large quantum computers were actually cheap and readily available, rather than horribly expensive and non-existent. So "I don't care, whatever" is thus safe in TLS 1.3 although presumably OpenSSL still expects you to actually pick anyway.

Re:TLS 1.0, 1.1 officially deprecated by laurent92 on Wednesday March 24, 2021 @04:48AM (#26564882)
That’s the answer I wanted but didn’t dare to ask. Thank you!
Re:TLS 1.0, 1.1 officially deprecated by lazyweb on Wednesday March 24, 2021 @04:24AM (#26564740)
Hm, thanks for your reply. I'm already obsessing over the SSL test in your 2nd link, having set everything to achieve an A+, including DNS CAA and all the recommended technical mitigations. But your point regarding accessibility is an important one, I think. Even though my page doesn't generate a lot of traffic that's something I wouldn't want to shut out.
Re:TLS 1.0, 1.1 officially deprecated by throwaways885 on Wednesday March 24, 2021 @12:03AM (#26563477)
> people on corporate networks, people in China

By supporting older protocols on sites, we're enabling this kind of abuse to run rampant. Maybe it's best to just cut them off.

Re:TLS 1.0, 1.1 officially deprecated by shaicoleman on Wednesday March 24, 2021 @04:19AM (#26564704)
I believe that ends up with hurting more the people who are already affected by these policies.

In the end they just get replaced with something worse.

e.g. I think that Google offering censored search in China is a lesser evil than Baidu, which is not only censored, but likely also tracks and reports all your searches to the government

Re:TLS 1.0, 1.1 officially deprecated by lenish on Tuesday March 23, 2021 @05:58PM (#26560886)
RFC7457[1] and Wikipedia[2] offer an overview of many of the attacks on older versions of TLS. Some of those attacks have been mitigated to varying extents in implementations of the affected versions. TLSv1.3 is meant to resolve completely as many of these issues as possible.

When using older protocol versions, it can be complicated to validate that the TLS implementation you are using has the necessary mitigations in place. It can be complicated to correctly configure TLS to minimize the effects of known attacks. Doing that properly requires a fair amount of research, threat modelling, and risk assessment both for yourself and on behalf of anyone accessing your website or service.

IME, TLSv1.2 is still a big chunk of legitimate web traffic. It has been steadily dropping since standardization, and TLSv1.3 is the majority by a wide margin from what I can see. I wouldn't be surprised to see some websites and services still needing to support it for a couple years more, at least, depending on their target audience.

[1] https://tools.ietf.org/html/rfc7457

[2] https://en.wikipedia.org/wiki/Transport_Layer_Security#Attac...

Re:TLS 1.0, 1.1 officially deprecated by GoblinSlayer on Wednesday March 24, 2021 @07:41AM (#26565883)
Most of those attacks require ssl2 or cooperation from client.
Re:TLS 1.0, 1.1 officially deprecated by walrus01 on Tuesday March 23, 2021 @07:31PM (#26561699)
When I looked into this over 3 years ago, 99%+ of user agents were capable of TLS1.2. I disabled everything below TLS1.2 on all public facing httpd with no negative consequences. I would not recommend going to TLS1.3-only for quite some time yet due to people who are very slow updating their clients.
Re:TLS 1.0, 1.1 officially deprecated by gnyman on Wednesday March 24, 2021 @04:11AM (#26564660)
I recently did the opposite and re-enabled 1.0 and 1.1

Wrote some thoughts on why here https://blog.nyman.re/2021/02/07/usability-security.html but in short, it's several magnitudes more likely someone will want to check out my blog using a old device vs someone trying to exploit vulnerabilities in the old protocols.

Google.com still allows TLS1.0/1.1 https://www.ssllabs.com/ssltest/analyze.html?d=google.com&s=...

Re:TLS 1.0, 1.1 officially deprecated by lazyweb on Wednesday March 24, 2021 @04:17AM (#26564690)
Yeah no, that's where I'd draw the line. I have one nginx instance serving my blog and various resources via proxypass (nextcloud, grafana, icinga, kibana etc.). For the sake of keeping things maintainable, there's one wildcard cert for my domain and one global SSL configuration. I'd rather shut out people with Windows XP than enabling < TLS 1.2 globally.
Re:TLS 1.0, 1.1 officially deprecated by gnyman on Wednesday March 24, 2021 @02:43PM (#26571340)
Everyone has different priorities of course. But note that as long as you use a modern client TLS_FALLBACK_SCSV will ensure you won't be at risk of downgrade attacks or similar. Without that I also don't think I would run it.
Re:TLS 1.0, 1.1 officially deprecated by cmeacham98 on Tuesday March 23, 2021 @10:31PM (#26562892)
I personally did it recently and it was a breath of fresh air not having to worry about cipher suites or DH params or other garbage as TLS1.3's defaults are secure.

Although note that I did see a drop of ~2%-3% in traffic after that. I don't directly make any money of these websites (just my personal blog and similar) and most of my viewers are likely to be technical (i.e. not using IE which doesn't support 1.3), so I decided the sacrifice was worth it for another small reduction in needed sysadmin thought+work.

Re:TLS 1.0, 1.1 officially deprecated by AdrianB1 on Tuesday March 23, 2021 @06:09PM (#26560984)
Based on the numbers in the other comments, you risk losing ~ 10% of the readers. It is up to you to decide if you want to do it or not.
Re:TLS 1.0, 1.1 officially deprecated by rodgerd on Tuesday March 23, 2021 @08:33PM (#26562112)
Pretty much anyone on the wrong end of middleboxes. A lot of "security" folks and vendors are addicted to MITM of secure network connections. You'll likely find anyone working behind a corporate firewall will be unable to access your site, since most of these folks are determined to break/block 1.3.
Re:TLS 1.0, 1.1 officially deprecated by userbinator on Tuesday March 23, 2021 @08:37PM (#26562140)
I MITM my own connections too, to do content filtering/adblocking/etc., although in my case the proxy upgrades lower versions to TLS 1.2.
Re:TLS 1.0, 1.1 officially deprecated by oaiey on Tuesday March 23, 2021 @06:34PM (#26561206)
Is TLS 1.3 is not rolled out to Windows 10? It rolled out to insider builds during last autumn but did it arrive already to the masses