Confirmed users
717
edits
Security/Features/CA pinning functionality: Difference between revisions
Jump to navigation
Jump to search
Security/Features/CA pinning functionality (view source)
Revision as of 22:14, 29 March 2012
, 29 March 2012no edit summary
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
{{FeatureTeam | {{FeatureTeam | ||
|Feature product manager=Lucas Adamski | |Feature product manager=Lucas Adamski | ||
|Feature feature manager=Camilo Viecco | |||
|Feature lead engineer=Camilo Viecco | |||
|Feature security lead=Curtis Koenig | |Feature security lead=Curtis Koenig | ||
|Feature privacy lead=Sid Stamm | |Feature privacy lead=Sid Stamm | ||
| Line 18: | Line 20: | ||
* Enabling pinning without also requiring HTTPS (see section 6.5 of spec) | * Enabling pinning without also requiring HTTPS (see section 6.5 of spec) | ||
|Feature functional spec=See https://tools.ietf.org/html/draft-evans-palmer-key-pinning . | |Feature functional spec=See https://tools.ietf.org/html/draft-evans-palmer-key-pinning . | ||
|Feature ux design=The draft recommends that users have ways of querying which domains are pinned. We need to consider whether we think this is necessary and, if so, how to do it. (Perhaps integrated with the history view?) | |Feature ux design=The draft recommends that users have ways of querying which domains are pinned. We need to consider whether we think this is necessary and, if so, how to do it. (Perhaps integrated with the history view?) | ||