Pop quiz: What's wrong with dropping privileges of a process, started as root, to "nobody", like this?
my $uid = getpwnam("nobody");
$< = $uid;
Answer: It's easy to regain root privileges afterwards by simply assigning 0 to $<.
Why is that? Turns out that assigning a uid to $< (or the effective uid $> for that matter) isn't using setuid(), at least not on Linux. Instead, it uses setreuid32() which allows the unprivileged user to switch back to the "saved set-user-ID".
You can see what's going on in a perl script like
$< = $uid;
$> = $uid;
$> = 0;
$< = 0;
by looking at the strace output:
$ sudo strace ./switchback 2>&1 | grep '^set'
setreuid32(99, -1) = 0
setresuid32(-1, 99, -1) = 0
setresuid32(-1, 0, -1) = 0
setreuid32(0, -1) = 0
The last two calls successfully restore root privileges (uid and euid) while running as an unprivileged user.
Question: What's the best way to drop privileges, then? POSIX:setuid( $uid ) seems to work, is that the best practice?
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.