Date: Fri, 06 Sep 2013 10:00:28 -0700 From: Darren Pilgrim <list_freebsd@bluerosetech.com> To: Aryeh Friedman <aryeh.friedman@gmail.com> Cc: FreeBSD Ports ML <freebsd-ports@freebsd.org> Subject: Re: setting the password of a automatically created account Message-ID: <522A0A2C.1040703@bluerosetech.com> In-Reply-To: <CAGBxaXkiTnKR6m%2BSuZ4OTbVDgPbNN4wk7q2AsVYXjkYhmv3oxw@mail.gmail.com> References: <CAGBxaXnyVyAMcGnbGTHatcgZe8Lc-H4=OenEF0HvPEO4ajgmYA@mail.gmail.com> <52294561.R3v3YVxoTsoMnIfV%perryh@pluto.rain.com> <CAGBxaXkiTnKR6m%2BSuZ4OTbVDgPbNN4wk7q2AsVYXjkYhmv3oxw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/5/2013 9:00 PM, Aryeh Friedman wrote: > related questions: > > 1. How do I add the user to wheel (has it's own group but needs to be in > wheel for reason number #2)? > 2. How do I modify (in the safest possible way) an other port's installed > config file(s) (namely I need to in the case of this port modify > /usr/local/etc/sudoers to allow the no password option for wheel members)? The answer to both is you don't. Include documentation telling the admin exactly what needs special access or elevated priveleges and let the admin make that happen. If you think something needs root because it needs to open something in /dev, tell the admin it needs to do something with /dev/foo. Devd and other mechanisms can provide that without root access. The same idea applies to almost all of what people typically think requires root access.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?522A0A2C.1040703>