| 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: <20080227235952.70a31d9f.akpm@linux-foundation.org> Date: Wed, 27 Feb 2008 23:59:52 -0800 From: Andrew Morton <akpm@...ux-foundation.org> To: Pavel Emelyanov <xemul@...nvz.org> Cc: Ian Kent <raven@...maw.net>, Kernel Mailing List <linux-kernel@...r.kernel.org>, autofs mailing list <autofs@...ux.kernel.org>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, "Eric W. Biederman" <ebiederm@...ssion.com> Subject: Re: [PATCH 3/4] autofs4 - track uid and gid of last mount requestor On Thu, 28 Feb 2008 10:51:08 +0300 Pavel Emelyanov <xemul@...nvz.org> wrote: > > So, why do we need the uid and gid? When someone walks over an autofs > > dentry that is meant to cause a mount we send a request packet to the > > daemon via a pipe which includes the process uid and gid, and as part of > > the lookup we set macros for several mount map substitution variables, > > derived from the uid and gid of the process requesting the mount and > > they can be used within autofs maps. > > Why do we need the uid then? Is just pid not enough to uniquely > identify a task? The problem is that the userspace daemon is restarted. ie: it exits and is re-run. It then needs to pick up various state from its previous run. -- 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