Closed
Bug 1513839
Opened 5 years ago
Closed 5 years ago
Collect SSL_TIME_UNTIL_HANDSHAKE_FINISHED by key exchange group
Categories
(Core :: Security: PSM, defect)
Core
Security: PSM
Tracking
()
RESOLVED
FIXED
mozilla66
Tracking | Status | |
---|---|---|
firefox66 | --- | fixed |
People
(Reporter: franziskus, Assigned: franziskus)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Telemetry for handshake times should be collected depending on the key exchange group.
Attachment #9031063 -
Flags: review?(chutten)
Assignee | ||
Comment 1•5 years ago
|
||
This collects SSL_TIME_UNTIL_HANDSHAKE_FINISHED dependent on the key group used. This is nice to have in general and especially for the ecdhe-sidh thing.
Comment 2•5 years ago
|
||
Comment on attachment 9031063 [details] data-review.txt Preliminary note: The answer to question 5 should contain the name, description, relevant bug#, and data collection category of each new or changed collection under review. So we're looking for something like SSL_TIME_UNTIL_HANDSHAKE_FINISHED_KEYED_BY_KA ms of SSL wait time for full handshake including TCP and proxy tunneling, keyed by the key exchange algorithm used bug 1340021 Category 1, Technical Please include this information (just echo the above if correct and helpful) in a follow-up comment in this bug. DATA COLLECTION REVIEW RESPONSE: Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate? Yes. This collection is Telemetry so it is documented in its definition file (Histograms.json), the Probe Dictionary, and on telemetry.mozilla.org's Measurement Dashboards. Is there a control mechanism that allows the user to turn the data collection on and off? Yes. This collection is Telemetry so can be controlled by Firefox's Preferences. If the request is for permanent data collection, is there someone who will monitor the data over time? Yes. Franziskus will monitor it over time. Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under? Category 1, Technical. Is the data collection request for default-on or default-off? Default on, all channels. Does the instrumentation include the addition of any new identifiers? Only categorical ones: the names of key exchange algorithm groups used. Is the data collection covered by the existing Firefox privacy notice? Yes. Does there need to be a check-in in the future to determine whether to renew the data? No. This collection is permanent. --- Result: datareview+, pending a full list of proposed measurements (Question 5 from the review request)
Attachment #9031063 -
Flags: review?(chutten) → review+
Assignee | ||
Comment 3•5 years ago
|
||
Yep, the full answer for Q5 is: SSL_TIME_UNTIL_HANDSHAKE_FINISHED_KEYED_BY_KA ms of SSL wait time for full handshake including TCP and proxy tunneling, keyed by the key exchange algorithm used bug 1340021 Category 1, Technical
Pushed by franziskuskiefer@gmail.com: https://hg.mozilla.org/integration/autoland/rev/4e040d8be2e4 Make SSL_TIME_UNTIL_HANDSHAKE_FINISHED keyed by kea group r=keeler,jcj
Comment 5•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/4e040d8be2e4
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox66:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
Updated•5 years ago
|
Assignee: nobody → franziskuskiefer
You need to log in
before you can comment on or make changes to this bug.
Description
•