public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: maxim wexler <blissfix@yahoo.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: two identical /etc/sudoers -- only one works
Date: Fri, 25 May 2007 20:14:48 -0700 (PDT)	[thread overview]
Message-ID: <493616.69169.qm@web31713.mail.mud.yahoo.com> (raw)
In-Reply-To: <86y7jc1lo7.fsf@poke.chrekh.se>

> Example:
> 
>   $ pwd
>   /usr/bin
>   $ ls -li sudo
>   8803772 ---s--x--x 2 root root 107240 2007-05-21
> 11:11 sudo*
>   $ find . -inum 8803772
>   ./sudo
>   ./foo
>   $ ls -li foo
>   8803772 ---s--x--x 2 root root 107240 2007-05-21
> 11:11 foo*
> 
> 
> Unfortunately I do not know what's wrong, try to
> strace sudo to see
> what it does, remember that you have to bee root to
> strace a setuid
> program. Look for
> 
> open("/etc/sudoers", O_RDONLY)          = 4
> 
> The 4 is what filedescriptor open returned, and is
> -1 for a failed
> open. 
> 

strace:
<...>
open("/etc/sudoers", O_RDONLY)          = -1 EACCES
(Permission denied)
geteuid32()                             = 1
setresuid32(0, 0, 0)                    = 0
write(2, "sudo: ", 6sudo: )                   = 6
write(2, "can\'t open /etc/sudoers", 23can't open
/etc/sudoers) = 23
write(2, ": ", 2: )                       = 2
write(2, "Permission denied\n", 18Permission denied
)     = 18
<...>

picky@localhost /usr/bin $ ls -li sudo
314108 ---s--x--x 2 root root 106160 Apr 11 09:26 sudo
picky@localhost /usr/bin $ find . -inum 314108
./sudo
./sudoedit
picky@localhost /usr/bin $ ls -li sudoedit
314108 ---s--x--x 2 root root 106160 Apr 11 09:26
sudoedit
picky@localhost /usr/bin $

Just noticed this:

picky@localhost ~ $ ls /
ls: cannot open directory /: Permission denied
picky@localhost ~ $

picky can't even mount a floppy or write to it!

But picky's fstab is identical to heathen's. 

Only thing I can think of: recently had to do emerge
--metadata on account of CacheCorruption error.




 
____________________________________________________________________________________
Sucker-punch spam with award-winning protection. 
Try the free Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/features_spam.html
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-05-26  3:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-24  1:14 [gentoo-user] two identical /etc/sudoers -- only one works maxim wexler
2007-05-24 22:00 ` Walter Dnes
2007-05-25  3:24   ` maxim wexler
2007-05-25 18:16   ` [gentoo-user] " Christer Ekholm
2007-05-25 23:34     ` maxim wexler
2007-05-26  0:19       ` Christer Ekholm
2007-05-26  3:14         ` maxim wexler [this message]
2007-05-26  5:40           ` Boyd Stephen Smith Jr.
2007-05-26 20:37             ` maxim wexler
2007-05-26 21:31           ` Christer Ekholm
2007-05-26 23:29             ` maxim wexler
2007-05-27  0:05               ` Christer Ekholm
2007-05-27  0:14                 ` Arturo 'Buanzo' Busleiman
2007-05-27  0:12               ` Christer Ekholm
2007-05-27  2:33                 ` maxim wexler
2007-05-27 10:59                   ` Christer Ekholm
2007-05-27 17:56                     ` maxim wexler
2007-05-29 21:04           ` Paul Varner
2007-05-29 22:05             ` Mick
2007-05-29 23:11               ` Mike Edenfield
     [not found] <20070530001052.GA24190@waltdnes.org>
2007-05-30  1:36 ` maxim wexler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=493616.69169.qm@web31713.mail.mud.yahoo.com \
    --to=blissfix@yahoo.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox