Parent Directory | Revision Log
|Links to HEAD:||(view) (download) (annotate)|
move retired to the top level hierarchy so people can easily checkout just the active issues
retire issues that: 1) sarge is no longer vulnerable to 2) upstream >= 2.6.17.x has a fix 3) have no ubuntu kernels listed these issues could still use some polishing - listing of patch names used, fixed versions marked, etc - but they no longer need to be tracked
start tracking security issues in linux-2.6.16
mark sarge2 issues as released... a bit prematurely
drop generic 2.6.8 - just track 2.6.8-sarge-security. Move all of the issues that were fixed in <= 2.6.8-16 to the 2.6.8-sarge-security bucket so we don't lose that info.
add corrected bug reference
fix has gone upstream; pending in 2.6.8-16sarge2; removed invalid bug reference
track issues against linux-2.6 instead of against each major release 2.6.12, 2.6.13, 2.6.14
use sync-pkg-list to add 2.4.18 hppa kernels to the tracker
mitre is retroactively using CVE-XXXX-XXX instead of CAN-XXXX-XXXX, let's do the same
move patch-tracking into a non-user-specific location, as announced on the mailing list
run everything through the (probably poorly named) sync-pkg-list script. That makes sure that every file has a field for every tree listed in 00pkglist
get all patches in the same format (which requires a few tweaks)
"branch" horms' patch tree so i can do some hacking on the system..
Extra annotations for CAN-2005-3055
Break out CVEs, separate CVE and 2.6-stable patch notes into separate directories
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
|Powered by ViewVC 1.1.5|