show SSL/TLS version in the UI

RESOLVED DUPLICATE of bug 711816

Status

()

Firefox
Page Info Window
--
enhancement
RESOLVED DUPLICATE of bug 711816
5 years ago
4 years ago

People

(Reporter: marco_pal, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
Currently in the page info at the security tab it shows only if it's ciphered, the algorithm and the length of the key. I would suggest to add also the type of the connection, SSL3 or TLS 1.0. In the near future also TLS 1.1 will be supported so it will be even more useful. Adding it also in the popup under the lock like in chrome would be useful.

Updated

5 years ago
Hardware: x86 → All
Version: unspecified → Trunk

Comment 1

5 years ago
Other browsers show this information (e.g. AFAIK IE, Chromium). Please add this to Firefox.

Comment 2

5 years ago
Please take care of this issue.

Comment 3

5 years ago
This seems like a pretty significant hole in functionality.

Comment 4

5 years ago
This seems like a pretty significant hole in Firefox's implementation of encryption.

Comment 5

5 years ago
Indeed, and please add more important information as well: 
Currently it only says the name of the CA and cipher e.g. AES 256 bit. I suggest to add more details like AES 256 with CBC, SHA-1 message authentication and RSA 1024 bit key exchange, and also Perfect Forward Secrecy enabled or not, mixed content if applicable, insecure renegotiation if applicable, Strict Transport Security, verified by OCSP or not and lastly perhaps OCSP stapling.

Comment 6

5 years ago
Vote added here, this is something that needs to be fixed prompto.

Comment 7

5 years ago
Why is this still "UNCONFIRMED"?
Duplicate of this bug: 906159
It's a very reasonable request that is getting reported regularly, so I am confirming it as something to be addressed.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 711816
You need to log in before you can comment on or make changes to this bug.