From owner-freebsd-hackers Mon Sep 6 13:33:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from online.no (pilt-s.online.no [148.122.208.18]) by hub.freebsd.org (Postfix) with ESMTP id A8D0315372 for ; Mon, 6 Sep 1999 13:33:19 -0700 (PDT) (envelope-from shaun.jurrens@stud.uni-regensburg.de) Received: from dakota.shamz.net (ti34a21-0071.dialup.online.no [130.67.68.71]) by online.no (8.9.3/8.9.1) with ESMTP id WAA16708; Mon, 6 Sep 1999 22:31:59 +0200 (MET DST) Received: (from shaun@localhost) by dakota.shamz.net (8.9.3/8.9.3) id AAA27810; Mon, 6 Sep 1999 00:19:18 +0200 (CEST) (envelope-from shaun) Date: Mon, 6 Sep 1999 00:19:18 +0200 From: Shaun Jurrens To: Sheldon Hearn Cc: hackers@FreeBSD.ORG Subject: Re: Proposal: Add generic username for 3rd-party MTA's Message-ID: <19990906001917.G385@dakota.shamz.net> References: <199909040034.UAA02063@sable.cc.vt.edu> <15136.936554136@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <15136.936554136@axl.noc.iafrica.com>; from Sheldon Hearn on Sun, Sep 05, 1999 at 07:55:36PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At the risk of being flamed for my inexperience... I caught the thread here more or less because it was a conspicuous mess on my list (and thanks to the flamers with the name suggestions, even longer). I still think that something good could be done here that of course would cause a little work, but might serve to teach those somewhat newer to the system (as I am) more about user.||:group naming schemes on the one hand and perhaps more about the secure use of such schemes in combination with their uid/gid's. A standard configure script for ports that are possible know security hazards (as MTA's can be) could suggest typical naming conventions (and a short reason for them) and uid/gid's (although these are more arbitrary) for said ports. If they were to go so far as to create new user/groups or simply prompt their creation seems like no minor security question, would however add to a certain automation (scripts to add users aren't unheard of) to the process. An initial make would prompt check if the port had been configured for user.group and if the uid/gid existed and simply chown the necessary files after install. This would help the new user develop a naming scheme as well as a sense of why while at the same time allowing advanced users to more quickly (I know chown is no big task) adapt new ports to system-wide uid/gid conventions. I simply see here a possible compromise that offers benefits to both sides. If I had a little more experience myself, I'd come with a concrete proposal and the work done, but you'll have to be patient. I will someday contribute, but for now I can only boast of the stabiliy and enjoy the beauty of all of your work in FreeBSD. -- Yours truly, Shaun D. Jurrens (hopefully soon: shaun@shamz.net) IRCnick: shamz #chillout #unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message