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
| ||
|
Date: Wed, 17 Sep 2008 15:24:07 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Paul Moore <paul.moore@...com> Cc: sds@...ho.nsa.gov, jmorris@...ei.org, rjw@...k.pl, linux-kernel@...r.kernel.org, kernel-testers@...r.kernel.org, ebiederm@...ssion.com, netdev@...r.kernel.org Subject: Re: [Bug #11500] /proc/net bug related to selinux On Wed, 17 Sep 2008 18:12:59 -0400 Paul Moore <paul.moore@...com> wrote: > > We don't even know the extent of the damage yet. Which distros were > > affected? With which versions of which userspace packages? > > Can I assume that the "right" thing to do would be to find the problem > and revert whatever change caused the issue, yes? Or are we happy to > wait and see since the fallout so far has been minimal? I don't think a revert is justified after all this time. afaik I'm the first person to notice the problem, and it's been out there for multiple months. However it would be good if we could find some not-completely-stinky way of making the old userspace work. otoh, people who are shipping 2.6.25- and 2.6.26-based distros probably wouldn't want such a patch in their kernels anyway. -- 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