| 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: Sun, 16 Nov 2008 15:07:56 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Bernhard Walle <bwalle@...e.de> Cc: x86@...nel.org, linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org, crash-utility@...hat.com, Bernhard Walle <bwalle@...e.de> Subject: Re: Turn CONFIG_STRICT_DEVMEM in sysctl dev.mem.restricted > The protection in the general case and the ability to do live debugging. What protection. You've completely failed to explain or provide a single example of any protection provided by the STRICT_DEVMEM code. > only a half of the story. The truth is that at least RHEL has /dev/crash > exactly to circumvent that /dev/mem restriction. Don't tell me that this > is better than having that sysctl entry. ;-) Which nicely illustrates what a waste of time the whole thing is. Please do the decent thing and just turn the crap concerned off. The fact other vendors get it wrong doesn't mean you need to copy. Even better submit a patch to remove this rubbish from the kernel completely. Your patch is still adding bells and whistles to a useless turd. In fact this patch is worse. Without this patch the turd can be disabled and left out, with your patch everyone now has to compile in said turd pile. NAK this changeset. Alan -- 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