Now i'm completely mystified. Since I'm a member of BugTraq,
I get full disclosure of the bugs that make it there.
Including the recent kernel bugs.
Since I'm in the position to see the problem before the solution,
I'd be happy to repost a summary of security-related changes
to vger, provided of course that I'm able to correlate the changes
with the advisories posted on BugTraq.
Of course, if Alan wanted to cc me on the kernel updates with the full
text of the changes, or if I had access to this new website, I'd still
be willing to repost.
Once a security issue is published to the global internet community
(via BugTraq, vger, or any other method) with regards to the open-source
componant of the linux kernel (i can't speak for non-GPL'd stuff of course)
in a manner consistant with full-disclosure, then I see no legal issue
with posting information that informs users of what fixes are made.
-- Leif Sawyer -- Pi@4398680 leif@gci.net || lsawyer@gci.com || internic: LS2540 (907) 868 - 0116 || ICQ - 3749190 || http://home.gci.net/~leif Network & Security Engineer -- General Communication Inc. PGP Fingerprint: 77 C8 34 B8 FD BC C6 32 5F FE 93 4B AE 6C F7 4E -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GAT d+ s: a C+++(++)$ US++++$ UL++++$ P+++ L++(+++) E--- W+++ N+ o+ K w O- M- V PS+ PE Y+ PGP(+) t+@ 5- X R- tv b++(+++) DI++++ D++ G+ e(+)* h-- r++ y+ PP++++ HH++++ A19 NT{--} ------END GEEK CODE BLOCK------ Decode it! http://www.ebb.org/ungeek/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/