| 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: <1337992009.23813.YahooMailClassic@web84502.mail.ne1.yahoo.com> Date: Fri, 25 May 2012 17:26:49 -0700 (PDT) From: kd6lvw@...oo.com To: "Eric W. Biederman" <ebiederm@...ssion.com>, Linus Torvalds <torvalds@...ux-foundation.org> Cc: linux-kernel@...r.kernel.org, Vasiliy Kulikov <segoon@...nwall.com>, Arkadiusz Miskiewicz <a.miskiewicz@...il.com>, Alexey Dobriyan <adobriyan@...il.com>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: Regression Mounting /proc w/ kernel 3.4.0 - "uid" parameter no longer ignored. Ignoring "uid=#" is the documented behavior from the "mount(8)" man page for procfs. That implies that the proposed patch should be [temporarily] installed. I personally don't care if the option is restored or not. My issue was that this side effect was not documented in any way in the change that occurred -- which affected documented behavior. I mount my /proc file system in a "mount -at nonfs" statement in an initialization script. The "uid" optional parameter was in /etc/fstab. I have removed "uid" in my "at home" copy of the configuration but haven't visited the remote server to fix it there (I can't log in from remote as a result of this issue). --- On Fri, 5/25/12, Linus Torvalds <torvalds@...ux-foundation.org> wrote: > If it is *only* uid, maybe we should just expressly ignore it. Like > the (completely untested) attached patch. -- 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