From: "Michael Kerrisk" <m.kerrisk@gmx.net>
To: "Marcelo Tosatti" <marcelo@conectiva.com.br>
Cc: <linux-kernel@vger.kernel.org>
Subject: [2.4.18 Patch] Update comments in include/linux/capabilities.h
Date: Wed, 26 Jun 2002 13:50:06 +0200 [thread overview]
Message-ID: <000001c21d12$b52df520$0200a8c0@MichaelKerrisk> (raw)
Hello Marcelo
After doing a fairly extensive scan of the 2.4.18 source code, I notice that
a few comments in include/linux/capabilities.h were wrong, and that a few
more things could be added.
Cheers
Miichael
--- linux-2.4.18/include/linux/capability.h Mon Jun 24 10:07:00 2002
+++ linux/include/linux/capability.h Wed Jun 26 12:52:04 2002
@@ -90,12 +90,12 @@
#define CAP_FOWNER 3
-/* Overrides the following restrictions that the effective user ID
- shall match the file owner ID when setting the S_ISUID and S_ISGID
- bits on that file; that the effective group ID (or one of the
- supplementary group IDs) shall match the file owner ID when setting
- the S_ISGID bit on that file; that the S_ISUID and S_ISGID bits are
- cleared on successful return from chown(2) (not implemented). */
+/* Overrides the following restrictions that:
+ the S_ISUID and S_ISGID bits will be turned off when a file is modified;
+ the effective group ID (or one of the supplementary group IDs) shall
+ match the file owner ID when setting the S_ISGID bit on that file;
+ the S_ISUID and S_ISGID bits are cleared on successful return
+ from chown(2) (not implemented). */
#define CAP_FSETID 4
@@ -104,7 +104,7 @@
#define CAP_FS_MASK 0x1f
/* Overrides the restriction that the real or effective user ID of a
- process sending a signal must match the real or effective user ID
+ process sending a signal must match the real or saved-set-user ID
of the process receiving the signal. */
#define CAP_KILL 5
@@ -116,7 +116,7 @@
#define CAP_SETGID 6
/* Allows set*uid(2) manipulation (including fsuid). */
-/* Allows forged pids on socket credentials passing. */
+/* Allows forged uids on socket credentials passing. */
#define CAP_SETUID 7
@@ -139,7 +139,7 @@
#define CAP_NET_BIND_SERVICE 10
-/* Allow broadcasting, listen to multicast */
+/* Allow broadcasting, listen to multicast (unused) */
#define CAP_NET_BROADCAST 11
@@ -210,7 +210,7 @@
/* Allow irix_prctl on mips (setstacksize) */
/* Allow flushing all cache on m68k (sys_cacheflush) */
/* Allow removing semaphores */
-/* Used instead of CAP_CHOWN to "chown" IPC message queues, semaphores
+/* Perform IPC_SET and IPC_RMID operations on IPC message queues,
semaphores
and shared memory */
/* Allow locking/unlocking of shared memory segment */
/* Allow turning swap on/off */
@@ -231,6 +231,8 @@
/* Allow enabling/disabling tagged queuing on SCSI controllers and sending
arbitrary SCSI commands */
/* Allow setting encryption key on loopback filesystem */
+/* Allow calling of setdomainname() and sethostname() */
+/* Allow RLIMIT_NPROC to be overridden */
#define CAP_SYS_ADMIN 21
reply other threads:[~2002-06-26 13:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000001c21d12$b52df520$0200a8c0@MichaelKerrisk' \
--to=m.kerrisk@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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
all inboxes | Powered by JetHome®