| 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: <20071012124808.GA32693@atjola.homenet> Date: Fri, 12 Oct 2007 14:48:08 +0200 From: Björn Steinbrink <B.Steinbrink@....de> To: "Robert P. J. Day" <rpjday@...dspring.com> Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: what is the rationale for "TAINT_USER"? On 2007.10.12 08:37:04 -0400, Robert P. J. Day wrote: > On Fri, 12 Oct 2007, Björn Steinbrink wrote: > > > On 2007.10.12 08:04:20 -0400, Robert P. J. Day wrote: > > > > > > i can see what the theoretical purpose for it is here: > > > > > > http://kerneltrap.org/node/6656 > > > > > > but it's not clear how it can possibly be set from userland given > > > that: > > > > > > $ grep -r TAINT_USER * > > > include/linux/kernel.h:#define TAINT_USER (1<<6) > > > kernel/panic.c: tainted & TAINT_USER ? 'U' : ' ', > > > $ > > > > > > am i missing something screamingly obvious? > > > > Grepping for "tainted" leads me to: > > > > echo 32 > /proc/sys/kernel/tainted > > ???. i have no idea what you were grepping through to find that > phrase, but TAINT_USER would seem to be equivalent to echo 64, not > echo 32, anyway, no? Oops, yeah, 64... And it didn't lead me to the exact phrase, but the sysctl handler, which (implicitly) led me to that command. Sorry for the confusion. Björn - 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