From owner-freebsd-ports@FreeBSD.ORG  Fri Sep  6 17:01:29 2013
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 89C9C54A
 for <freebsd-ports@freebsd.org>; Fri,  6 Sep 2013 17:01:29 +0000 (UTC)
 (envelope-from list_freebsd@bluerosetech.com)
Received: from yoshi.bluerosetech.com (yoshi.bluerosetech.com
 [IPv6:2607:f2f8:a450::66])
 (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 70A722F5D
 for <freebsd-ports@freebsd.org>; Fri,  6 Sep 2013 17:01:29 +0000 (UTC)
Received: from chombo.houseloki.net (c-76-27-220-79.hsd1.wa.comcast.net
 [76.27.220.79])
 by yoshi.bluerosetech.com (Postfix) with ESMTPSA id AA856E6040;
 Fri,  6 Sep 2013 10:01:28 -0700 (PDT)
Received: from [IPv6:fc00:970::70be:f335:56cc:10bc] (unknown
 [IPv6:fc00:970::70be:f335:56cc:10bc])
 by chombo.houseloki.net (Postfix) with ESMTPSA id D88E7A25;
 Fri,  6 Sep 2013 10:00:27 -0700 (PDT)
Message-ID: <522A0A2C.1040703@bluerosetech.com>
Date: Fri, 06 Sep 2013 10:00:28 -0700
From: Darren Pilgrim <list_freebsd@bluerosetech.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Aryeh Friedman <aryeh.friedman@gmail.com>
Subject: Re: setting the password of a automatically created account
References: <CAGBxaXnyVyAMcGnbGTHatcgZe8Lc-H4=OenEF0HvPEO4ajgmYA@mail.gmail.com>
 <52294561.R3v3YVxoTsoMnIfV%perryh@pluto.rain.com>
 <CAGBxaXkiTnKR6m+SuZ4OTbVDgPbNN4wk7q2AsVYXjkYhmv3oxw@mail.gmail.com>
In-Reply-To: <CAGBxaXkiTnKR6m+SuZ4OTbVDgPbNN4wk7q2AsVYXjkYhmv3oxw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: FreeBSD Ports ML <freebsd-ports@freebsd.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Sep 2013 17:01:29 -0000

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.