Phriction Trusted Firmware Collaboration TF-M Security Patch Release Process History Version 10 vs 11
Version 10 vs 11
Version 10 vs 11
Edits
Edits
- Edit by shebuk, Version 11
- Jul 15 2021 3:40 PM
- Edit by abhishek-pandit, Version 10
- Jul 15 2021 3:34 PM
| « Previous Change | Next Change » |
| Edit Older Version 10... | Edit Older Version 11... |
Content Changes
Content Changes
(WARNING) Draft in review
This document outlines the proposal for backporting of TF-M security fixes to previous releases and the testing policy of such releases.
**Updated proposal including feedback gathered over the time. 7/6/21**
- A security vulnerability found and fixed at any moment resulted in fixes applied to the ongoing code and tagged with an incremented hotfix number. I.e., having the latest tag v1.4.0, a new security fix will be staged by v1.4.1.
- There will be no fixes for past versions to avoid LTS maintenance and backporting overheads.
- The fix shall be tested using the standard regression test suit on Arm reference platform, agreed by maintainers.
**Previous text moved in to the comment below**
(WARNING) Draft in review
This document outlines the proposal for applying TF-M security fixes to latest release and the testing policy of such releases.
**Updated proposal including feedback gathered over the time. 7/6/21**
- A security vulnerability found and fixed at any moment resulted in fixes applied to the ongoing code and tagged with an incremented hotfix number. I.e., having the latest tag v1.4.0, a new security fix will be staged by v1.4.1.
- There will be no fixes for past versions to avoid LTS maintenance and backporting overheads.
- The fix shall be tested using the standard regression test suite on Arm reference platform, agreed by maintainers.
**Previous text moved in to the comment below**
(WARNING) Draft in review
This document outlines the proposal for backporting ofapplying TF-M security fixes to previouslatest releases and the testing policy of such releases.
**Updated proposal including feedback gathered over the time. 7/6/21**
- A security vulnerability found and fixed at any moment resulted in fixes applied to the ongoing code and tagged with an incremented hotfix number. I.e., having the latest tag v1.4.0, a new security fix will be staged by v1.4.1.
- There will be no fixes for past versions to avoid LTS maintenance and backporting overheads.
- The fix shall be tested using the standard regression test suite on Arm reference platform, agreed by maintainers.
**Previous text moved in to the comment below**