On Wed, 2 Jun 1999, Pollywog wrote:
> I had this problem yesterday and the cause is a faulty package, the one
> containing the su executable. It needs to be reset suid root.
There's a fix available now. From the changelog:
shellutils (1.16-6.5) unstable; urgency=high
* Fix su not-suid-ro
On 02-Jun-99 Steve Lamb wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Wed, 2 Jun 1999 17:59:56 -0400, David Gaudine wrote:
>
>>power failure. (i.e. while I'm still logged in and don't have to
>>work from a rescue disk.)
>
> Have you looked at the password/shadow entries f
On 02-Jun-99 David Gaudine wrote:
> I just telnetted to my potato system and tried to su to root.
> (I know I should be using ssh, but it's my ssh problem that
> I was trying to fix, thanks Brad.) I got the message
>su: incorrect password
> Surely I didn't forget my own root password, but jus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 2 Jun 1999 17:59:56 -0400, David Gaudine wrote:
>power failure. (i.e. while I'm still logged in and don't have to
>work from a rescue disk.)
Have you looked at the password/shadow entries for root?
- --
Steve C. Lamb |
I just telnetted to my potato system and tried to su to root.
(I know I should be using ssh, but it's my ssh problem that
I was trying to fix, thanks Brad.) I got the message
su: incorrect password
Surely I didn't forget my own root password, but just in case,
I went physically to the system wh
5 matches
Mail list logo
