Your system information

• Steam client version (build number or date): 1751405894
• Distribution (e.g. Ubuntu): Pop/Cosmic OS
• Opted into Steam client beta?: [No]
• Have you checked for system updates?: [Yes]
• Steam Logs: n/a
• GPU: n/a

Please describe your issue in as much detail as possible:

crash.steampowered.com is using the older TLS1.2 instead of TLS1.3 which all other pages of steampowered.com seem to use.

Supporting TLS1.3 on the server - and configuring the client to use it might help

• speed up Steam startup time (by less round trips)
• future proof that setup
• Provide better security

There might also be a bug where multiple requests are made without reusing a connection?

Steps for reproducing this issue:

1. Run packet capture
2. Boot a fresh Steam client
3. Note sometimes it makes TLS1.2 Requests to crash.steampowered.com. In my one test it made 3 separate TLS1.2 Hellos in a row all to crash.

Sometimes I don't see it in the packet capture, but I was testing clients reconnecting in a row.

Analysis - https://www.hardenize.com/report/crash.steampowered.com/1751953188#www_tls
Good summary of security and performance benefits https://www.cloudflare.com/learning/ssl/why-use-tls-1.3/