From: Olaf Dietsche <olaf.dietsche#list.linux-kernel@t-online.de>
To: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com, viro@math.psu.edu
Subject: [PATCH][RFC] 2.5.42 (2/2): Filesystem capabilities user tool
Date: Fri, 18 Oct 2002 21:07:39 +0200 [thread overview]
Message-ID: <87smz3mupw.fsf@goat.bogus.local> (raw)
This is the change capabilities tool. It is a first cut at "managing"
capabilities and not very comfortable.
You need to tell where the .capabilities file is. This must be located
in the mountpoint of the filesystem.
Given a filename, how can I locate the mountpoint of the associated
filesystem? If someone knows, how to do this, please tell me.
Example:
# chmod u-s /bin/ping
# chcap /.capabilities 0x2000 0 0x2000 /bin/ping
This sets the effective and permitted CAP_NET_RAW capability for /bin/ping.
Regards, Olaf.
--- /dev/null Thu Mar 21 19:31:20 2002
+++ chcap.c Fri Oct 18 21:02:15 2002
@@ -0,0 +1,74 @@
+#include <asm/types.h>
+#include <sys/types.h>
+#include <sys/stat.h>
+#include <sys/fcntl.h>
+#include <stdio.h>
+#include <unistd.h>
+
+static const char *capfile;
+static struct stat capbuf;
+
+static void chcap(ino_t ino, __u32 *caps)
+{
+ int fd = open(capfile, O_WRONLY);
+ if (fd < 0) {
+ perror(capfile);
+ exit(1);
+ } else {
+ off_t rc = lseek(fd, ino * 3 * sizeof(*caps), SEEK_SET);
+ if (rc == -1)
+ perror(capfile);
+ else
+ write(fd, caps, 3 * sizeof(*caps));
+
+ close(fd);
+ }
+}
+
+int main(int argc, char **argv)
+{
+ __u32 caps[3];
+ int rc;
+ int i = 1;
+
+ if (argc < 6) {
+ fprintf(stderr, "usage: %s /path/to/.capabilities eff inh perm file ...\n", argv[0]);
+ exit(2);
+ }
+
+ capfile = argv[i++];
+ rc = access(capfile, F_OK);
+ if (rc != 0) {
+ int fd = open(capfile, O_CREAT | O_EXCL | O_RDONLY, 0600);
+ if (fd >= 0) {
+ close(fd);
+ } else {
+ perror(capfile);
+ exit(1);
+ }
+ }
+
+ rc = stat(capfile, &capbuf);
+ if (rc != 0) {
+ perror(capfile);
+ }
+
+ caps[0] = strtol(argv[i++], 0, 0);
+ caps[1] = strtol(argv[i++], 0, 0);
+ caps[2] = strtol(argv[i++], 0, 0);
+
+ for (; i < argc; ++i) {
+ struct stat buf;
+ rc = stat(argv[i], &buf);
+ if (rc == 0) {
+ if (buf.st_dev == capbuf.st_dev)
+ chcap(buf.st_ino, caps);
+ else
+ fprintf(stderr, "%s: %s is on different file system\n", argv[i], capfile);
+ } else {
+ perror(argv[i]);
+ }
+ }
+
+ return 0;
+}
next reply other threads:[~2002-10-18 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 19:07 Olaf Dietsche [this message]
2002-10-24 12:31 ` [PATCH][RFC] 2.5.44 " Olaf Dietsche
2002-10-27 13:55 ` [PATCH][RFC] 2.5.42 " Andreas Gruenbacher
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=87smz3mupw.fsf@goat.bogus.local \
--to=olaf.dietsche#list.linux-kernel@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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®