Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: unido!zgdvda!zhang@uunet.uu.net (Ning Zhang)
Newsgroups: comp.sys.sun
Subject: su(1) bug
Keywords: SunOS
Message-ID: <468@zgdvda.UUCP>
Date: 25 Apr 89 04:47:38 GMT
Sender: usenet@rice.edu
Organization: ZGDV Darmstadt, FRG
Lines: 15
Approved: Sun-Spots@rice.edu
Original-Date: 5 Apr 89 15:13:58 GMT
X-Sun-Spots-Digest: Volume 7, Issue 244, message 9 of 10

On SunOS 3.5 and Ultrix (2.x and 3.0) systems here, su(1) still cannot
correctly track super-user log. On Ultrix, the follow shows su(1) tells
nothing about who has become a super-user or who has tried su(1) command
but failed.

	su < /dev/tty

Then a message like "SU:  /dev/tty" will be printed out on console, and
"SU:  /dev/tty Wed Apr  5 12:25:40 1989" in /usr/adm/sulog.  Any comments?
Perhaps, Ultrix's su(1), rexecd(8), rshd(8), etc. should do more checking.

On SunOS 3.5, I got "SU: (null) /dev/tty" on console.

Ning Zhang
PS: su "" < /dev/tty if there is a line "::0:0:::" in /etc/passwd!