From: Rob Landley <landley@trommello.org>
To: linux-kernel@vger.kernel.org
Subject: Security question: "Text file busy" overwriting executables but not shared libraries?
Date: Tue, 2 Oct 2001 22:55:02 -0400 [thread overview]
Message-ID: <01100222550205.02611@localhost.localdomain> (raw)
Anybody want to venture an opinion why overwriting executable files that are
currently in use gives you a "text file busy" error, but overwriting shared
libraries that are in use apparently works just fine (modulo a core dump if
you aren't subtle about your run-time patching)?
Permissions are still enforced, but it seems to me somebody who cracks root
on a system could potentially modify the behavior of important system daemons
without changing their process ID numbers.
Did I miss something somewhere?
Rob
next reply other threads:[~2001-10-03 6:55 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 2:55 Rob Landley [this message]
2001-10-03 7:07 ` Security question: "Text file busy" overwriting executables but not shared libraries? Alexander Viro
-- strict thread matches above, loose matches on Subject: below --
2001-10-03 12:49 Jesse Pollard
2001-10-03 18:06 ` Eric W. Biederman
2001-10-03 23:20 ` Rob Landley
2001-10-04 3:38 ` Eric W. Biederman
2001-10-04 4:19 ` Alexander Viro
2001-10-04 6:15 ` Eric W. Biederman
2001-10-04 8:21 ` CaT
2001-10-04 8:35 ` john slee
2001-10-04 8:45 ` CaT
2001-10-04 13:11 ` Eric W. Biederman
2001-10-04 8:30 ` Ville Herva
2001-10-04 9:46 ` Erik Andersen
2001-10-04 8:53 ` Andreas Schwab
2001-10-04 13:23 ` Eric W. Biederman
2001-10-04 5:38 ` Linus Torvalds
2001-10-04 5:44 ` Alexander Viro
2001-10-04 5:49 ` Linus Torvalds
2001-10-04 15:01 ` Eric W. Biederman
2001-10-04 15:49 ` Linus Torvalds
2001-10-04 16:02 ` Richard Gooch
2001-10-04 16:20 ` Andreas Schwab
2001-10-04 17:19 ` Richard Gooch
2001-10-04 16:11 ` Alexander Viro
2001-10-04 17:25 ` Eric W. Biederman
2001-10-13 14:53 ` Jamie Lokier
2001-10-13 17:13 ` Linus Torvalds
2001-10-13 18:18 ` Rik van Riel
2001-10-13 18:40 ` Pablo Alcaraz
2001-10-13 19:05 ` Jamie Lokier
2001-10-13 18:54 ` Jamie Lokier
2001-10-13 19:23 ` Linus Torvalds
2001-10-13 19:46 ` Jamie Lokier
2001-10-13 21:43 ` Aaron Lehmann
2001-10-13 22:27 ` Eric W. Biederman
2001-10-13 22:50 ` Aaron Lehmann
2001-10-15 11:24 ` Jamie Lokier
2001-10-13 22:19 ` Linus Torvalds
2001-10-14 6:49 ` Eric W. Biederman
2001-10-14 8:17 ` Xavier Bestel
2001-10-14 15:40 ` Linus Torvalds
2001-10-14 18:49 ` Eric W. Biederman
2001-10-15 11:43 ` Jamie Lokier
2001-10-13 22:41 ` Richard Gooch
2001-10-15 11:35 ` Jamie Lokier
2001-10-15 11:51 ` Alexander Viro
2001-10-15 12:29 ` Jamie Lokier
2001-10-13 22:27 ` Linus Torvalds
2001-10-14 21:43 ` Mark H. Wood
2001-10-04 5:53 ` Richard Gooch
2001-10-04 6:50 ` George Greer
2001-10-04 12:54 ` John Levon
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=01100222550205.02611@localhost.localdomain \
--to=landley@trommello.org \
--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.