| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <486D4541.25808.C600354@pageexec.freemail.hu> Date: Thu, 03 Jul 2008 21:31:45 +0200 From: pageexec@...email.hu To: Greg KH <greg@...ah.com> CC: linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, torvalds@...ux-foundation.org, stable@...nel.org Subject: Re: Linux 2.6.25.10 [spender's asked to be off the CC] On 3 Jul 2008 at 11:57, Greg KH wrote: > On Thu, Jul 03, 2008 at 10:29:14AM -0700, Greg KH wrote: > Adding 2 more addresses to this thread, as they were said to have > questions about this kernel release. not only this one, but every commit for the past few years that fixed bugs with security impact. for reference: http://lwn.net/Articles/285438/ http://lwn.net/Articles/286263/ http://lwn.net/Articles/287339/ http://lwn.net/Articles/288473/ > Again, if the above information is somehow insufficient as to what > exactly is fixed in the -stable releases, and anyone has questions about > how these release announcements are created, please let me know. what is the disclosure policy used for commits fixing bugs with security impact (both vanilla and -stable, especially if there's a difference)? what do you include/omit? how does it relate to what is declared in Documentation/SecurityBugs? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists