canmove, Confirmed users
1,537
edits
Privacy/Features/Handshake checkpoint API: Difference between revisions
Jump to navigation
Jump to search
Privacy/Features/Handshake checkpoint API (view source)
Revision as of 17:29, 2 September 2011
, 2 September 2011no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{FeatureStatus | {{FeatureStatus | ||
|Feature name=Create API for add-ons and components that provides check-point between TLS/SSL handshake and HTTP request | |Feature name=Create API for add-ons and components that provides check-point between TLS/SSL handshake and HTTP request | ||
|Feature stage= | |Feature stage=Feature Inbox | ||
|Feature status=In progress | |||
|Feature health=OK | |Feature health=OK | ||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
|Feature product manager=Sid Stamm | |Feature product manager=Sid Stamm | ||
|Feature lead engineer=Honza Bombas | |||
|Feature privacy lead=Sid Stamm | |||
|Feature additional members=Brian Smith | |||
}} | }} | ||
{{FeaturePageBody | {{FeaturePageBody | ||
|Feature overview=Create API for add-ons and components that provides check-point between TLS/SSL handshake and HTTP request, allowing add-ons greater scrutiny of secure connections before they are used. | |Feature overview=Create API for add-ons and components that provides check-point between TLS/SSL handshake and HTTP request, allowing add-ons greater scrutiny of secure connections before they are used. This feature also would expose the controls to add-ons so they can implement an alternate certificate-validation path that's not dependent on our existing PKI and root certificate program. | ||
|Feature users and use cases=Convergence: Moxie would really like an API like this for simplifying the Convergence (http://convergence.io) add-on implementation. He had to "jump through some pretty prolific hoops in order to replace the browser's default certificate validation with my own." | |||
|Feature dependencies=* {{bug|644640}}: Implement extension point for extensions to influence trust decisions in PSM | |||
|Feature non-goals=* This will not ''replace'' our existing PKI/CA program | |||
* This is not affecting stuff outside the TLS layer of HTTPS connections. | |||
* This is not adding additional UI over the DV/EV SSL indicators. | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||
|Feature priority=P1 | |Feature priority=P1 | ||
|Feature theme=Secure Network Connections | |||
|Feature roadmap=Privacy | |Feature roadmap=Privacy | ||
|Feature secondary roadmap=Security | |Feature secondary roadmap=Security | ||
|Feature list=Platform | |Feature list=Platform | ||
|Feature engineering team=Networking | |||
}} | }} | ||
{{FeatureTeamStatus}} | {{FeatureTeamStatus}} | ||