Date: Sat, 27 Feb 1999 14:38:20 -0500 From: Jim Bloom <bloom@acm.org> To: Bruce Evans <bde@zeta.org.au> Cc: current@FreeBSD.ORG Subject: Re: Really! strange uid value Message-ID: <36D849AC.A36743C1@acm.org> References: <199902271617.DAA18010@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
I believe that (uid_t)-2 has a lot to do with the user nobody. That was the historical reason why the uid 65534 for chosen for nobody back when uid_t was only 16 bits. I would recommend that the default mapped uid for root be defined as 65534 instead of (uid_t)-2. This seems to make the most sense when trying to avoid user suprises. I would also suggest the default gid be changed similarly. (On Solaris 2.5.1, nobody is now uid 60001 with nobody4 as uid 65534 (for SunOS 4).) Jim Bloom bloom@acm.org Bruce Evans wrote: > > 4294967294 is just the default mapped uid for root. It is (uid_t)-2. > See mountd sources. It has nothing to do with user nobody or 65534, > except possibly on buggy clients that silently truncate it mod 65536. > Perhaps it is a bug to use (uid_t)-2 instead of 65534. For clients > with only 16-bit uid_t's you would want to keep all uids on the > server < 65536. > > Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36D849AC.A36743C1>