TLS fallback Topic is solved

[darkarts]

Hello all.

I've just been prompted to upgrade to v32.5.1 and the Release Notes include this:

Restricted protocol fallback for TLS. Pale Moon no longer (by default) allows TLS 1.3 to fall back to earlier protocol versions during the initial handshake.

Before upgrading, please could someone explain the detail here? Specifically, if a server does not offer TLSv1.3 will the new PM refuse to connect? And if that's the case, what is the approved way of changing this behaviour from the default?

Thanks very much.

[Moonchild]

This only applies to protocol downgrades, not to the server not offering TLS 1.3 to begin with. if a server does not offer TLS 1.3, the TLS 1.2 will be negotiated right away, and nothing has changed in that respect.

Previously, Pale Moon would allow the protocol to be downgraded from TLS 1.3 to TLS 1.2 during initial handshake. Our recent upgrade of NSS already implemented a downgrade sentinel for that but unfortunately the resulting error message was not very transparent and we ran into specific middleware causing this to be triggered when there was a certificate error. The new configuration will present the user with the relevant cert error and no longer respond to the downgrade request by the middleware/server.

[darkarts]

Thanks for this extra detail which all makes perfect sense. Hoped it would be along these lines.

I'll proceed with the PM upgrade now with confidence.