From: DervishD <raul@pleyades.net>
To: Jon Burgess <Jon_Burgess@eur.3com.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Changing argv[0] under Linux.
Date: Thu, 16 Jan 2003 13:58:43 +0100 [thread overview]
Message-ID: <20030116125843.GD1358@DervishD> (raw)
In-Reply-To: <80256CB0.003F4ECF.00@notesmta.eur.3com.com>
Hi Jon :)
> It is easy to do a mount() system call, the rootfs can be ro.
Yes, but you still need a mountpoint. Lot of worries for
something as trivial and useless as changing the ps identity ;))
> > What if /proc/self/exe is not part form procfs,
> > but from some evil user ;))
> Would the user not need root privilegdes to mess with /proc?
/proc/self/exe doesn't need to be in procfs... If proc is not
mounted... Anyway it was just an example. The degree of evil-user
intrusion in a machine for doing something like that is quite high.
There are simpler ways of attacking a machine if you can forge
/proc/self/exe :))
> Is there any good reason why init should not be executable
> by root only?
My init refuses to run if not called by the superuser ;) because
I think the same as you and anyway my init doesn't need a shutdown
command, it works with a keycombo that root controls.
Raúl
next prev parent reply other threads:[~2003-01-16 12:55 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 11:31 Changing argv[0] under Linux Jon Burgess
2003-01-16 12:58 ` DervishD [this message]
[not found] <20030116130013.GE1358@DervishD>
[not found] ` <200301161315.h0GDFLM27487@isengard.accucard.com>
2003-01-17 10:08 ` DervishD
-- strict thread matches above, loose matches on Subject: below --
2003-01-16 10:12 Jon Burgess
2003-01-16 10:32 ` DervishD
[not found] <122203493@toto.iv>
2003-01-14 22:55 ` Peter Chubb
2003-01-14 18:59 DervishD
2003-01-14 19:10 ` Richard B. Johnson
2003-01-14 19:14 ` DervishD
2003-01-14 19:43 ` Richard B. Johnson
2003-01-14 19:50 ` DervishD
2003-01-14 19:56 ` Richard B. Johnson
2003-01-14 20:23 ` Mark Mielke
2003-01-14 20:28 ` Richard B. Johnson
2003-01-14 21:21 ` Mark Mielke
2003-01-15 14:00 ` Richard B. Johnson
2003-01-15 16:43 ` Richard B. Johnson
2003-01-15 16:57 ` DervishD
2003-01-14 22:00 ` DervishD
2003-01-21 14:16 ` Bill Davidsen
2003-01-21 15:33 ` DervishD
2003-01-14 20:25 ` Philippe Troin
2003-01-14 20:56 ` Richard B. Johnson
2003-01-14 22:04 ` DervishD
2003-01-14 23:04 ` Bob Miller
2003-01-14 23:11 ` Bob Miller
2003-01-15 4:46 ` Mark Mielke
2003-01-15 8:25 ` jw schultz
2003-01-15 11:41 ` DervishD
2003-01-15 13:16 ` Jakob Oestergaard
2003-01-15 16:22 ` DervishD
2003-01-15 16:47 ` Jakob Oestergaard
2003-01-15 17:10 ` DervishD
2003-01-15 21:26 ` Andreas Schwab
2003-01-15 21:36 ` Jesse Pollard
2003-01-15 22:03 ` DervishD
2003-01-16 9:19 ` Dorin Lazar
2003-01-15 11:35 ` DervishD
2003-01-14 21:55 ` Miquel van Smoorenburg
2003-01-14 22:04 ` Valdis.Kletnieks
2003-01-15 11:28 ` DervishD
2003-01-27 7:47 ` Anuradha Ratnaweera
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=20030116125843.GD1358@DervishD \
--to=raul@pleyades.net \
--cc=Jon_Burgess@eur.3com.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.