From: "H. Peter Anvin" <hpa@zytor.com>
To: Oleg Verych <olecom@flower.upol.cz>
Cc: dash list <dash@vger.kernel.org>
Subject: Re: euidaccess() vs non suid /bin/sh (Re: dash test -w oddities)
Date: Wed, 30 Apr 2008 15:52:25 -0700 [thread overview]
Message-ID: <4818F829.60601@zytor.com> (raw)
In-Reply-To: <20080430230109.GR24008@flower.upol.cz>
Oleg Verych wrote:
>> I've asked why it's needed and why euidaccess() from glibc
>> wasn't used, especially in case of selinux stuff.
>
> I wonder even more why access() syscall isn't a solution, because
> /bin/sh isn't set-uid by definition.
>
> #/bin/cc glibc/sysdeps/posix/euidaccess.c
> [...]
> /* If we are not set-uid or set-gid, access does the same. */
> return access (path, mode);
> [...]
> #end_cc
It might be run from a setuid program.
-hpa
next prev parent reply other threads:[~2008-04-30 22:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 21:05 dash test -w oddities Remi Broemeling
2008-04-30 22:38 ` Oleg Verych
2008-04-30 23:01 ` euidaccess() vs non suid /bin/sh (Re: dash test -w oddities) Oleg Verych
2008-04-30 22:52 ` H. Peter Anvin [this message]
2008-05-01 0:19 ` Oleg Verych
2008-05-01 6:03 ` H. Peter Anvin
2008-05-02 16:48 ` Oleg Verych
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=4818F829.60601@zytor.com \
--to=hpa@zytor.com \
--cc=dash@vger.kernel.org \
--cc=olecom@flower.upol.cz \
/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