Closed
Bug 1304924
Opened 8 years ago
Closed 8 years ago
Report key exchange group and server signature scheme in channel info
Categories
(NSS :: Libraries, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
3.28
People
(Reporter: mt, Assigned: mt)
References
Details
These are no longer part of the cipher suite, so users of TLS 1.3 have less information than they had before. We can make that more by adding these two fields. We might as well report these for other versions at the same time. The only question I have is whether we need to include string values for these as well.
Assignee | ||
Comment 1•8 years ago
|
||
Review at https://nss-dev.phacility.com/D37
Updated•8 years ago
|
Assignee: nobody → martin.thomson
Assignee | ||
Comment 3•8 years ago
|
||
Minor incremental part landed: https://hg.mozilla.org/projects/nss/rev/edecfb87990f
Comment 4•8 years ago
|
||
The primary value of this information is for logging or metrics gathering purposes, which means having a simple way to get a human readable string makes the API better.
Comment 5•8 years ago
|
||
I would propose that we have code->string translators rather than clutter up the structures
Assignee | ||
Comment 6•8 years ago
|
||
https://hg.mozilla.org/projects/nss/rev/adc3e36d504614bb50116165b1b6631a6ea2bb2f
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → 3.28
You need to log in
before you can comment on or make changes to this bug.
Description
•