Bug 637 - need documentation for our security process
Summary: need documentation for our security process
Status: RESOLVED FIXED
Alias: None
Product: Reference
Classification: Documentation
Component: handbook (show other bugs)
Version: 1.0
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.0 PointRelease
Assignee: Scott Garman
QA Contact:
URL:
Whiteboard: 2011-04-20: 95% complete
Depends on:
Blocks:
 
Reported: 2011-01-06 16:16 UTC by Kevin Tian
Modified: 2011-05-02 15:22 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Tian 2011-01-06 16:16:53 UTC
We have one task in 1.0 to define the security update process which I think has been on-going under Scott Garman. It'd be good to document this process to prove our secure development process
Comment 1 Scott Garman 2011-04-18 15:49:37 UTC
Moving the target milestone to something current so it stays visible in my lists.
Comment 2 Scott Garman 2011-05-02 15:22:07 UTC
This has been written up and is currently being made available on GitHub:

https://github.com/ScottGarman/YoctoSecurityAdvisoryTrackingUtility/blob/master/readme.txt

I'm happy to migrate it to the Yocto git repository, but I'm not sure yet where Richard will want it. It is a standalone tool, so putting the scripts into scripts/ may not make sense.