Confirmed users
502
edits
B2G/Architecture/System Security: Difference between revisions
B2G/Architecture/System Security (view source)
Revision as of 00:13, 2 November 2012
, 2 November 2012no edit summary
Gdestuynder (talk | contribs) (→Proposed Implementation: additional information for split encryption/unlock codes) |
Gdestuynder (talk | contribs) mNo edit summary |
||
| Line 266: | Line 266: | ||
|Implementation Status||Priority||Proposed ETA | |Implementation Status||Priority||Proposed ETA | ||
|- | |- | ||
|N/A|| | |N/A||Medium||Unknown | ||
|} | |} | ||
| Line 276: | Line 276: | ||
The version tracking mechanism should automatically warn the product security group based on a security feed (CVEs, Android Security upgrades) | The version tracking mechanism should automatically warn the product security group based on a security feed (CVEs, Android Security upgrades) | ||
==== Issues ==== | |||
* This part of B2G may differ and generally be handled by a third party, such as a vendor or carrier, thus, they must be the ones running the tracking software | |||
* The tracking software may however be provided to them, with guidance, for example | |||
* Guidance on updates may also be provided instead | |||