New issue
Advanced search Search tips

Issue 642416 link

Starred by 8 users

Issue metadata

Status: Fixed
Owner:
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Launch-OWP
Launch-Accessibility: ----
Launch-Exp-Leadership: ----
Launch-Leadership: ----
Launch-Legal: ----
Launch-M-Approved: ----
Launch-M-Target: 55-Dev , 55-Beta , 55-Stable
Launch-Privacy: ----
Launch-Security: ----
Launch-Test: ----
Launch-UI: ----
Rollout-Type: ----


Show other hotlists

Hotlists containing this issue:
Hotlist-1
Hotlist-2


Sign in to add a comment

RSA-PSS for TLS

Project Member Reported by davidben@chromium.org, Aug 30 2016

Issue description

(See http://www.chromium.org/blink#launch-process for an overview)

Change description:
Enable RSA-PSS for TLS 1.2 in preparation for TLS 1.3.

Changes to API surface:
Chrome's ClientHello will include RSA-PSS values in the signature_algorithms extension and will accept RSA-PSS signatures for ServerKeyExchange.

Links:
Public standards discussion:
https://tools.ietf.org/html/draft-ietf-tls-tls13-15#section-4.2.2

Support in other browsers:
Internet Explorer:
Firefox: in progress as part of TLS 1.3 work
Safari:

(There's well-established consensus that TLS 1.3 will support RSA-PSS, so other browsers will likely support it once they get to 1.3.)

*Make sure to fill in any labels with a -?, including all OSes this change
affects. Feel free to leave other labels at the defaults.

 
Labels: -OWP-Standards-UnofficialSpec OWP-Standards-OfficialSpec
(I guess IETF drafts like this are probably closer to Working Draft than Editor's Draft. Not sure.)
Status: Fixed (was: Assigned)
LGTMs received on the thread and the code's in M55.  Marking as fixed.

Sign in to add a comment