Description of problem: Bad Your client is using TLS 1.0, which is very old, possibly susceptible to the BEAST attack, and doesn't have the best cipher suites available on it. Additions like AES-GCM, and SHA256 to replace MD5-SHA-1 are unavailable to a TLS 1.0 client as well as many more modern cipher suites. protonmail does not support firefox-24.6 Any hope to have a backport of firefox-30.0? Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
Not a packaging problem, first of all. Second of all, a newer FF won't matter, because it uses NSS for its SSL/TLS stuff, and we already have the newest NSS (and we will have a newer FF when the next stable ESR version comes out). TLS negotiates the best TLS version and ciphers that both the client and server support, as I understand it, so that site is only telling you that your browser supports some older/weaker ones, which is required sometimes unfortunately. As time goes by, you'll probably see some of these get dropped. According to the normal schedule, 31 should be the next stable version, so please be patient.
Status: NEW => RESOLVEDResolution: (none) => INVALID
Also, about:config lets you control the minimum and maximum TLS versions supported, but it apparently doesn't support newer than 1.0 yet, and it also allows you to disable individual ciphers.
Maybe it is a bug at protonmail.ch? I have reported the problem to protonmail.