From owner-freebsd-current Sat Dec 20 09:22:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA29146 for current-outgoing; Sat, 20 Dec 1997 09:22:29 -0800 (PST) (envelope-from owner-freebsd-current) Received: from limbo.rtfm.net (nathan@rtfm.net [204.141.125.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA29132 for ; Sat, 20 Dec 1997 09:20:49 -0800 (PST) (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.8.8/8.8.6) id MAA16495; Sat, 20 Dec 1997 12:20:48 -0500 (EST) Message-ID: <19971220122048.25138@rtfm.net> Date: Sat, 20 Dec 1997 12:20:48 -0500 From: Nathan Dorfman To: freebsd-current@FreeBSD.org Subject: su and login.conf Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 Sender: owner-freebsd-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Anyone else out there think that su should read login.conf when started without the - flag? 1) When you su to root, and don't use the - flag, you probably still want the stuff in /sbin, /usr/sbin, etc. In fact, more than a few ports makefiles (and make world IIRC) want utilities in the sbin directories without specifying a full path. 2) The umask. The umask for most users is 0, while the umask for root is 022. With an inherited umask for an su, you can realize that noone can access the new port you've installed. If I'm not mistaken, su without - is supposed to not set the - flag in your shell's argv[0] to prevent it from executing it's .profile or .login; the settings in login.conf should be affected by even a temporary su to install a port or make world or something else that requires a brief access to root. Anyway, just a suggestion, anyone else feel this way? -- ________________ _______________________________ / Nathan Dorfman V PGP: finger nathan@rtfm.net / / nathan@rtfm.net | http://www.rtfm.net /