From owner-freebsd-security Tue Jun 1 20:14: 0 1999 Delivered-To: freebsd-security@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 8CCF414D6C for ; Tue, 1 Jun 1999 20:13:58 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA86277; Tue, 1 Jun 1999 20:13:42 -0700 (PDT) (envelope-from dillon) Date: Tue, 1 Jun 1999 20:13:42 -0700 (PDT) From: Matthew Dillon Message-Id: <199906020313.UAA86277@apollo.backplane.com> To: Andrew Kenneth Milton Cc: matt@Mlink.NET (matt), akm@mail.theinternet.com.au, bc@thehub.com.au, cain@tasam.com, freebsd-security@FreeBSD.ORG Subject: Re: Shell Account system References: <199906020254.MAA22390@mail.theinternet.com.au> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org :| :| Actually, You normally would make an account called irc or ircd, chmod :| that home directory 700, set the D/S paths in the ircd config, and run :| it FROM the irc home dir, with the conf chmod 600. There's absolutely :| no need to SUID ircd at all, nor would I recommend it. : :Unless you have multiple remote admins, who you don't want to be :able to stuff with the conf files, but, you do want them to be able :to restart the daemon. : :-- :Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew You can always argue that your favoriate methods of admin requires binaries to be suid-root, but all it means is that you need to change your methods. In this case, I think of several ways to avoid running ircd as root or with root and have admins who do not have root or access to the ircd account to nevertheless be able to restart the daemon. Perhaps with a special port/password, or simply with an suid-ircd program which kills and restarts ircd. No brainer. No root access required. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message