[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OBSD 3.1 i386 su problem: invalid script: /usr/libexec/auth/login_krb4-or-pwd

To: "Todd C. Miller" <Todd.Miller@courtesan.com>
Subject: Re: OBSD 3.1 i386 su problem: invalid script: /usr/libexec/auth/login_krb4-or-pwd
From: "Raymond C. Rodgers" <obsd@bbnk.dhs.org>
Date: Sun, 30 Jun 2002 14:40:20 -0700
Cc: misc@openbsd.org
References: <Your message of "Sat, 29 Jun 2002 09:59:32 PDT." <5.1.0.14.2.20020629094040.02a29508@ipostoffice.worldnet.att.net> <5.1.0.14.2.20020629094040.02a29508@ipostoffice.worldnet.att.net>

That did it! Thanks for that tip, I did extract the file sets by hand 
(because I haven't had any luck upgrading automatically through the boot 
disk) and I didn't use the 'p' flag... I guess the wise thing to do right 
about now would be to redo the extractions with the 'p' flag skipping the 
etc31.tgz file set.

Thanks again!
Raymond
At 09:36 PM 6/29/2002, Todd C. Miller wrote:
>Often this is because /usr/bin/su is not setuid root, usually because
>the 'p' flag was not used when untarring file sets by hand.
>
>  - todd

References:
- OBSD 3.1 i386 su problem: invalid script: /usr/libexec/auth/login_krb4-or-pwd
  - From: "Raymond C. Rodgers" <obsd@bbnk.dhs.org>
- Re: OBSD 3.1 i386 su problem: invalid script: /usr/libexec/auth/login_krb4-or-pwd
  - From: "Todd C. Miller" <Todd.Miller@courtesan.com>

Prev by Date: Re: OBSD 3.1 i386 su problem: invalid script: /usr/libexec/auth/login_krb4-or-pwd
Next by Date: allowing gre through 3.0 firewall
Prev by thread: Re: OBSD 3.1 i386 su problem: invalid script: /usr/libexec/auth/login_krb4-or-pwd
Next by thread: unable to boot any self-compiled kernel on ultra10
Index(es):
- Date
- Thread