Bug 637

Summary: need documentation for our security process
Product: [Documentation] Reference Reporter: Kevin Tian <kevin.tian>
Component: handbookAssignee: Scott Garman <scott.a.garman>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: poky.doc.watcher, poky.watcher, scott.a.garman, sgw
Version: 1.0   
Target Milestone: 1.0 PointRelease   
Hardware: x86   
OS: Multiple   
Whiteboard: 2011-04-20: 95% complete
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

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.