Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 8 May 2017 11:45:46 +0000
From:      Rick Macklem <rmacklem@uoguelph.ca>
To:        Slawa Olhovchenkov <slw@zxy.spb.ru>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
Subject:   more default uid/gid for NFS in mountd
Message-ID:  <YTXPR01MB01895E8D60DD369C1762785DDDEE0@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM>

next in thread | raw e-mail | index | archive | help
Hi,

Five years ago (yea, it slipped through a crack;-), Slawa reported that fil=
es
created by root would end up owned by uid 2**32-2 (-2 as uint32_t).
This happens if there is no "-maproot=3D<user>" in the /etc/exports line.

The cause is obvious. The value is set to -2 by default.

The question is... Should this be changed to 65534 (ie "nobody")?
- It would seem more consistent to make it the uid of nobody, but I can als=
o see
  the argument that since it has been like this *forever*, that changing it=
 would be
  a POLA violation.
What do others think?

It is also the case that mountd.c doesn't look "nobody" up in the password =
database
to set the default. It would be nice to do this, but it could result in the=
 mountd daemon
getting "stuck" during a boot waiting for an unresponsive LDAP service or s=
imilar.
Does doing this sound like a good idea?

Thanks for any comments, rick
ps: Here's the original email thread, in case you are interested:
      https://lists.freebsd.org/pipermail/freebsd-stable/2012-March/066868.=
html




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTXPR01MB01895E8D60DD369C1762785DDDEE0>