summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorJim Meyering <jim@meyering.net>2003-07-12 11:31:55 +0000
committerJim Meyering <jim@meyering.net>2003-07-12 11:31:55 +0000
commitb5125cf5f0752bd25a3aed4026a154af4ab4810c (patch)
treeeee3ab4226af64f5586b3e6063c6c70a5e7ef729 /NEWS
parente5e207df7c66045bf4ced0284b7bdc65c48ac93e (diff)
downloadcoreutils-b5125cf5f0752bd25a3aed4026a154af4ab4810c.tar.xz
*** empty log message ***
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS10
1 files changed, 10 insertions, 0 deletions
diff --git a/NEWS b/NEWS
index 4f5b01bc3..588da78db 100644
--- a/NEWS
+++ b/NEWS
@@ -5,6 +5,16 @@ GNU coreutils NEWS -*- outline -*-
- new program: `[' (much like `test')
** New features
+- chown no longer tries to preserve set-user-ID and set-group-ID bits;
+ on some systems, the chown syscall resets those bits, and previous
+ versions of the chown command would call chmod to restore the original,
+ pre-chown(2) settings, but that behavior is problematic.
+ 1) There was a window whereby a malicious user, M, could subvert a
+ chown command run by some other user and operating on files in a
+ directory where M has write access.
+ 2) Before (and even now, on systems with chown(2) that doesn't reset
+ those bits), an unwary admin. could use chown unwittingly to create e.g.,
+ a set-user-ID root copy of /bin/sh.
- head now accepts --lines=-N (--bytes=-N) to print all but the
N lines (bytes) at the end of the file
- md5sum --check now accepts the output of the BSD md5sum program, e.g.,