From owner-freebsd-current  Tue Jan 14 01:30:49 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id BAA03286
          for current-outgoing; Tue, 14 Jan 1997 01:30:49 -0800 (PST)
Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA03279
          for <freebsd-current@freebsd.org>; Tue, 14 Jan 1997 01:30:43 -0800 (PST)
Received: (from davidn@localhost)
          by labs.usn.blaze.net.au (8.8.4/8.8.4)
	  id UAA02683; Tue, 14 Jan 1997 20:30:03 +1100 (EST)
Message-ID: <Mutt.19970114203002.davidn@labs.blaze.net.au>
Date: Tue, 14 Jan 1997 20:30:02 +1100
From: davidn@unique.usn.blaze.net.au (David Nugent)
To: peter@hw.nl (Peter Korsten)
Cc: kargl@troutmask.apl.washington.edu (Steven G. Kargl),
        freebsd-current@freebsd.org
Subject: Re: su appears broken?
References: <199701140646.WAA29600@troutmask.apl.washington.edu> <199701140826.JAA11870@orac.hw.nl>
X-Mailer: Mutt 0.56
Mime-Version: 1.0
In-Reply-To: <199701140826.JAA11870@orac.hw.nl>; from Peter Korsten on Jan 14, 1997 09:26:16 +0100
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Peter Korsten writes:
> I barely dare ask, but is the x bit of tcsh set?

:-)

No the bug was real. I have no idea why tcsh reacted like it did,
but the end effect of a stray '~' was that su could only su to root,
and not to a non-root account. The fix was just committed.


Regards,

David Nugent - Unique Computing Pty Ltd - Melbourne, Australia
Voice +61-3-9791-9547  Data/BBS +61-3-9792-3507  3:632/348@fidonet
davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/