SecurityEngineering/Public Key Pinning/ReleaseEngineering: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
# Push a hotfix to disable the pinning pref. In case pinning breaks AMO, this will not be possible. | # Push a hotfix to disable the pinning pref. In case pinning breaks AMO, this will not be possible. | ||
# Push a chemspill. | # Push a chemspill. | ||
== How long do updates take? == | |||
* Hotfix: almost all users in 2 days | |||
* Chemspill: unknown | |||
* Fennec (Google play): Majority users in 2 days | |||
== What about other platforms besides desktop? == | == What about other platforms besides desktop? == | ||
Revision as of 23:30, 22 May 2014
Whom to contact in case of emergency
seceng@mozilla.org
Implementation status
Pinning is enabled by default in Nightly 32.
What critical Mozilla properties are we planning to pin?
- AMO
How to rollback pinning for Firefox
Pinning is controlled by a preference, security.cert_pinning.enforcement_level. To disable pinning, set this pref to 0. In case of emergency, we can
- Push a hotfix to disable the pinning pref. In case pinning breaks AMO, this will not be possible.
- Push a chemspill.
How long do updates take?
- Hotfix: almost all users in 2 days
- Chemspill: unknown
- Fennec (Google play): Majority users in 2 days