exporting capability code/name pairs (try 2nd)
Subsystems (4)
PATCH 1/3 exporting capability code/name pairs (try 2nd)
We can apply this patch to kernel-2.6.24.
It enables to export code/name pairs of capabilities at /sys/kernel/capability/, as follows:
--------
[root@saba ~]# ls /sys/kernel/capability/
cap_audit_control cap_kill cap_setgid cap_sys_ptrace cap_audit_write cap_lease cap_setpcap cap_sys_rawio cap_chown cap_linux_immutable cap_setuid cap_sys_resource cap_dac_override cap_mknod cap_sys_admin cap_sys_time cap_dac_read_search cap_net_admin cap_sys_boot cap_sys_tty_config cap_fowner cap_net_bind_service cap_sys_chroot index cap_fsetid cap_net_broadcast cap_sys_module version cap_ipc_lock cap_net_raw cap_sys_nice cap_ipc_owner cap_setfcap cap_sys_pacct
[root@saba ~]# cat /sys/kernel/capability/cap_setfcap 31
[root@saba ~]# cat /sys/kernel/capability/version 0x19980330
[root@saba ~]#
--------
In the previous version of kernel, we have no way to obtain what capabilities are supported in this running kernel.
The libcap is a library to provide fundamental facilities to handle capabilities. It has to be rebuilt when new capabilities are added, because it statically holds the list of all capabilities generated from kernel header automatically on its build environment.
This patch enables libcap to obtain these infomation dynamically, and improves userspace portability.
Please consider to apply these patches.
Thanks,
----
kernel/Makefile | 9 ++++++++ kernel/capability.c | 36 +++++++++++++++++++++++++++++++++++ scripts/mkcapnames.sh | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 95 insertions(+), 0 deletions(-)
kernel/Makefile +9 -0
@@ -80,3 +80,12 @@ quiet_cmd_ikconfiggz = IKCFG $@ targets += config_data.h $(obj)/config_data.h: $(obj)/config_data.gz FORCE $(call if_changed,ikconfiggz) + +# cap_names.h contains the code/name pair of capabilities. +# It is generated using include/linux/capability.h automatically. +$(obj)/capability.o: $(obj)/cap_names.h +quiet_cmd_cap_names = CAPS $@ + cmd_cap_names = /bin/sh $(src)/../scripts/mkcapnames.sh > $@ +targets += cap_names.h +$(obj)/cap_names.h: $(src)/../scripts/mkcapnames.sh $(src)/../include/linux/capability.h FORCE + $(call if_changed,cap_names)
kernel/capability.c +36 -0
@@ -245,3 +245,39 @@ int capable(int cap)return __capable (current, cap); }EXPORT_SYMBOL (capable); + +/* +* Export the list of capabilities on /sys/kernel/capability +*/ +#define SYSFS_CAPABILITY_ENTRY (_name, _fmt, ...) \ + static ssize_t _name##_show(struct kset *kset, char *buffer) \ + { \ + return scnprintf(buffer, PAGE_SIZE, _fmt, __VA_ARGS__); \ + } \ + static struct subsys_attribute _name##_attr = __ATTR_RO(_name) + +/* +* capability_attrs[] is generated automatically by scripts/mkcapnames.sh +* This script parses include/linux/capability.h +*/ +#include "cap_names.h" + +static struct attribute_group capability_attr_group = { + .name ="capability" , + .attrs = capability_attrs, +}; + +static int __init capability_export_names (void ) +{ +int rc; + + rc =sysfs_create_group (&kernel_subsys.kobj, + &capability_attr_group); +if (rc) { +printk (KERN_ERR "Unable to export capabilities\n" ); +return rc; + } + +return 0 ; +} +__initcall (capability_export_names);
scripts/mkcapnames.sh +50 -0
50 lines not on this page · raw message
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
KaiGai,
While this is cute :-), I guess I'm still not all that convinced that this is needed.
libcap already had some (admittedly not quite working) support for numeric values of capabilities not currently defined (which I believe is now fixed in top of trunk):
# ./setcap 35=i ./setcap # ./getcap ./setcap ./setcap = 35+i
Although, I obviously can't argue that this is as readable as your approach, it does seem unlikely that the rate of addition of new capabilities will be all that great, and you can recompile everything capability related in user-space on a live system without a reboot. Further, if anyone ever wants to translate the capabilities into another language, it seems like user-space is a much better place for that than in the kernel.
This patch also requires that /sys be mounted. How does that work for code operating early in the boot process or in a chroot environment (where an incapable uid=0 account being able to read/write /sys & /proc files can do more than a little damage)?
None of this touches on the fact that most utility applications that will support capabilities "the right way"(TM), will need the #define's at compile time for each of the capabilities they require (so they can pepper critical regions with cap_set_flag()/cap_set_proc() code.
When I mentioned this last time, you said you felt this feature was more aimed at admin applications like {get,set,pam_}cap. This is fine, but none of these admin applications 'use' capabilities, they just make them available/visible for other utility applications to use - which gets us back to my point; the utility apps can't use them (properly) without having compiled-in support to use them appropriately, which requires the #define's at compile time or an appropriate vintage of sys/capability.h which comes with an appropriately modern version of libcap. So, practically speaking all the capabilities the applications on a system should need should be present in the libcap on the system.
All that being said, the friendliness factor of this is somewhat undeniable, and so I can see why folk might want it in the kernel anyway. If so, would it possible to move this code into security/capability.c and not in the main kernel per-se - protected with a configuration option? If it does appear in the kernel, we'll obviously add your libcap changes too. If it doesn't, then perhaps we can meet your needs with a slight modification to your libcap patch to read the capabilities from an optional /etc/XXX file - and make text visibility of 'late breaking' capabilities something that the admin can tweak as needed?
Cheers
Andrew
Kohei KaiGai wrote:
| We can apply this patch to kernel-2.6.24. | It enables to export code/name pairs of capabilities | at /sys/kernel/capability/, as follows:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFHmZCh+bHCR3gb8jsRArf8AJ0QK/c54cvOp7Uo3FksZL1OHM3SEQCfdQ02 kOkmExkYjcpdF4xs0hcgrTI=
=rZNg
-----END PGP SIGNATURE-----
Andrew,
Thanks for your comments.
Quoted 12 lines · Andrew G. Morgan
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1KaiGai,
While this is cute :-), I guess I'm still not all that convinced that this is needed.
libcap already had some (admittedly not quite working) support for numeric values of capabilities not currently defined (which I believe is now fixed in top of trunk):
Quoted 8 lines
# ./setcap 35=i ./setcap # ./getcap ./setcap ./setcap = 35+iAlthough, I obviously can't argue that this is as readable as your approach, it does seem unlikely that the rate of addition of new capabilities will be all that great, and you can recompile everything capability related in user-space on a live system without a reboot.
cap_set_flag() and cap_from_text() checks whether required capability code is in between 0 and __CAP_BITS, or not.
I don't think it works correctly. Is it necessary to obtain this bound dynamically?
Quoted 3 lines
Further, if anyone ever wants to translate the capabilities into another language, it seems like user-space is a much better place for that than in the kernel.
Are you intend to translate "cap_net_admin" into native language representation, for example?
I want to see how Chinese represents it :), but I think it is different issue with kernel dose not expose its suporing capabilities.
Quoted 4 lines
This patch also requires that /sys be mounted. How does that work for code operating early in the boot process or in a chroot environment (where an incapable uid=0 account being able to read/write /sys & /proc files can do more than a little damage)?
When this patch cannot access /sys, it does not provide dynamically collected code/name pairs, and it works with statically constructed table as current libcap doing.
The patched libcap never switch to the dynamic table without successes in all steps of initialization. Thus, there is no major regression on this facilitiy.
Quoted 5 lines
None of this touches on the fact that most utility applications that will support capabilities "the right way"(TM), will need the #define's at compile time for each of the capabilities they require (so they can pepper critical regions with cap_set_flag()/cap_set_proc() code.
Quoted 10 lines
When I mentioned this last time, you said you felt this feature was more aimed at admin applications like {get,set,pam_}cap. This is fine, but none of these admin applications 'use' capabilities, they just make them available/visible for other utility applications to use - which gets us back to my point; the utility apps can't use them (properly) without having compiled-in support to use them appropriately, which requires the #define's at compile time or an appropriate vintage of
sys/capability.hwhich comes with an appropriately modern version of libcap. So, practically speaking all the capabilities the applications on a system should need should be present in the libcap on the system.
Hmm, you are correct. Indeed, applications using capabilities have to be built with the new libcap which provides fresh sys/capabilitity.h. It is like a chicken and egg argument.
However, all applications are always built on its running environment, like RPM packages. These can be delivered as pre-built packages.
Quoted 10 lines
All that being said, the friendliness factor of this is somewhat undeniable, and so I can see why folk might want it in the kernel anyway. If so, would it possible to move this code into
security/capability.cand not in the main kernel per-se - protected with a configuration option? If it does appear in the kernel, we'll obviously add your libcap changes too. If it doesn't, then perhaps we can meet your needs with a slight modification to your libcap patch to read the capabilities from an optional/etc/XXXfile - and make text visibility of 'late breaking' capabilities something that the admin can tweak as needed?
I think optional configuration file is not a good idea. It can make unneeded confusion.
If necessary, I'll move this features into security/capability.c and add a Kconfig option to select it.
Thanks,
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Re: [PATCH 1/3] exporting capability code/name pairs (try #3)
Quoted 11 lines
Quoted 10 lines
All that being said, the friendliness factor of this is somewhat undeniable, and so I can see why folk might want it in the kernel anyway. If so, would it possible to move this code into
security/capability.cand not in the main kernel per-se - protected with a configuration option? If it does appear in the kernel, we'll obviously add your libcap changes too. If it doesn't, then perhaps we can meet your needs with a slight modification to your libcap patch to read the capabilities from an optional/etc/XXXfile - and make text visibility of 'late breaking' capabilities something that the admin can tweak as needed?
Quoted 5 lines
I think optional configuration file is not a good idea. It can make unneeded confusion.
If necessary, I'll move this features into
security/capability.cand add aKconfigoption to select it.
The following patch enables to export the list of capabilities supported on the running kernel, under /sys/kernel/capability .
Changelog from the previous version:
- Implementation is moved into security/capability.c from kernel/capability.c
- A Kconfig option SECURITY_CAPABILITIES_EXPORT is added to tuen on/off this feature.
[kaigai@saba ~]$ for x in /sys/kernel/capability/*
Quoted 3 lines
do
echo "$x -->cat $x"
done
/sys/kernel/capability/cap_audit_control --> 30/sys/kernel/capability/cap_audit_write --> 29
- snip -/sys/kernel/capability/cap_sys_time --> 25/sys/kernel/capability/cap_sys_tty_config --> 26/sys/kernel/capability/index --> 31/sys/kernel/capability/version --> 0x19980330
[kaigai@saba ~]$
Thanks,
----
scripts/mkcapnames.sh | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ security/Kconfig | 9 ++++++++ security/Makefile | 11 ++++++++++ security/capability.c | 49 ++++++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 119 insertions(+), 0 deletions(-)
scripts/mkcapnames.sh +50 -0
@@ -0,0 +1,50 @@ +#!/bin/sh + +# +# generate a cap_names.h file from include/linux/capability.h +# + +BASEDIR=`dirname $0` + +echo '#ifndef CAP_NAMES_H' +echo '#define CAP_NAMES_H' +echo +echo '/*' +echo ' * Do NOT edit this file directly.' +echo ' * This file is generated from include/linux/capability.h automatically' +echo ' */' +echo +echo '#ifndef SYSFS_CAPABILITY_ENTRY' +echo '#error cap_names.h should be included from kernel/capability.c' +echo '#else' + +echo 'SYSFS_CAPABILITY_ENTRY(version, "0x%08x\n", _LINUX_CAPABILITY_VERSION);' + +cat ${BASEDIR}/../include/linux/capability.h \ + | egrep '^#define CAP_[A-Z_]+[ ]+[0-9]+$' \ + | awk 'BEGIN { + max_code = -1; + } + { + if ($3 > max_code) + max_code = $3; + printf("SYSFS_CAPABILITY_ENTRY(%s, \"%%u\\n\", %s);\n", tolower($2), $2); + } + END { + printf("SYSFS_CAPABILITY_ENTRY(index, \"%%u\\n\", %u);\n", max_code); + }' + +echo +echo 'static struct attribute *capability_attrs[] = {' +echo ' &version_attr.attr,' +echo ' &index_attr.attr,' + +cat ${BASEDIR}/../include/linux/capability.h \ + | egrep '^#define CAP_[A-Z_]+[ ]+[0-9]+$' \ + | awk '{ printf (" &%s_attr.attr,\n", tolower($2)); }' + +echo ' NULL,' +echo '};' + +echo '#endif /* SYSFS_CAPABILITY_ENTRY */' +echo '#endif /* CAP_NAMES_H */'
security/Kconfig +9 -0
@@ -90,6 +90,15 @@ config SECURITY_FILE_CAPABILITIES If in doubt, answer N. +config SECURITY_CAPABILITIES_EXPORT + bool "Exporting capabilities kernel supported" + depends on SECURITY_CAPABILITIES && SYSFS + help + This enables to export any capabilities which are supported + in the running kernel. + + If you are unsure how to answer this question, answer Y. + config SECURITY_ROOTPLUG bool "Root Plug Support" depends on USB=y && SECURITY
security/Makefile +11 -0
@@ -16,3 +16,14 @@ obj-$(CONFIG_SECURITY) += security.o dummy.o inode.o obj-$(CONFIG_SECURITY_SELINUX) += selinux/built-in.o obj-$(CONFIG_SECURITY_CAPABILITIES) += commoncap.o capability.o obj-$(CONFIG_SECURITY_ROOTPLUG) += commoncap.o root_plug.o + +ifeq ($(CONFIG_SECURITY_CAPABILITIES_EXPORT),y) +# cap_names.h contains the code/name pair of capabilities. +# It is generated using include/linux/capability.h automatically. +$(obj)/capability.o: $(obj)/cap_names.h +quiet_cmd_cap_names = CAPS $@ + cmd_cap_names = /bin/sh $(src)/../scripts/mkcapnames.sh > $@ +targets += cap_names.h +$(obj)/cap_names.h: $(src)/../scripts/mkcapnames.sh $(src)/../include/linux/capability.h FORCE + $(call if_changed,cap_names) +endif
security/capability.c +49 -0
61 lines not on this page · raw message
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Re: [PATCH 1/3] exporting capability code/name pairs (try #3)
Quoted 17 lines · Kohei KaiGai
Quoted 11 lines
Quoted 10 lines
All that being said, the friendliness factor of this is somewhat undeniable, and so I can see why folk might want it in the kernel anyway. If so, would it possible to move this code into
security/capability.cand not in the main kernel per-se - protected with a configuration option? If it does appear in the kernel, we'll obviously add your libcap changes too. If it doesn't, then perhaps we can meet your needs with a slight modification to your libcap patch to read the capabilities from an optional/etc/XXXfile - and make text visibility of 'late breaking' capabilities something that the admin can tweak as needed?Quoted 5 lines
I think optional configuration file is not a good idea. It can make unneeded confusion.
If necessary, I'll move this features into
security/capability.cand add aKconfigoption to select it.
Quoted 6 lines
The following patch enables to export the list of capabilities supported on the running kernel, under
/sys/kernel/capability.Changelog from the previous version:
- Implementation is moved intosecurity/capability.cfromkernel/capability.c
- AKconfigoptionSECURITY_CAPABILITIES_EXPORTis added to tuen on/off this feature.
can you explain one more time exactly what this lets you do that you absolutely can't do with the current api?
I for one don't really object even if it is "duplicated" since it is far easier to use, and I frequently have systems where kernel and userspace are out of sync so /usr/include/sys/capabilities is worthless... Though I'm a little worried that b/scripts/mkcapnames.sh is the kind of thing that'll eventually break, but I suppose that's my fault for objecting two duplicated list of capability definitions :)
-serge
Quoted 189 lines
[kaigai@saba ~]$ for x in
/sys/kernel/capability/*Quoted 3 lines
do
echo "$x -->cat $x"
done
/sys/kernel/capability/cap_audit_control--> 30/sys/kernel/capability/cap_audit_write--> 29
- snip -/sys/kernel/capability/cap_sys_time--> 25/sys/kernel/capability/cap_sys_tty_config--> 26/sys/kernel/capability/index--> 31/sys/kernel/capability/version-->0x19980330
[kaigai@saba ~]$Thanks,
Signed-off-by KaiGai Kohei <[email protected]>----
scripts/mkcapnames.sh | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ security/Kconfig | 9 ++++++++ security/Makefile | 11 ++++++++++ security/capability.c | 49 ++++++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 119 insertions(+), 0 deletions(-)scripts/mkcapnames.sh +50
-0@@ -0,0 +1,50 @@ +#!/bin/sh + +# +# generate a cap_names.h file from include/linux/capability.h +# + +BASEDIR=`dirname $0` + +echo '#ifndef CAP_NAMES_H' +echo '#define CAP_NAMES_H' +echo +echo '/*' +echo ' * Do NOT edit this file directly.' +echo ' * This file is generated from include/linux/capability.h automatically' +echo ' */' +echo +echo '#ifndef SYSFS_CAPABILITY_ENTRY' +echo '#error cap_names.h should be included from kernel/capability.c' +echo '#else' + +echo 'SYSFS_CAPABILITY_ENTRY(version, "0x%08x\n", _LINUX_CAPABILITY_VERSION);' + +cat ${BASEDIR}/../include/linux/capability.h \ + | egrep '^#define CAP_[A-Z_]+[ ]+[0-9]+$' \ + | awk 'BEGIN { + max_code = -1; + } + { + if ($3 > max_code) + max_code = $3; + printf("SYSFS_CAPABILITY_ENTRY(%s, \"%%u\\n\", %s);\n", tolower($2), $2); + } + END { + printf("SYSFS_CAPABILITY_ENTRY(index, \"%%u\\n\", %u);\n", max_code); + }' + +echo +echo 'static struct attribute *capability_attrs[] = {' +echo ' &version_attr.attr,' +echo ' &index_attr.attr,' + +cat ${BASEDIR}/../include/linux/capability.h \ + | egrep '^#define CAP_[A-Z_]+[ ]+[0-9]+$' \ + | awk '{ printf (" &%s_attr.attr,\n", tolower($2)); }' + +echo ' NULL,' +echo '};' + +echo '#endif /* SYSFS_CAPABILITY_ENTRY */' +echo '#endif /* CAP_NAMES_H */'security/Kconfig +9
-0@@ -90,6 +90,15 @@ config SECURITY_FILE_CAPABILITIES If in doubt, answer N. +config SECURITY_CAPABILITIES_EXPORT + bool "Exporting capabilities kernel supported" + depends on SECURITY_CAPABILITIES && SYSFS + help + This enables to export any capabilities which are supported + in the running kernel. + + If you are unsure how to answer this question, answer Y. + config SECURITY_ROOTPLUG bool "Root Plug Support" depends on USB=y && SECURITYsecurity/Makefile +11
-0@@ -16,3 +16,14 @@ obj-$(CONFIG_SECURITY) += security.o dummy.o inode.o obj-$(CONFIG_SECURITY_SELINUX) += selinux/built-in.o obj-$(CONFIG_SECURITY_CAPABILITIES) += commoncap.o capability.o obj-$(CONFIG_SECURITY_ROOTPLUG) += commoncap.o root_plug.o + +ifeq ($(CONFIG_SECURITY_CAPABILITIES_EXPORT),y) +# cap_names.h contains the code/name pair of capabilities. +# It is generated using include/linux/capability.h automatically. +$(obj)/capability.o: $(obj)/cap_names.h +quiet_cmd_cap_names = CAPS $@ + cmd_cap_names = /bin/sh $(src)/../scripts/mkcapnames.sh > $@ +targets += cap_names.h +$(obj)/cap_names.h: $(src)/../scripts/mkcapnames.sh $(src)/../include/linux/capability.h FORCE + $(call if_changed,cap_names) +endifsecurity/capability.c +49
-0@@ -20,6 +20,8 @@#include <linux/netlink.h> #include <linux/ptrace.h> #include <linux/moduleparam.h> +#include <linux/kobject.h> +#include <linux/sysfs.h> static struct security_operations capability_ops = { .ptrace = cap_ptrace,@@ -58,6 +60,53 @@ static int secondary;static int capability_disable;module_param_named (disable, capability_disable, int,0 ); +#ifdef CONFIG_SECURITY_CAPABILITIES_EXPORT +/* +* Export the list of capabilities on /sys/kernel/capability +*/ +struct capability_attribute { +struct attribute attr; +ssize_t (*show)(struct kobject *kobj, +struct capability_attribute *attr, +char *buffer); +ssize_t (*store)(struct kobject *kobj, +struct capability_attribute *attr, +const char *buffer,size_t count); +}; + +#define SYSFS_CAPABILITY_ENTRY (_name, _fmt, ...) \ + static ssize_t _name##_show(struct kobject *kobj, \ + struct capability_attribute *attr, \ + char *buffer) \ + { \ + return scnprintf(buffer, PAGE_SIZE, _fmt, __VA_ARGS__); \ + } \ + static struct capability_attribute _name##_attr = __ATTR_RO(_name) +/* +* capability_attrs[] is generated automatically by scripts/mkcapnames.sh +* This script parses include/linux/capability.h +*/ +#include "cap_names.h" + +static struct attribute_group capability_attr_group = { + .name ="capability" , + .attrs = capability_attrs, +}; + +static int __init capability_export_names (void ) +{ +int rc; + + rc =sysfs_create_group (kernel_kobj, &capability_attr_group); +if (rc) { +printk (KERN_ERR "Unable to export capabilities\n" ); +return rc; + } +return 0 ; +} +__initcall (capability_export_names); +#endif +static int __init capability_init (void ) {if (capability_disable) {Signature · 3 lines
-- OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Re: [PATCH 1/3] exporting capability code/name pairs (try #3)
Quoted 19 lines · Serge E. Hallyn
Quoted 18 lines · Kohei KaiGai
Quoted 10 lines
Quoted 10 lines
All that being said, the friendliness factor of this is somewhat undeniable, and so I can see why folk might want it in the kernel anyway. If so, would it possible to move this code into
security/capability.cand not in the main kernel per-se - protected with a configuration option? If it does appear in the kernel, we'll obviously add your libcap changes too. If it doesn't, then perhaps we can meet your needs with a slight modification to your libcap patch to read the capabilities from an optional/etc/XXXfile - and make text visibility of 'late breaking' capabilities something that the admin can tweak as needed?Quoted 5 lines
I think optional configuration file is not a good idea. It can make unneeded confusion.
If necessary, I'll move this features into
security/capability.cand add aKconfigoption to select it.The following patch enables to export the list of capabilities supported on the running kernel, under
/sys/kernel/capability.
Quoted 6 lines
Quoted 3 lines
Changelog from the previous version:
- Implementation is moved intosecurity/capability.cfromkernel/capability.c
- AKconfigoptionSECURITY_CAPABILITIES_EXPORTis added to tuen on/off this feature.can you explain one more time exactly what this lets you do that you absolutely can't do with the current api?
Please consider the following situation:
A user intend to run an application which use a new capability supported at new kernel without synced libcap. In this case, the application cannot work well, because libcap prevent to use new capability.
When the kernel and libcap are not synced, the header files provided by libcap pacakge is not reliable. Typically, kernel developer sometimes faces such a situation. :)
This feature can fill the gap with providing a new interface to collect capabilities supported by the running kernel collectly.
Quoted 6 lines
I for one don't really object even if it is "duplicated" since it is far easier to use, and I frequently have systems where kernel and userspace are out of sync so
/usr/include/sys/capabilitiesis worthless... Though I'm a little worried thatb/scripts/mkcapnames.shis the kind of thing that'll eventually break, but I suppose that's my fault for objecting two duplicated list of capability definitions :)
Are you worried about "mkcapnames.sh" get broken in the future version?
If so, we can add a code to check whether this script works correctly, or not
like:
-- at security/capability.c
#include <linux/capability.h>
: #if CAP_LAST_CAP != ARRAY_SIZE(capability_attrs) #error "mkcapnames.sh added fewer or more entries than expected!" #endif
Thanks,
Quoted 193 lines
-serge
Quoted 188 lines
[kaigai@saba ~]$ for x in
/sys/kernel/capability/*Quoted 3 lines
do
echo "$x -->cat $x"
done
/sys/kernel/capability/cap_audit_control--> 30/sys/kernel/capability/cap_audit_write--> 29
- snip -/sys/kernel/capability/cap_sys_time--> 25/sys/kernel/capability/cap_sys_tty_config--> 26/sys/kernel/capability/index--> 31/sys/kernel/capability/version-->0x19980330
[kaigai@saba ~]$Thanks,
Signed-off-by KaiGai Kohei <[email protected]>----
scripts/mkcapnames.sh | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ security/Kconfig | 9 ++++++++ security/Makefile | 11 ++++++++++ security/capability.c | 49 ++++++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 119 insertions(+), 0 deletions(-)scripts/mkcapnames.sh +50
-0@@ -0,0 +1,50 @@ +#!/bin/sh + +# +# generate a cap_names.h file from include/linux/capability.h +# + +BASEDIR=`dirname $0` + +echo '#ifndef CAP_NAMES_H' +echo '#define CAP_NAMES_H' +echo +echo '/*' +echo ' * Do NOT edit this file directly.' +echo ' * This file is generated from include/linux/capability.h automatically' +echo ' */' +echo +echo '#ifndef SYSFS_CAPABILITY_ENTRY' +echo '#error cap_names.h should be included from kernel/capability.c' +echo '#else' + +echo 'SYSFS_CAPABILITY_ENTRY(version, "0x%08x\n", _LINUX_CAPABILITY_VERSION);' + +cat ${BASEDIR}/../include/linux/capability.h \ + | egrep '^#define CAP_[A-Z_]+[ ]+[0-9]+$' \ + | awk 'BEGIN { + max_code = -1; + } + { + if ($3 > max_code) + max_code = $3; + printf("SYSFS_CAPABILITY_ENTRY(%s, \"%%u\\n\", %s);\n", tolower($2), $2); + } + END { + printf("SYSFS_CAPABILITY_ENTRY(index, \"%%u\\n\", %u);\n", max_code); + }' + +echo +echo 'static struct attribute *capability_attrs[] = {' +echo ' &version_attr.attr,' +echo ' &index_attr.attr,' + +cat ${BASEDIR}/../include/linux/capability.h \ + | egrep '^#define CAP_[A-Z_]+[ ]+[0-9]+$' \ + | awk '{ printf (" &%s_attr.attr,\n", tolower($2)); }' + +echo ' NULL,' +echo '};' + +echo '#endif /* SYSFS_CAPABILITY_ENTRY */' +echo '#endif /* CAP_NAMES_H */'security/Kconfig +9
-0@@ -90,6 +90,15 @@ config SECURITY_FILE_CAPABILITIES If in doubt, answer N. +config SECURITY_CAPABILITIES_EXPORT + bool "Exporting capabilities kernel supported" + depends on SECURITY_CAPABILITIES && SYSFS + help + This enables to export any capabilities which are supported + in the running kernel. + + If you are unsure how to answer this question, answer Y. + config SECURITY_ROOTPLUG bool "Root Plug Support" depends on USB=y && SECURITYsecurity/Makefile +11
-0@@ -16,3 +16,14 @@ obj-$(CONFIG_SECURITY) += security.o dummy.o inode.o obj-$(CONFIG_SECURITY_SELINUX) += selinux/built-in.o obj-$(CONFIG_SECURITY_CAPABILITIES) += commoncap.o capability.o obj-$(CONFIG_SECURITY_ROOTPLUG) += commoncap.o root_plug.o + +ifeq ($(CONFIG_SECURITY_CAPABILITIES_EXPORT),y) +# cap_names.h contains the code/name pair of capabilities. +# It is generated using include/linux/capability.h automatically. +$(obj)/capability.o: $(obj)/cap_names.h +quiet_cmd_cap_names = CAPS $@ + cmd_cap_names = /bin/sh $(src)/../scripts/mkcapnames.sh > $@ +targets += cap_names.h +$(obj)/cap_names.h: $(src)/../scripts/mkcapnames.sh $(src)/../include/linux/capability.h FORCE + $(call if_changed,cap_names) +endifsecurity/capability.c +49
-0@@ -20,6 +20,8 @@#include <linux/netlink.h> #include <linux/ptrace.h> #include <linux/moduleparam.h> +#include <linux/kobject.h> +#include <linux/sysfs.h> static struct security_operations capability_ops = { .ptrace = cap_ptrace,@@ -58,6 +60,53 @@ static int secondary;static int capability_disable;module_param_named (disable, capability_disable, int,0 ); +#ifdef CONFIG_SECURITY_CAPABILITIES_EXPORT +/* +* Export the list of capabilities on /sys/kernel/capability +*/ +struct capability_attribute { +struct attribute attr; +ssize_t (*show)(struct kobject *kobj, +struct capability_attribute *attr, +char *buffer); +ssize_t (*store)(struct kobject *kobj, +struct capability_attribute *attr, +const char *buffer,size_t count); +}; + +#define SYSFS_CAPABILITY_ENTRY (_name, _fmt, ...) \ + static ssize_t _name##_show(struct kobject *kobj, \ + struct capability_attribute *attr, \ + char *buffer) \ + { \ + return scnprintf(buffer, PAGE_SIZE, _fmt, __VA_ARGS__); \ + } \ + static struct capability_attribute _name##_attr = __ATTR_RO(_name) +/* +* capability_attrs[] is generated automatically by scripts/mkcapnames.sh +* This script parses include/linux/capability.h +*/ +#include "cap_names.h" + +static struct attribute_group capability_attr_group = { + .name ="capability" , + .attrs = capability_attrs, +}; + +static int __init capability_export_names (void ) +{ +int rc; + + rc =sysfs_create_group (kernel_kobj, &capability_attr_group); +if (rc) { +printk (KERN_ERR "Unable to export capabilities\n" ); +return rc; + } +return 0 ; +} +__initcall (capability_export_names); +#endif +static int __init capability_init (void ) {if (capability_disable) {Signature · 3 lines
-- OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Re: [PATCH 1/3] exporting capability code/name pairs (try #3)
Quoted 27 lines · Kohei KaiGai
Quoted 26 lines · Serge E. Hallyn
Quoted 25 lines · Kohei KaiGai
Quoted 12 lines
Quoted 4 lines
All that being said, the friendliness factor of this is somewhat undeniable, and so I can see why folk might want it in the kernel anyway. If so, would it possible to move this code into
security/capability.cand not in the main kernel per-se - protectedQuoted 8 lines
with
a configuration option? If it does appear in the kernel, we'll obviously
add your libcap changes too. If it doesn't, then perhaps we can meet your needs with a slight modification to your libcap patch to read the capabilities from an optional/etc/XXXfile - and make text visibility of 'late breaking' capabilities something that the admin can tweak as needed?Quoted 5 lines
I think optional configuration file is not a good idea. It can make unneeded confusion.
If necessary, I'll move this features into
security/capability.cand add aKconfigoption to select it.The following patch enables to export the list of capabilities supported on the running kernel, under
/sys/kernel/capability.Changelog from the previous version:
- Implementation is moved intosecurity/capability.cfromkernel/capability.c
- AKconfigoptionSECURITY_CAPABILITIES_EXPORTis added to tuen on/off this feature.
Quoted 8 lines
Quoted 2 lines
can you explain one more time exactly what this lets you do that you absolutely can't do with the current api?
Please consider the following situation:
A user intend to run an application which use a new capability supported at new kernel without synced libcap. In this case, the application cannot work well, because libcap prevent to use new capability.
(Though we don't want to encourage application writers to not use libcap...)
Quoted 3 lines
When the kernel and libcap are not synced, the header files provided by libcap pacakge is not reliable. Typically, kernel developer sometimes faces such a situation. :)
Yeah it would definately be nice for me.
Quoted 15 lines
This feature can fill the gap with providing a new interface to collect capabilities supported by the running kernel collectly.
Quoted 6 lines
I for one don't really object even if it is "duplicated" since it is far easier to use, and I frequently have systems where kernel and userspace are out of sync so
/usr/include/sys/capabilitiesis worthless... Though I'm a little worried thatb/scripts/mkcapnames.shis the kind of thing that'll eventually break, but I suppose that's my fault for objecting two duplicated list of capability definitions :)Are you worried about "
mkcapnames.sh" get broken in the future version?If so, we can add a code to check whether this script works correctly, or not
Quoted 7 lines
like:
-- atsecurity/capability.c#include <linux/capability.h> :#if
CAP_LAST_CAP!=ARRAY_SIZE(capability_attrs)#error "mkcapnames.shadded fewer or more entries than expected!" #endif
Yeah, the regexp misfiring was my biggest concern so this should help.
thanks,
-serge
PATCH 1/1 exporting capability code/name pairs (try #4)
This patch enables to export code/name pair of capabilities supported on the running kernel, under the /sys/kernel/capability . We can apply it onto the latest Linus's git tree.
Changes from the previous version:
- I added "names/" ans "codes/" directories, and we can use them to lookup capability code or name non-sequentially.
In the previous version, we had to scan whole of entries to lookup capability name by its code.
(required by Andrew Morgan)
- I added an assertion when "mkcapname.sh" works incorrectly. (required by Serge E.Hallyn)
In addition, Andrew suggested me to export these translation by symlinks to reduce the number of invocation of system call.
However, current sysfs interface does not allows to create symlinks with invalid indication.
Thus, this patch exports them as regular files.
--------------------------------------------------------
[kaigai@saba ~]$ ls -R /sys/kernel/capability//sys/kernel/capability/:
codes names version
/sys/kernel/capability/codes:
0 10 12 14 16 18 2 21 23 25 27 29 30 32 4 6 8 1 11 13 15 17 19 20 22 24 26 28 3 31 33 5 7 9
/sys/kernel/capability/names:
cap_audit_control cap_kill cap_net_raw cap_sys_nice cap_audit_write cap_lease cap_setfcap cap_sys_pacct cap_chown cap_linux_immutable cap_setgid cap_sys_ptrace cap_dac_override cap_mac_admin cap_setpcap cap_sys_rawio cap_dac_read_search cap_mac_override cap_setuid cap_sys_resource cap_fowner cap_mknod cap_sys_admin cap_sys_time cap_fsetid cap_net_admin cap_sys_boot cap_sys_tty_config cap_ipc_lock cap_net_bind_service cap_sys_chroot cap_ipc_owner cap_net_broadcast cap_sys_module
[kaigai@saba ~]$ cat /sys/kernel/capability/codes/20 cap_sys_pacct
[kaigai@saba ~]$ cat /sys/kernel/capability/names/cap_mknod 27
[kaigai@saba ~]$
--------------------------------------------------------
Any comment please.
Thanks,
----
scripts/mkcapnames.sh | 44 +++++++++++++++++++ security/Kconfig | 9 ++++ security/Makefile | 11 +++++ security/capability.c | 115 +++++++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 179 insertions(+), 0 deletions(-)
scripts/mkcapnames.sh +44 -0
@@ -0,0 +1,44 @@ +#!/bin/sh + +# +# generate a cap_names.h file from include/linux/capability.h +# + +CAPHEAD="`dirname $0`/../include/linux/capability.h" +REGEXP='^#define CAP_[A-Z_]+[ ]+[0-9]+$' +NUMCAP=`cat "$CAPHEAD" | egrep -c "$REGEXP"` + +echo '#ifndef CAP_NAMES_H' +echo '#define CAP_NAMES_H' +echo +echo '/*' +echo ' * Do NOT edit this file directly.' +echo ' * This file is generated from include/linux/capability.h automatically' +echo ' */' +echo +echo '#if !defined(SYSFS_CAP_NAME_ENTRY) || !defined(SYSFS_CAP_CODE_ENTRY)' +echo '#error cap_names.h should be included from security/capability.c' +echo '#else' +echo "#if $NUMCAP != CAP_LAST_CAP + 1" +echo '#error mkcapnames.sh cannot collect capabilities correctly' +echo '#else' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("SYSFS_CAP_NAME_ENTRY(%s,%s);\n", tolower($2), $2); }' +echo +echo 'static struct attribute *capability_name_attrs[] = {' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("\t&%s_name_attr.attr,\n", tolower($2)); } END { print "\tNULL," }' +echo '};' + +echo +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("SYSFS_CAP_CODE_ENTRY(%s,%s);\n", tolower($2), $2); }' +echo +echo 'static struct attribute *capability_code_attrs[] = {' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("\t&%s_code_attr.attr,\n", tolower($2)); } END { print "\tNULL," }' +echo '};' + +echo '#endif' +echo '#endif' +echo '#endif'
security/Kconfig +9 -0
@@ -91,6 +91,15 @@ config SECURITY_FILE_CAPABILITIES If in doubt, answer N. +config SECURITY_CAPABILITIES_EXPORT + bool "Exporting capabilities kernel supported" + depends on SECURITY_CAPABILITIES && SYSFS + help + This enables to export any capabilities which are supported + in the running kernel. + + If you are unsure how to answer this question, answer Y. + config SECURITY_ROOTPLUG bool "Root Plug Support" depends on USB=y && SECURITY
security/Makefile +11 -0
@@ -18,3 +18,14 @@ obj-$(CONFIG_SECURITY_SELINUX) += selinux/built-in.o obj-$(CONFIG_SECURITY_SMACK) += commoncap.o smack/built-in.o obj-$(CONFIG_SECURITY_CAPABILITIES) += commoncap.o capability.o obj-$(CONFIG_SECURITY_ROOTPLUG) += commoncap.o root_plug.o + +ifeq ($(CONFIG_SECURITY_CAPABILITIES_EXPORT),y) +# cap_names.h contains the code/name pair of capabilities. +# It is generated using include/linux/capability.h automatically. +$(obj)/capability.o: $(obj)/cap_names.h +quiet_cmd_cap_names = CAPS $@ + cmd_cap_names = /bin/sh $(src)/../scripts/mkcapnames.sh > $@ +targets += cap_names.h +$(obj)/cap_names.h: $(src)/../scripts/mkcapnames.sh $(src)/../include/linux/capability.h FORCE + $(call if_changed,cap_names) +endif
security/capability.c +115 -0
127 lines not on this page · raw message
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Re: [PATCH] exporting capability code/name pairs (try #4)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
KaiGai,
Thanks for trying to accommodate me :-)
Kohei KaiGai wrote:
| In addition, Andrew suggested me to export these translation by symlinks | to reduce the number of invocation of system call.
Yes, I wanted to make use of readlink() instead of open()/read()/close() to access each unknown capability.
| However, current sysfs interface does not allows to create symlinks with | invalid indication.
:-(
| Thus, this patch exports them as regular files.
What about using symlinks for the name files and text content for the numeric ones? You could even drop the names/ and codes/ subdirectories too:
$ cat /sys/kernel/capability/20 cap_sys_pacct $ ls -l /sys/kernel/capability/cap_mknod lr--r--r-- 1 root root 64 Feb 8 08:26 cap_mknod -> 27 $ cat /sys/kernel/capability/names/cap_mknod cap_mknod
Cheers
Andrew
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFHrIfh+bHCR3gb8jsRAkueAKDYMu+so+YCJD9klNentiWlwZJXlQCgrzSa tWr1XM1nKcvST1ScAfO27j4=
=w5N/
-----END PGP SIGNATURE-----
Re: [PATCH] exporting capability code/name pairs (try #4)
Quoted 24 lines · Andrew G. Morgan
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1KaiGai,
Thanks for trying to accommodate me :-)
Kohei KaiGai wrote:
| In addition, Andrew suggested me to export these translation by symlinks | to reduce the number of invocation of system call.Yes, I wanted to make use of
readlink()instead of open()/read()/close() to access each unknown capability.| However, current sysfs interface does not allows to create symlinks with | invalid indication.
:-(
| Thus, this patch exports them as regular files.
What about using symlinks for the name files and text content for the numeric ones? You could even drop the names/ and codes/ subdirectories too:
Quoted 6 lines
$ cat /sys/kernel/capability/20 cap_sys_pacct $ ls -l /sys/kernel/capability/cap_mknod lr--r--r-- 1 root root 64 Feb 8 08:26 cap_mknod -> 27 $ cat /sys/kernel/capability/names/cap_mknod cap_mknod
Sysfs does not support to create symbolic links to regular files now.
The sysfs_create_link() is a function to create a symbolic link on sysfs. However, it requires two kobjects as its arguments. One is to specify its parent directory, the other is to specify the target of indirection. It means the indicated target have to be a directory.
At include/linux/sysfs.h:
int __must_check sysfs_create_link(struct kobject *kobj, struct kobject *target,
const char *name);
Please tell me, if I have any misunderstandings.
Thanks,
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Re: [PATCH] exporting capability code/name pairs (try #4)
In reply to Kohei KaiGaiQuoted 18 lines · Kohei KaiGai
[kaigai@saba ~]$ ls -R
/sys/kernel/capability//sys/kernel/capability/:
codes names version
/sys/kernel/capability/codes:0 10 12 14 16 18 2 21 23 25 27 29 30 32 4 6 8 1 11 13 15 17 19 20 22 24 26 28 3 31 33 5 7 9
/sys/kernel/capability/names:cap_audit_control cap_kill cap_net_raw cap_sys_nice cap_audit_write cap_lease cap_setfcap cap_sys_pacct cap_chown cap_linux_immutable cap_setgid cap_sys_ptrace cap_dac_override cap_mac_admin cap_setpcap cap_sys_rawio cap_dac_read_search cap_mac_override cap_setuid cap_sys_resource cap_fowner cap_mknod cap_sys_admin cap_sys_time cap_fsetid cap_net_admin cap_sys_boot cap_sys_tty_config cap_ipc_lock cap_net_bind_service cap_sys_chroot cap_ipc_owner cap_net_broadcast cap_sys_module
Quoted 7 lines
[kaigai@saba ~]$ cat
/sys/kernel/capability/codes/20cap_sys_pacct
[kaigai@saba ~]$ cat/sys/kernel/capability/names/cap_mknod27
[kaigai@saba ~]$
--------------------------------------------------------
Any comment please.
You don't like 1 (one) /proc/capabilities, why?
Re: [PATCH] exporting capability code/name pairs (try #4)
Quoted 27 lines · Alexey Dobriyan
Quoted 18 lines · Kohei KaiGai
[kaigai@saba ~]$ ls -R
/sys/kernel/capability//sys/kernel/capability/:
codes names version
/sys/kernel/capability/codes:0 10 12 14 16 18 2 21 23 25 27 29 30 32 4 6 8 1 11 13 15 17 19 20 22 24 26 28 3 31 33 5 7 9
/sys/kernel/capability/names:cap_audit_control cap_kill cap_net_raw cap_sys_nice cap_audit_write cap_lease cap_setfcap cap_sys_pacct cap_chown cap_linux_immutable cap_setgid cap_sys_ptrace cap_dac_override cap_mac_admin cap_setpcap cap_sys_rawio cap_dac_read_search cap_mac_override cap_setuid cap_sys_resource cap_fowner cap_mknod cap_sys_admin cap_sys_time cap_fsetid cap_net_admin cap_sys_boot cap_sys_tty_config cap_ipc_lock cap_net_bind_service cap_sys_chroot cap_ipc_owner cap_net_broadcast cap_sys_moduleQuoted 7 lines
[kaigai@saba ~]$ cat
/sys/kernel/capability/codes/20cap_sys_pacct
[kaigai@saba ~]$ cat/sys/kernel/capability/names/cap_mknod27
[kaigai@saba ~]$
--------------------------------------------------------
Any comment please.
Quoted 1 line
You don't like 1 (one)
/proc/capabilities, why?
I have no preference whether a single /proc/capabilities, or the current approach. However, this idea requires a bit more cost to lookup a capability not sequencially.
Thank,
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Re: [PATCH] exporting capability code/name pairs (try #4)
Quoted 30 lines · Kohei KaiGai
Quoted 29 lines · Alexey Dobriyan
Quoted 27 lines · Kohei KaiGai
[kaigai@saba ~]$ ls -R
/sys/kernel/capability//sys/kernel/capability/:
codes names version
/sys/kernel/capability/codes:0 10 12 14 16 18 2 21 23 25 27 29 30 32 4 6 8 1 11 13 15 17 19 20 22 24 26 28 3 31 33 5 7 9
/sys/kernel/capability/names:cap_audit_control cap_kill cap_net_raw cap_sys_nice cap_audit_write cap_lease cap_setfcap cap_sys_pacct cap_chown cap_linux_immutable cap_setgid cap_sys_ptrace cap_dac_override cap_mac_admin cap_setpcap cap_sys_rawio cap_dac_read_search cap_mac_override cap_setuid cap_sys_resource cap_fowner cap_mknod cap_sys_admin cap_sys_time cap_fsetid cap_net_admin cap_sys_boot cap_sys_tty_config cap_ipc_lock cap_net_bind_service cap_sys_chroot cap_ipc_owner cap_net_broadcast cap_sys_module[kaigai@saba ~]$ cat
/sys/kernel/capability/codes/20cap_sys_pacct
[kaigai@saba ~]$ cat/sys/kernel/capability/names/cap_mknod27
[kaigai@saba ~]$
--------------------------------------------------------
Any comment please.
Quoted 6 lines
Quoted 1 line
You don't like 1 (one)
/proc/capabilities, why?I have no preference whether a single
/proc/capabilities, or the current approach.
However, this idea requires a bit more cost to lookup a capability not sequencially.
And I'm sure far less memory wasted at runtime.
Also, adding config option for one file/directory seems ridiculous to me. And changelog completely fails to mention why it is useful to lookup capabilities by name and number -- CAP_SYS_* numbers are part of ABI, they won't change.
Re: [PATCH] exporting capability code/name pairs (try #4)
Quoted 32 lines · Alexey Dobriyan
Quoted 27 lines · Kohei KaiGai
Quoted 26 lines · Alexey Dobriyan
Quoted 25 lines · Kohei KaiGai
[kaigai@saba ~]$ ls -R
/sys/kernel/capability//sys/kernel/capability/:
codes names version
/sys/kernel/capability/codes:0 10 12 14 16 18 2 21 23 25 27 29 30 32 4 6 8 1 11 13 15 17 19 20 22 24 26 28 3 31 33 5 7 9
/sys/kernel/capability/names:cap_audit_control cap_kill cap_net_raw cap_sys_nice cap_audit_write cap_lease cap_setfcap cap_sys_pacct cap_chown cap_linux_immutable cap_setgid cap_sys_ptrace cap_dac_override cap_mac_admin cap_setpcap cap_sys_rawio cap_dac_read_search cap_mac_override cap_setuid cap_sys_resource cap_fowner cap_mknod cap_sys_admin cap_sys_time cap_fsetid cap_net_admin cap_sys_boot cap_sys_tty_config cap_ipc_lock cap_net_bind_service cap_sys_chroot cap_ipc_owner cap_net_broadcast cap_sys_module[kaigai@saba ~]$ cat
/sys/kernel/capability/codes/20cap_sys_pacct
[kaigai@saba ~]$ cat/sys/kernel/capability/names/cap_mknod27
[kaigai@saba ~]$
--------------------------------------------------------
Any comment please.Quoted 3 lines
Quoted 1 line
You don't like 1 (one)
/proc/capabilities, why?I have no preference whether a single
/proc/capabilities, or the current approach. However, this idea requires a bit more cost to lookup a capability not sequencially.
Quoted 6 lines
And I'm sure far less memory wasted at runtime.
Also, adding config option for one file/directory seems ridiculous to me. And changelog completely fails to mention why it is useful to lookup capabilities by name and number -- CAP_SYS_* numbers are part of ABI, they won't change.
The codes of capabilities are not removed/modified, but a new one may be added. In actually, two capabilities will be added at 2.6.25. If we don't have dynamic interface to obtain the list of capabilities, libcap built on older kernel cannot work enough on the latest one.
I'll add a description to make clear its purpose in the next patch. Please wait for a while.
Thanks,
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Re: [PATCH] exporting capability code/name pairs (try #4)
In reply to Kohei KaiGaiQuoted 110 lines · Kohei KaiGai
This patch enables to export code/name pair of capabilities supported on the running kernel, under the
/sys/kernel/capability. We can apply it onto the latest Linus's git tree.Changes from the previous version:
- I added "names/" ans "codes/" directories, and we can use them to lookup capability code or name non-sequentially.
In the previous version, we had to scan whole of entries to lookup capability name by its code.
(required by Andrew Morgan)
- I added an assertion when "mkcapname.sh" works incorrectly. (required by Serge E.Hallyn)In addition, Andrew suggested me to export these translation by symlinks to reduce the number of invocation of system call.
However, current sysfs interface does not allows to create symlinks with invalid indication.
Thus, this patch exports them as regular files.--------------------------------------------------------
[kaigai@saba ~]$ ls -R/sys/kernel/capability//sys/kernel/capability/:
codes names version
/sys/kernel/capability/codes:0 10 12 14 16 18 2 21 23 25 27 29 30 32 4 6 8 1 11 13 15 17 19 20 22 24 26 28 3 31 33 5 7 9
/sys/kernel/capability/names:cap_audit_control cap_kill cap_net_raw cap_sys_nice cap_audit_write cap_lease cap_setfcap cap_sys_pacct cap_chown cap_linux_immutable cap_setgid cap_sys_ptrace cap_dac_override cap_mac_admin cap_setpcap cap_sys_rawio cap_dac_read_search cap_mac_override cap_setuid cap_sys_resource cap_fowner cap_mknod cap_sys_admin cap_sys_time cap_fsetid cap_net_admin cap_sys_boot cap_sys_tty_config cap_ipc_lock cap_net_bind_service cap_sys_chroot cap_ipc_owner cap_net_broadcast cap_sys_module[kaigai@saba ~]$ cat
/sys/kernel/capability/codes/20cap_sys_pacct
[kaigai@saba ~]$ cat/sys/kernel/capability/names/cap_mknod27
[kaigai@saba ~]$
--------------------------------------------------------
Any comment please.Thanks,
Signed-off-by KaiGai Kohei <[email protected]>----
scripts/mkcapnames.sh | 44 +++++++++++++++++++ security/Kconfig | 9 ++++ security/Makefile | 11 +++++ security/capability.c | 115 +++++++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 179 insertions(+), 0 deletions(-)scripts/mkcapnames.sh +44
-0@@ -0,0 +1,44 @@ +#!/bin/sh + +# +# generate a cap_names.h file from include/linux/capability.h +# + +CAPHEAD="`dirname $0`/../include/linux/capability.h" +REGEXP='^#define CAP_[A-Z_]+[ ]+[0-9]+$' +NUMCAP=`cat "$CAPHEAD" | egrep -c "$REGEXP"` + +echo '#ifndef CAP_NAMES_H' +echo '#define CAP_NAMES_H' +echo +echo '/*' +echo ' * Do NOT edit this file directly.' +echo ' * This file is generated from include/linux/capability.h automatically' +echo ' */' +echo +echo '#if !defined(SYSFS_CAP_NAME_ENTRY) || !defined(SYSFS_CAP_CODE_ENTRY)' +echo '#error cap_names.h should be included from security/capability.c' +echo '#else' +echo "#if $NUMCAP != CAP_LAST_CAP + 1" +echo '#error mkcapnames.sh cannot collect capabilities correctly' +echo '#else' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("SYSFS_CAP_NAME_ENTRY(%s,%s);\n", tolower($2), $2); }' +echo +echo 'static struct attribute *capability_name_attrs[] = {' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("\t&%s_name_attr.attr,\n", tolower($2)); } END { print "\tNULL," }' +echo '};' + +echo +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("SYSFS_CAP_CODE_ENTRY(%s,%s);\n", tolower($2), $2); }' +echo +echo 'static struct attribute *capability_code_attrs[] = {' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("\t&%s_code_attr.attr,\n", tolower($2)); } END { print "\tNULL," }' +echo '};' + +echo '#endif' +echo '#endif' +echo '#endif'security/Kconfig +0
-0
security/Kconfig config SECURITY_FILE_CAPABILITIES · line 96
Quoted 6 lines
security/Kconfig +3
-0@@ -91,6 +91,15 @@ config SECURITY_FILE_CAPABILITIES If in doubt, answer N. +config SECURITY_CAPABILITIES_EXPORT + bool "Exporting capabilities kernel supported" + depends on SECURITY_CAPABILITIES && SYSFS
Oh no, we're being bit by this again... When SECURITY=n, capabilities are compiled in but SECURITY_CAPABILITIES=n.
Months ago I floated the following patch so we'd have a CONFIG variable to let us know whether commoncap is compiled in. You might want to use this and depend on CONFIG_COMMONCAP? (Though really I personally don't think you need your own config variable for this)
Other than that, this tested fine for me.
thanks,
-serge
Quoted 1 line
From
54c70ca7671750fe8986451fae91d42107d0ca90Mon Sep 17 00:00:00 2001
From: Serge E. Hallyn <[email protected]>
Date: Fri, 28 Sep 2007 10:33:33 -0500
Subject: [PATCH 1/2] capabilities: define CONFIG_COMMONCAP
currently the compilation of commoncap.c is determined through Makefile logic. So there is no single CONFIG variable which can be relied upon to know whether it will be compiled.
Define CONFIG_COMMONCAP to be true when lsm is not compiled in, or when the capability or rootplug modules are compiled. These are the cases when commoncap is currently compiled. Use this variable in security/Makefile to determine commoncap.c's compilation.
Apart from being a logic cleanup, this is needed by the upcoming cap_bset patch so that prctl can know whether PR_SET_BSET should be allowed.
--- security/Kconfig | 4 ++++ security/Makefile | 9 +++------ 2 files changed, 7 insertions(+), 6 deletions(-)
security/Kconfig +4 -0
@@ -103,6 +103,10 @@ config SECURITY_ROOTPLUG If you are unsure how to answer this question, answer N. +config COMMONCAP + bool + default !SECURITY || SECURITY_CAPABILITIES || SECURITY_ROOTPLUG + source security/selinux/Kconfig endmenu
security/Makefile +3 -6
@@ -5,14 +5,11 @@ obj-$(CONFIG_KEYS) += keys/ subdir-$(CONFIG_SECURITY_SELINUX) += selinux -# if we don't select a security model, use the default capabilities -ifneq ($(CONFIG_SECURITY),y) -obj-y += commoncap.o -endif +obj-$(CONFIG_COMMONCAP) += commoncap.o # Object file lists obj-$(CONFIG_SECURITY) += security.o dummy.o inode.o # Must precede capability.o in order to stack properly. obj-$(CONFIG_SECURITY_SELINUX) += selinux/built-in.o -obj-$(CONFIG_SECURITY_CAPABILITIES) += commoncap.o capability.o -obj-$(CONFIG_SECURITY_ROOTPLUG) += commoncap.o root_plug.o +obj-$(CONFIG_SECURITY_CAPABILITIES) += capability.o +obj-$(CONFIG_SECURITY_ROOTPLUG) += root_plug.o
Signature · 1 line
1.5.1.1.GIT
Re: [PATCH] exporting capability code/name pairs (try #4)
Quoted 16 lines · Serge E. Hallyn
security/Kconfig config SECURITY_FILE_CAPABILITIES · line 96
Quoted 11 lines · Kohei KaiGai
security/Kconfig +3
-0@@ -91,6 +91,15 @@ config SECURITY_FILE_CAPABILITIES If in doubt, answer N. +config SECURITY_CAPABILITIES_EXPORT + bool "Exporting capabilities kernel supported" + depends on SECURITY_CAPABILITIES && SYSFSOh no, we're being bit by this again... When SECURITY=n, capabilities are compiled in but SECURITY_CAPABILITIES=n.
Quoted 4 lines
Months ago I floated the following patch so we'd have a CONFIG variable to let us know whether commoncap is compiled in. You might want to use this and depend on
CONFIG_COMMONCAP? (Though really I personally don't think you need your own config variable for this)
I also think its own config variable is not necessary to turn on/off exporting the list of capabilities in actually.
Do you want this feture to be moved into security/commoncap.c and enabled unconditionally? I can agree this suggestion.
Is there any complaint for this idea?
Thanks,
Quoted 68 lines
Other than that, this tested fine for me.
thanks,
-sergeQuoted 1 line
From
54c70ca7671750fe8986451fae91d42107d0ca90Mon Sep 17 00:00:00 2001From: Serge E. Hallyn <[email protected]>
Date: Fri, 28 Sep 2007 10:33:33 -0500
Subject: [PATCH 1/2] capabilities: defineCONFIG_COMMONCAPcurrently the compilation of
commoncap.cis determined throughMakefilelogic. So there is no single CONFIG variable which can be relied upon to know whether it will be compiled.Define
CONFIG_COMMONCAPto be true when lsm is not compiled in, or when the capability or rootplug modules are compiled. These are the cases when commoncap is currently compiled. Use this variable insecurity/Makefileto determine commoncap.c's compilation.Apart from being a logic cleanup, this is needed by the upcoming
cap_bsetpatch so that prctl can know whetherPR_SET_BSETshould be allowed.Signed-off-by Serge E. Hallyn <[email protected]>--- security/Kconfig | 4 ++++ security/Makefile | 9 +++------ 2 files changed, 7 insertions(+), 6 deletions(-)security/Kconfig +4
-0@@ -103,6 +103,10 @@ config SECURITY_ROOTPLUG If you are unsure how to answer this question, answer N. +config COMMONCAP + bool + default !SECURITY || SECURITY_CAPABILITIES || SECURITY_ROOTPLUG + source security/selinux/Kconfig endmenusecurity/Makefile +3
-6@@ -5,14 +5,11 @@ obj-$(CONFIG_KEYS) += keys/ subdir-$(CONFIG_SECURITY_SELINUX) += selinux -# if we don't select a security model, use the default capabilities -ifneq ($(CONFIG_SECURITY),y) -obj-y += commoncap.o -endif +obj-$(CONFIG_COMMONCAP) += commoncap.o # Object file lists obj-$(CONFIG_SECURITY) += security.o dummy.o inode.o # Must precede capability.o in order to stack properly. obj-$(CONFIG_SECURITY_SELINUX) += selinux/built-in.o -obj-$(CONFIG_SECURITY_CAPABILITIES) += commoncap.o capability.o -obj-$(CONFIG_SECURITY_ROOTPLUG) += commoncap.o root_plug.o +obj-$(CONFIG_SECURITY_CAPABILITIES) += capability.o +obj-$(CONFIG_SECURITY_ROOTPLUG) += root_plug.o
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
PATCH 1/1 exporting capability code/name pairs (try #5)
This patch enables to export code/name of capabilities supported on the running kernel.
A newer kernel sometimes adds new capabilities, like CAP_MAC_ADMIN at 2.6.25. However, we have no interface to disclose what capabilities are supported on this kernel. Thus, we have to maintain libcap version in appropriate one synchronously.
This patch enables libcap to collect the list of capabilities on run time, and provide them for users.
It helps to improve portability of library.
It exports these information as regular files under /sys/kernel/capability. The numeric node exports its name, the symbolic node exports its code.
Please consider to put this patch on the queue of 2.6.25.
Thanks,
===================================================
[kaigai@saba ~]$ ls -R /sys/kernel/capability//sys/kernel/capability/:
codes names version
/sys/kernel/capability/codes:
0 10 12 14 16 18 2 21 23 25 27 29 30 32 4 6 8 1 11 13 15 17 19 20 22 24 26 28 3 31 33 5 7 9
/sys/kernel/capability/names:
cap_audit_control cap_kill cap_net_raw cap_sys_nice cap_audit_write cap_lease cap_setfcap cap_sys_pacct cap_chown cap_linux_immutable cap_setgid cap_sys_ptrace cap_dac_override cap_mac_admin cap_setpcap cap_sys_rawio cap_dac_read_search cap_mac_override cap_setuid cap_sys_resource cap_fowner cap_mknod cap_sys_admin cap_sys_time cap_fsetid cap_net_admin cap_sys_boot cap_sys_tty_config cap_ipc_lock cap_net_bind_service cap_sys_chroot cap_ipc_owner cap_net_broadcast cap_sys_module
[kaigai@saba ~]$ cat /sys/kernel/capability/version 0x20071026
[kaigai@saba ~]$ cat /sys/kernel/capability/codes/30 cap_audit_control
[kaigai@saba ~]$ cat /sys/kernel/capability/names/cap_sys_pacct 20
[kaigai@saba ~]$
===================================================
--
scripts/mkcapnames.sh | 44 +++++++++++++++++++ security/Makefile | 9 ++++ security/commoncap.c | 112 +++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 165 insertions(+), 0 deletions(-)
scripts/mkcapnames.sh +44 -0
@@ -0,0 +1,44 @@ +#!/bin/sh + +# +# generate a cap_names.h file from include/linux/capability.h +# + +CAPHEAD="`dirname $0`/../include/linux/capability.h" +REGEXP='^#define CAP_[A-Z_]+[ ]+[0-9]+$' +NUMCAP=`cat "$CAPHEAD" | egrep -c "$REGEXP"` + +echo '#ifndef CAP_NAMES_H' +echo '#define CAP_NAMES_H' +echo +echo '/*' +echo ' * Do NOT edit this file directly.' +echo ' * This file is generated from include/linux/capability.h automatically' +echo ' */' +echo +echo '#if !defined(SYSFS_CAP_NAME_ENTRY) || !defined(SYSFS_CAP_CODE_ENTRY)' +echo '#error cap_names.h should be included from security/capability.c' +echo '#else' +echo "#if $NUMCAP != CAP_LAST_CAP + 1" +echo '#error mkcapnames.sh cannot collect capabilities correctly' +echo '#else' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("SYSFS_CAP_NAME_ENTRY(%s,%s);\n", tolower($2), $2); }' +echo +echo 'static struct attribute *capability_name_attrs[] = {' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("\t&%s_name_attr.attr,\n", tolower($2)); } END { print "\tNULL," }' +echo '};' + +echo +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("SYSFS_CAP_CODE_ENTRY(%s,%s);\n", tolower($2), $2); }' +echo +echo 'static struct attribute *capability_code_attrs[] = {' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("\t&%s_code_attr.attr,\n", tolower($2)); } END { print "\tNULL," }' +echo '};' + +echo '#endif' +echo '#endif' +echo '#endif'
security/Makefile +9 -0
@@ -18,3 +18,12 @@ obj-$(CONFIG_SECURITY_SELINUX) += selinux/built-in.o obj-$(CONFIG_SECURITY_SMACK) += commoncap.o smack/built-in.o obj-$(CONFIG_SECURITY_CAPABILITIES) += commoncap.o capability.o obj-$(CONFIG_SECURITY_ROOTPLUG) += commoncap.o root_plug.o + +# cap_names.h contains the code/name pair of capabilities. +# It is generated using include/linux/capability.h automatically. +$(obj)/commoncap.o: $(obj)/cap_names.h +quiet_cmd_cap_names = CAPS $@ + cmd_cap_names = /bin/sh $(src)/../scripts/mkcapnames.sh > $@ +targets += cap_names.h +$(obj)/cap_names.h: $(src)/../scripts/mkcapnames.sh $(src)/../include/linux/capability.h FORCE + $(call if_changed,cap_names)
security/commoncap.c +112 -0
121 lines not on this page · raw message
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Re: [PATCH] exporting capability code/name pairs (try #5)
Kohei KaiGai wrote:
<...snip...>
Quoted 23 lines
security/commoncap.c +23
-0+static int __init capability_export_names (void ) +{ +/* make /sys/kernel/capability */ + capability_kobj =kobject_create_and_add ("capability" , kernel_kobj); +if (!capability_kobj) + goto error0; + +/* make /sys/kernel/capability/names */ +if (sysfs_create_group (capability_kobj, + &capability_name_attr_group)) + goto error1; + +/* make /sys/kernel/capability/codes */ +if (sysfs_create_group (capability_kobj, + &capability_code_attr_group)) + goto error2; + +if (sysfs_create_file (capability_kobj, + &cap_version_attr.attr)) + goto error3; + +return 0 ; +
security/commoncap.c int cap_vm_enough_memory(struct mm_struct *mm, long pages) · line 749
Quoted 10 lines
security/commoncap.c +10
-0+error3: +sysfs_remove_group (capability_kobj, &capability_code_attr_group); +error2: +sysfs_remove_group (capability_kobj, &capability_name_attr_group); +error1: +kobject_put (capability_kobj); +error0: +printk (KERN_ERR "Unable to export capabilities\n" ); + +return 0 ;
Should return -EFXXX ..
Quoted 3 lines
(quoted diff) +2
-0+} +__initcall(capability_export_names);
Re: [PATCH] exporting capability code/name pairs (try #5.1)
Li Zefan wrote:
- snip -
Quoted 8 lines
Review
Quoted 6 lines
(quoted diff) +6
-0+error1: + kobject_put(capability_kobj); +error0: + printk(KERN_ERR "Unable to export capabilities\n"); + + return 0;Should return
-EFXXX..
Oops,
I fixed it as follows. Thanks for your pointed out.
--------
This patch enables to export code/name of capabilities supported on the running kernel.
A newer kernel sometimes adds new capabilities, like CAP_MAC_ADMIN at 2.6.25. However, we have no interface to disclose what capabilities are supported on this kernel. Thus, we have to maintain libcap version in appropriate one synchronously.
This patch enables libcap to collect the list of capabilities on run time, and provide them for users.
It helps to improve portability of library.
It exports these information as regular files under /sys/kernel/capability. The numeric node exports its name, the symbolic node exports its code.
Please consider to put this patch on the queue of 2.6.25.
Thanks,
===================================================
[kaigai@saba ~]$ ls -R /sys/kernel/capability//sys/kernel/capability/:
codes names version
/sys/kernel/capability/codes:
0 10 12 14 16 18 2 21 23 25 27 29 30 32 4 6 8 1 11 13 15 17 19 20 22 24 26 28 3 31 33 5 7 9
/sys/kernel/capability/names:
cap_audit_control cap_kill cap_net_raw cap_sys_nice cap_audit_write cap_lease cap_setfcap cap_sys_pacct cap_chown cap_linux_immutable cap_setgid cap_sys_ptrace cap_dac_override cap_mac_admin cap_setpcap cap_sys_rawio cap_dac_read_search cap_mac_override cap_setuid cap_sys_resource cap_fowner cap_mknod cap_sys_admin cap_sys_time cap_fsetid cap_net_admin cap_sys_boot cap_sys_tty_config cap_ipc_lock cap_net_bind_service cap_sys_chroot cap_ipc_owner cap_net_broadcast cap_sys_module
[kaigai@saba ~]$ cat /sys/kernel/capability/version 0x20071026
[kaigai@saba ~]$ cat /sys/kernel/capability/codes/30 cap_audit_control
[kaigai@saba ~]$ cat /sys/kernel/capability/names/cap_sys_pacct 20
[kaigai@saba ~]$
===================================================
--
scripts/mkcapnames.sh | 44 ++++++++++++++++++ security/Makefile | 9 ++++ security/commoncap.c | 118 +++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 171 insertions(+), 0 deletions(-)
scripts/mkcapnames.sh +44 -0
@@ -0,0 +1,44 @@ +#!/bin/sh + +# +# generate a cap_names.h file from include/linux/capability.h +# + +CAPHEAD="`dirname $0`/../include/linux/capability.h" +REGEXP='^#define CAP_[A-Z_]+[ ]+[0-9]+$' +NUMCAP=`cat "$CAPHEAD" | egrep -c "$REGEXP"` + +echo '#ifndef CAP_NAMES_H' +echo '#define CAP_NAMES_H' +echo +echo '/*' +echo ' * Do NOT edit this file directly.' +echo ' * This file is generated from include/linux/capability.h automatically' +echo ' */' +echo +echo '#if !defined(SYSFS_CAP_NAME_ENTRY) || !defined(SYSFS_CAP_CODE_ENTRY)' +echo '#error cap_names.h should be included from security/capability.c' +echo '#else' +echo "#if $NUMCAP != CAP_LAST_CAP + 1" +echo '#error mkcapnames.sh cannot collect capabilities correctly' +echo '#else' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("SYSFS_CAP_NAME_ENTRY(%s,%s);\n", tolower($2), $2); }' +echo +echo 'static struct attribute *capability_name_attrs[] = {' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("\t&%s_name_attr.attr,\n", tolower($2)); } END { print "\tNULL," }' +echo '};' + +echo +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("SYSFS_CAP_CODE_ENTRY(%s,%s);\n", tolower($2), $2); }' +echo +echo 'static struct attribute *capability_code_attrs[] = {' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("\t&%s_code_attr.attr,\n", tolower($2)); } END { print "\tNULL," }' +echo '};' + +echo '#endif' +echo '#endif' +echo '#endif'
security/Makefile +9 -0
@@ -18,3 +18,12 @@ obj-$(CONFIG_SECURITY_SELINUX) += selinux/built-in.o obj-$(CONFIG_SECURITY_SMACK) += commoncap.o smack/built-in.o obj-$(CONFIG_SECURITY_CAPABILITIES) += commoncap.o capability.o obj-$(CONFIG_SECURITY_ROOTPLUG) += commoncap.o root_plug.o + +# cap_names.h contains the code/name pair of capabilities. +# It is generated using include/linux/capability.h automatically. +$(obj)/commoncap.o: $(obj)/cap_names.h +quiet_cmd_cap_names = CAPS $@ + cmd_cap_names = /bin/sh $(src)/../scripts/mkcapnames.sh > $@ +targets += cap_names.h +$(obj)/cap_names.h: $(src)/../scripts/mkcapnames.sh $(src)/../include/linux/capability.h FORCE + $(call if_changed,cap_names)
security/commoncap.c +118 -0
127 lines not on this page · raw message
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Re: [PATCH] exporting capability code/name pairs (try #5.1)
Quoted 23 lines · Kohei KaiGai
Li Zefan wrote:
- snip -Quoted 8 lines
security/commoncap.c int cap_vm_enough_memory(struct mm_struct *mm, long pages)
Quoted 6 lines
security/commoncap.c +6
-0+error1: +kobject_put (capability_kobj); +error0: +printk (KERN_ERR "Unable to export capabilities\n" ); + +return 0 ;Should return
-EFXXX..Oops,
I fixed it as follows. Thanks for your pointed out.--------
This patch enables to export code/name of capabilities supported on the running kernel.A newer kernel sometimes adds new capabilities, like
CAP_MAC_ADMINat 2.6.25. However, we have no interface to disclose what capabilities are supported on this kernel. Thus, we have to maintain libcap version in appropriate one synchronously.
Quoted 8 lines
This patch enables libcap to collect the list of capabilities on run time, and provide them for users.
It helps to improve portability of library.It exports these information as regular files under
/sys/kernel/capability. The numeric node exports its name, the symbolic node exports its code.Please consider to put this patch on the queue of 2.6.25.
Looks good, except don't you need to put the code in commoncap.c under a #ifdef SYSFS?
thanks,
-serge
Quoted 244 lines
Thanks,
===================================================
[kaigai@saba ~]$ ls -R/sys/kernel/capability//sys/kernel/capability/:
codes names version
/sys/kernel/capability/codes:0 10 12 14 16 18 2 21 23 25 27 29 30 32 4 6 8 1 11 13 15 17 19 20 22 24 26 28 3 31 33 5 7 9
/sys/kernel/capability/names:cap_audit_control cap_kill cap_net_raw cap_sys_nice cap_audit_write cap_lease cap_setfcap cap_sys_pacct cap_chown cap_linux_immutable cap_setgid cap_sys_ptrace cap_dac_override cap_mac_admin cap_setpcap cap_sys_rawio cap_dac_read_search cap_mac_override cap_setuid cap_sys_resource cap_fowner cap_mknod cap_sys_admin cap_sys_time cap_fsetid cap_net_admin cap_sys_boot cap_sys_tty_config cap_ipc_lock cap_net_bind_service cap_sys_chroot cap_ipc_owner cap_net_broadcast cap_sys_module[kaigai@saba ~]$ cat
/sys/kernel/capability/version0x20071026
[kaigai@saba ~]$ cat/sys/kernel/capability/codes/30cap_audit_control
[kaigai@saba ~]$ cat/sys/kernel/capability/names/cap_sys_pacct20
[kaigai@saba ~]$
===================================================Signed-off-by KaiGai Kohei <[email protected]>--
scripts/mkcapnames.sh | 44 ++++++++++++++++++ security/Makefile | 9 ++++ security/commoncap.c | 118 +++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 171 insertions(+), 0 deletions(-)scripts/mkcapnames.sh +44
-0@@ -0,0 +1,44 @@ +#!/bin/sh + +# +# generate a cap_names.h file from include/linux/capability.h +# + +CAPHEAD="`dirname $0`/../include/linux/capability.h" +REGEXP='^#define CAP_[A-Z_]+[ ]+[0-9]+$' +NUMCAP=`cat "$CAPHEAD" | egrep -c "$REGEXP"` + +echo '#ifndef CAP_NAMES_H' +echo '#define CAP_NAMES_H' +echo +echo '/*' +echo ' * Do NOT edit this file directly.' +echo ' * This file is generated from include/linux/capability.h automatically' +echo ' */' +echo +echo '#if !defined(SYSFS_CAP_NAME_ENTRY) || !defined(SYSFS_CAP_CODE_ENTRY)' +echo '#error cap_names.h should be included from security/capability.c' +echo '#else' +echo "#if $NUMCAP != CAP_LAST_CAP + 1" +echo '#error mkcapnames.sh cannot collect capabilities correctly' +echo '#else' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("SYSFS_CAP_NAME_ENTRY(%s,%s);\n", tolower($2), $2); }' +echo +echo 'static struct attribute *capability_name_attrs[] = {' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("\t&%s_name_attr.attr,\n", tolower($2)); } END { print "\tNULL," }' +echo '};' + +echo +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("SYSFS_CAP_CODE_ENTRY(%s,%s);\n", tolower($2), $2); }' +echo +echo 'static struct attribute *capability_code_attrs[] = {' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("\t&%s_code_attr.attr,\n", tolower($2)); } END { print "\tNULL," }' +echo '};' + +echo '#endif' +echo '#endif' +echo '#endif'security/Makefile +9
-0@@ -18,3 +18,12 @@ obj-$(CONFIG_SECURITY_SELINUX) += selinux/built-in.o obj-$(CONFIG_SECURITY_SMACK) += commoncap.o smack/built-in.o obj-$(CONFIG_SECURITY_CAPABILITIES) += commoncap.o capability.o obj-$(CONFIG_SECURITY_ROOTPLUG) += commoncap.o root_plug.o + +# cap_names.h contains the code/name pair of capabilities. +# It is generated using include/linux/capability.h automatically. +$(obj)/commoncap.o: $(obj)/cap_names.h +quiet_cmd_cap_names = CAPS $@ + cmd_cap_names = /bin/sh $(src)/../scripts/mkcapnames.sh > $@ +targets += cap_names.h +$(obj)/cap_names.h: $(src)/../scripts/mkcapnames.sh $(src)/../include/linux/capability.h FORCE + $(call if_changed,cap_names)security/commoncap.c +118
-0@@ -24,6 +24,8 @@#include <linux/hugetlb.h> #include <linux/mount.h> #include <linux/sched.h> +#include <linux/kobject.h> +#include <linux/sysfs.h> /* Global security state */ @@ -637,3 +639,119 @@ int cap_vm_enough_memory(struct mm_struct *mm, long pages)return __vm_enough_memory (mm, pages, cap_sys_admin); } +/* +* Export the list of capabilities on /sys/kernel/capability +*/ +static struct kobject *capability_kobj; + +struct capability_attribute { +struct attribute attr; +ssize_t (*show)(struct kobject *kobj, +struct capability_attribute *attr, +char *buffer); +ssize_t (*store)(struct kobject *kobj, +struct capability_attribute *attr, +const char *buffer,size_t count); +union { +int code; +char *name; + } c; +}; + +static ssize_t capability_name_show (struct kobject *kobj, +struct capability_attribute *attr, +char *buffer) +{ +return scnprintf (buffer,PAGE_SIZE ,"%d\n" , attr->c.code); +} + +static ssize_t capability_code_show (struct kobject *kobj, +struct capability_attribute *attr, +char *buffer) +{ +return scnprintf (buffer,PAGE_SIZE ,"%s\n" , attr->c.name); +} + +static ssize_t capability_version_show (struct kobject *kobj, +struct capability_attribute *attr, +char *buffer) +{ +return scnprintf (buffer,PAGE_SIZE ,"0x%08x\n" , + _LINUX_CAPABILITY_VERSION); +} + +#define SYSFS_CAP_NAME_ENTRY (_name,_code) \ + static struct capability_attribute _name##_name_attr = { \ + .attr = { .name = __stringify(_name), .mode = 0444 }, \ + .show = capability_name_show, \ + .c.code = (_code), \ + } + +#define SYSFS_CAP_CODE_ENTRY (_name,_code) \ + static struct capability_attribute _name##_code_attr = { \ + .attr = { .name = __stringify(_code), .mode = 0444 }, \ + .show = capability_code_show, \ + .c.name = __stringify(_name), \ + } +/* +* capability_attrs[] is generated automatically by scripts/mkcapnames.sh +* This script parses include/linux/capability.h +*/ +#include "cap_names.h" + +static struct attribute_group capability_name_attr_group = { + .name ="names" , + .attrs = capability_name_attrs, +}; + +static struct attribute_group capability_code_attr_group = { + .name ="codes" , + .attrs = capability_code_attrs, +}; + +static struct capability_attribute cap_version_attr = { + .attr = { .name ="version" , .mode =0444 }, + .show = capability_version_show, +}; + +static int __init capability_export_names (void ) +{ +int rc = -ENOMEM ; + +/* make /sys/kernel/capability */ + capability_kobj =kobject_create_and_add ("capability" , kernel_kobj); +if (!capability_kobj) + goto error0; + +/* make /sys/kernel/capability/names */ + rc =sysfs_create_group (capability_kobj, + &capability_name_attr_group); +if (rc) + goto error1; + +/* make /sys/kernel/capability/codes */ + rc =sysfs_create_group (capability_kobj, + &capability_code_attr_group); +if (rc) + goto error2; + +/* make /sys/kernel/capability/version */ + rc =sysfs_create_file (capability_kobj, + &cap_version_attr.attr); +if (rc) + goto error3; + +return 0 ; + +error3: +sysfs_remove_group (capability_kobj, &capability_code_attr_group); +error2: +sysfs_remove_group (capability_kobj, &capability_name_attr_group); +error1: +kobject_put (capability_kobj); +error0: +printk (KERN_ERR "Unable to export capabilities\n" ); + +return rc; +} +__initcall (capability_export_names);Signature · 7 lines
-- OSS Platform Development Division, NEC KaiGai Kohei <[email protected]> - To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] exporting capability code/name pairs (try #5.1)
Quoted 31 lines · Serge E. Hallyn
Quoted 30 lines · Kohei KaiGai
Li Zefan wrote:
- snip -Quoted 8 lines
security/commoncap.c int cap_vm_enough_memory(struct mm_struct *mm, long pages)
Quoted 6 lines
security/commoncap.c +6
-0+error1: +kobject_put (capability_kobj); +error0: +printk (KERN_ERR "Unable to export capabilities\n" ); + +return 0 ;Should return
-EFXXX..Oops,
I fixed it as follows. Thanks for your pointed out.--------
This patch enables to export code/name of capabilities supported on the running kernel.A newer kernel sometimes adds new capabilities, like
CAP_MAC_ADMINat 2.6.25. However, we have no interface to disclose what capabilities are supported on this kernel. Thus, we have to maintain libcap version in appropriate one synchronously.This patch enables libcap to collect the list of capabilities on run time, and provide them for users.
It helps to improve portability of library.It exports these information as regular files under
/sys/kernel/capability. The numeric node exports its name, the symbolic node exports its code.
Quoted 37 lines
Quoted 1 line
Please consider to put this patch on the queue of 2.6.25.
Looks good, except don't you need to put the code in
commoncap.cunder a #ifdef SYSFS?thanks,
-sergeQuoted 29 lines
Thanks,
===================================================
[kaigai@saba ~]$ ls -R/sys/kernel/capability//sys/kernel/capability/:
codes names version
/sys/kernel/capability/codes:0 10 12 14 16 18 2 21 23 25 27 29 30 32 4 6 8 1 11 13 15 17 19 20 22 24 26 28 3 31 33 5 7 9
/sys/kernel/capability/names:cap_audit_control cap_kill cap_net_raw cap_sys_nice cap_audit_write cap_lease cap_setfcap cap_sys_pacct cap_chown cap_linux_immutable cap_setgid cap_sys_ptrace cap_dac_override cap_mac_admin cap_setpcap cap_sys_rawio cap_dac_read_search cap_mac_override cap_setuid cap_sys_resource cap_fowner cap_mknod cap_sys_admin cap_sys_time cap_fsetid cap_net_admin cap_sys_boot cap_sys_tty_config cap_ipc_lock cap_net_bind_service cap_sys_chroot cap_ipc_owner cap_net_broadcast cap_sys_module[kaigai@saba ~]$ cat
/sys/kernel/capability/version0x20071026
[kaigai@saba ~]$ cat/sys/kernel/capability/codes/30cap_audit_control
[kaigai@saba ~]$ cat/sys/kernel/capability/names/cap_sys_pacct20
[kaigai@saba ~]$
===================================================
As you are adding new sysfs entries, please also add the needed Documentation/ABI/ entries as well.
Also, this code can be cleaned up a lot by just using the basic kobject attributes, and not rolling your own types here.
thanks,
greg k-h
Re: [PATCH] exporting capability code/name pairs (try #5.1)
Quoted 14 lines · Greg KH
Quoted 13 lines · Serge E. Hallyn
Quoted 13 lines
--------
This patch enables to export code/name of capabilities supported on the running kernel.A newer kernel sometimes adds new capabilities, like
CAP_MAC_ADMINat 2.6.25. However, we have no interface to disclose what capabilities are supported on this kernel. Thus, we have to maintain libcap version in appropriate one synchronously.This patch enables libcap to collect the list of capabilities on run time, and provide them for users.
It helps to improve portability of library.
Quoted 6 lines
Quoted 6 lines
Quoted 4 lines
It exports these information as regular files under
/sys/kernel/capability. The numeric node exports its name, the symbolic node exports its code.Please consider to put this patch on the queue of 2.6.25.
Looks good, except don't you need to put the code in
commoncap.cunder a #ifdef SYSFS?
Fair enough.
I added the #ifdef - #endif block in this patch.
Quoted 28 lines
Quoted 19 lines
Quoted 19 lines
===================================================
[kaigai@saba ~]$ ls -R/sys/kernel/capability//sys/kernel/capability/:
codes names version
/sys/kernel/capability/codes:0 10 12 14 16 18 2 21 23 25 27 29 30 32 4 6 8 1 11 13 15 17 19 20 22 24 26 28 3 31 33 5 7 9
/sys/kernel/capability/names:cap_audit_control cap_kill cap_net_raw cap_sys_nice cap_audit_write cap_lease cap_setfcap cap_sys_pacct cap_chown cap_linux_immutable cap_setgid cap_sys_ptrace cap_dac_override cap_mac_admin cap_setpcap cap_sys_rawio cap_dac_read_search cap_mac_override cap_setuid cap_sys_resource cap_fowner cap_mknod cap_sys_admin cap_sys_time cap_fsetid cap_net_admin cap_sys_boot cap_sys_tty_config cap_ipc_lock cap_net_bind_service cap_sys_chroot cap_ipc_owner cap_net_broadcast cap_sys_moduleQuoted 8 lines
Quoted 8 lines
[kaigai@saba ~]$ cat
/sys/kernel/capability/version0x20071026
[kaigai@saba ~]$ cat/sys/kernel/capability/codes/30cap_audit_control
[kaigai@saba ~]$ cat/sys/kernel/capability/names/cap_sys_pacct20
[kaigai@saba ~]$
===================================================
Quoted 2 lines
As you are adding new sysfs entries, please also add the needed
Documentation/ABI/entries as well.
OK, I'll add a short description at Documentation/ABI/sysfs-kernel-capability .
Quoted 2 lines
Also, this code can be cleaned up a lot by just using the basic kobject attributes, and not rolling your own types here.
I replaced my own defined capability_attribute by kobj_attribute.
It made the patch cleaned up, however, it also impossible to share a single _show() method instance, because kobj_attribute does not have any private member. Is there any reason why kobj_attribute does not have "void *private;"?
Thanks,
--
Documentation/ABI/testing/sysfs-kernel-capability | 23 +++++ scripts/mkcapnames.sh | 44 +++++++++ security/Makefile | 9 ++ security/commoncap.c | 102 +++++++++++++++++++++ 4 files changed, 178 insertions(+), 0 deletions(-)
Documentation/ABI/testing/sysfs-kernel-capability +23 -0
@@ -0,0 +1,23 @@ +What: /sys/kernel/capability +Date: Feb 2008 +Contact: KaiGai Kohei <[email protected]> +Description: + The entries under /sys/kernel/capability are used to export + the list of capabilities the running kernel supported. + + - /sys/kernel/capability/version + returns the most preferable version number for the + running kernel. + e.g) $ cat /sys/kernel/capability/version + 0x20071026 + + - /sys/kernel/capability/code/<numerical representation> + returns its symbolic representation, on reading. + e.g) $ cat /sys/kernel/capability/codes/30 + cap_audit_control + + - /sys/kernel/capability/name/<symbolic representation> + returns its numerical representation, on reading. + e.g) $ cat /sys/kernel/capability/names/cap_sys_pacct + 20 +
scripts/mkcapnames.sh +44 -0
44 lines not on this page · raw message
security/Makefile +9 -0
@@ -18,3 +18,12 @@ obj-$(CONFIG_SECURITY_SELINUX) += selinux/built-in.o obj-$(CONFIG_SECURITY_SMACK) += commoncap.o smack/built-in.o obj-$(CONFIG_SECURITY_CAPABILITIES) += commoncap.o capability.o obj-$(CONFIG_SECURITY_ROOTPLUG) += commoncap.o root_plug.o + +# cap_names.h contains the code/name pair of capabilities. +# It is generated using include/linux/capability.h automatically. +$(obj)/commoncap.o: $(obj)/cap_names.h +quiet_cmd_cap_names = CAPS $@ + cmd_cap_names = /bin/sh $(src)/../scripts/mkcapnames.sh > $@ +targets += cap_names.h +$(obj)/cap_names.h: $(src)/../scripts/mkcapnames.sh $(src)/../include/linux/capability.h FORCE + $(call if_changed,cap_names)
security/commoncap.c +102 -0
111 lines not on this page · raw message
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Re: [PATCH] exporting capability code/name pairs (try #5.1)
Quoted 18 lines · Kohei KaiGai
Quoted 17 lines · Greg KH
Quoted 16 lines · Serge E. Hallyn
Quoted 16 lines
--------
This patch enables to export code/name of capabilities supported on the running kernel.A newer kernel sometimes adds new capabilities, like
CAP_MAC_ADMINat 2.6.25. However, we have no interface to disclose what capabilities are supported on this kernel. Thus, we have to maintain libcap version in appropriate one synchronously.This patch enables libcap to collect the list of capabilities on run time, and provide them for users.
It helps to improve portability of library.It exports these information as regular files under
/sys/kernel/capability. The numeric node exports its name, the symbolic node exports its code.
Quoted 6 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
Please consider to put this patch on the queue of 2.6.25.
Looks good, except don't you need to put the code in
commoncap.cunder a #ifdef SYSFS?Fair enough.
I added the #ifdef - #endif block in this patch.
Not needed, if SYSFS is not build in, all of that code pretty much compiles away to nothing. So you can drop that.
Quoted 29 lines
Quoted 29 lines
Quoted 28 lines
Quoted 28 lines
===================================================
[kaigai@saba ~]$ ls -R/sys/kernel/capability//sys/kernel/capability/:
codes names version
/sys/kernel/capability/codes:0 10 12 14 16 18 2 21 23 25 27 29 30 32 4 6 8 1 11 13 15 17 19 20 22 24 26 28 3 31 33 5 7 9
/sys/kernel/capability/names:cap_audit_control cap_kill cap_net_raw cap_sys_nice cap_audit_write cap_lease cap_setfcap cap_sys_pacct cap_chown cap_linux_immutable cap_setgid cap_sys_ptrace cap_dac_override cap_mac_admin cap_setpcap cap_sys_rawio cap_dac_read_search cap_mac_override cap_setuid cap_sys_resource cap_fowner cap_mknod cap_sys_admin cap_sys_time cap_fsetid cap_net_admin cap_sys_boot cap_sys_tty_config cap_ipc_lock cap_net_bind_service cap_sys_chroot cap_ipc_owner cap_net_broadcast cap_sys_module[kaigai@saba ~]$ cat
/sys/kernel/capability/version0x20071026
[kaigai@saba ~]$ cat/sys/kernel/capability/codes/30cap_audit_control
[kaigai@saba ~]$ cat/sys/kernel/capability/names/cap_sys_pacct20
[kaigai@saba ~]$
===================================================
Quoted 4 lines
Quoted 2 lines
As you are adding new sysfs entries, please also add the needed
Documentation/ABI/entries as well.OK, I'll add a short description at
Documentation/ABI/sysfs-kernel-capability.
Thank you.
Quoted 8 lines
Quoted 2 lines
Also, this code can be cleaned up a lot by just using the basic kobject attributes, and not rolling your own types here.
I replaced my own defined
capability_attributebykobj_attribute.It made the patch cleaned up, however, it also impossible to share a single
_show()method instance, becausekobj_attributedoes not have any private member. Is there any reason whykobj_attributedoes not have "void *private;"?
Because no one has asked for it? :)
Or you can just do as the example in samples/kobject/ does it, no need for the void pointer as that code shows.
Quoted 168 lines
Thanks,
Signed-off-by KaiGai Kohei <[email protected]>--
Documentation/ABI/testing/sysfs-kernel-capability | 23 +++++ scripts/mkcapnames.sh | 44 +++++++++ security/Makefile | 9 ++ security/commoncap.c | 102 +++++++++++++++++++++ 4 files changed, 178 insertions(+), 0 deletions(-)Documentation/ABI/testing/sysfs-kernel-capability +23
-0@@ -0,0 +1,23 @@ +What: /sys/kernel/capability +Date: Feb 2008 +Contact: KaiGai Kohei <[email protected]> +Description: + The entries under /sys/kernel/capability are used to export + the list of capabilities the running kernel supported. + + - /sys/kernel/capability/version + returns the most preferable version number for the + running kernel. + e.g) $ cat /sys/kernel/capability/version + 0x20071026 + + - /sys/kernel/capability/code/<numerical representation> + returns its symbolic representation, on reading. + e.g) $ cat /sys/kernel/capability/codes/30 + cap_audit_control + + - /sys/kernel/capability/name/<symbolic representation> + returns its numerical representation, on reading. + e.g) $ cat /sys/kernel/capability/names/cap_sys_pacct + 20 +scripts/mkcapnames.sh +44
-0@@ -0,0 +1,44 @@ +#!/bin/sh + +# +# generate a cap_names.h file from include/linux/capability.h +# + +CAPHEAD="`dirname $0`/../include/linux/capability.h" +REGEXP='^#define CAP_[A-Z_]+[ ]+[0-9]+$' +NUMCAP=`cat "$CAPHEAD" | egrep -c "$REGEXP"` + +echo '#ifndef CAP_NAMES_H' +echo '#define CAP_NAMES_H' +echo +echo '/*' +echo ' * Do NOT edit this file directly.' +echo ' * This file is generated from include/linux/capability.h automatically' +echo ' */' +echo +echo '#if !defined(SYSFS_CAP_NAME_ENTRY) || !defined(SYSFS_CAP_CODE_ENTRY)' +echo '#error cap_names.h should be included from security/capability.c' +echo '#else' +echo "#if $NUMCAP != CAP_LAST_CAP + 1" +echo '#error mkcapnames.sh cannot collect capabilities correctly' +echo '#else' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("SYSFS_CAP_NAME_ENTRY(%s,%s);\n", tolower($2), $2); }' +echo +echo 'static struct attribute *capability_name_attrs[] = {' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("\t&%s_name_attr.attr,\n", tolower($2)); } END { print "\tNULL," }' +echo '};' + +echo +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("SYSFS_CAP_CODE_ENTRY(%s,%s);\n", tolower($2), $2); }' +echo +echo 'static struct attribute *capability_code_attrs[] = {' +cat "$CAPHEAD" | egrep "$REGEXP" \ + | awk '{ printf("\t&%s_code_attr.attr,\n", tolower($2)); } END { print "\tNULL," }' +echo '};' + +echo '#endif' +echo '#endif' +echo '#endif'security/Makefile +9
-0@@ -18,3 +18,12 @@ obj-$(CONFIG_SECURITY_SELINUX) += selinux/built-in.o obj-$(CONFIG_SECURITY_SMACK) += commoncap.o smack/built-in.o obj-$(CONFIG_SECURITY_CAPABILITIES) += commoncap.o capability.o obj-$(CONFIG_SECURITY_ROOTPLUG) += commoncap.o root_plug.o + +# cap_names.h contains the code/name pair of capabilities. +# It is generated using include/linux/capability.h automatically. +$(obj)/commoncap.o: $(obj)/cap_names.h +quiet_cmd_cap_names = CAPS $@ + cmd_cap_names = /bin/sh $(src)/../scripts/mkcapnames.sh > $@ +targets += cap_names.h +$(obj)/cap_names.h: $(src)/../scripts/mkcapnames.sh $(src)/../include/linux/capability.h FORCE + $(call if_changed,cap_names)security/commoncap.c +49
-0@@ -24,6 +24,8 @@#include <linux/hugetlb.h> #include <linux/mount.h> #include <linux/sched.h> +#include <linux/kobject.h> +#include <linux/sysfs.h> /* Global security state */ @@ -637,3 +639,103 @@ int cap_vm_enough_memory(struct mm_struct *mm, long pages)return __vm_enough_memory (mm, pages, cap_sys_admin); } +#ifdef CONFIG_SYSFS +/* +* Export the list of capabilities on /sys/kernel/capability +*/ +static struct kobject *capability_kobj; + +#define SYSFS_CAP_NAME_ENTRY (_name,_code) \ + static ssize_t capname_##_name##_show(struct kobject *kobj, \ + struct kobj_attribute *attr, \ + char *buffer) \ + { \ + return scnprintf(buffer, PAGE_SIZE, "%d\n", _code); \ + } \ + static struct kobj_attribute _name##_name_attr = { \ + .attr = { .name = __stringify(_name), .mode = 0444, }, \ + .show = capname_##_name##_show, \ + } + +#define SYSFS_CAP_CODE_ENTRY (_name,_code) \ + static ssize_t capcode_##_name##_show(struct kobject *kobj, \ + struct kobj_attribute *attr, \ + char *buffer) \ + { \ + return scnprintf(buffer, PAGE_SIZE, "%s\n", __stringify(_name)); \ + } \ + static struct kobj_attribute _name##_code_attr = { \ + .attr = { .name = __stringify(_code), .mode = 0444, }, \ + .show = capcode_##_name##_show, \ + } + +/* +* capability_attrs[] is generated automatically by scripts/mkcapnames.sh +* This script parses include/linux/capability.h +*/ +#include "cap_names.h" + +static struct attribute_group capability_name_attr_group = { + .name ="names" , + .attrs = capability_name_attrs, +}; + +static struct attribute_group capability_code_attr_group = { + .name ="codes" , + .attrs = capability_code_attrs, +}; + +static ssize_t capability_version_show(struct kobject *kobj,
security/commoncap.c int cap_vm_enough_memory(struct mm_struct *mm, long pages) · line 698
Quoted 10 lines
security/commoncap.c +10
-0+struct kobj_attribute *attr, + char *buffer) +{ + return scnprintf(buffer, PAGE_SIZE, "0x%08x\n", +_LINUX_CAPABILITY_VERSION ); +} +static struct kobj_attribute cap_version_attr = { + .attr = { .name ="version" , .mode =0444 }, + .show = capability_version_show, +};
We do have macros for these kinds of things :)
Look at ATTR() and friends.
Quoted 33 lines
security/commoncap.c +33
-0+ +static int __init capability_export_names (void ) +{ +int rc = -ENOMEM ; + +/* make /sys/kernel/capability */ + capability_kobj =kobject_create_and_add ("capability" , kernel_kobj); +if (!capability_kobj) + goto error0; + +/* make /sys/kernel/capability/names */ + rc =sysfs_create_group (capability_kobj, + &capability_name_attr_group); +if (rc) + goto error1; + +/* make /sys/kernel/capability/codes */ + rc =sysfs_create_group (capability_kobj, + &capability_code_attr_group); +if (rc) + goto error2; + +/* make /sys/kernel/capability/version */ + rc =sysfs_create_file (capability_kobj, + &cap_version_attr.attr); +if (rc) + goto error3; + +return 0 ; + +error3: +sysfs_remove_group (capability_kobj, &capability_code_attr_group); +error2:
security/commoncap.c int cap_vm_enough_memory(struct mm_struct *mm, long pages) · line 741
Quoted 10 lines
security/commoncap.c +10
-0+sysfs_remove_group (capability_kobj, &capability_name_attr_group); +error1: +kobject_put (capability_kobj); +error0: +printk (KERN_ERR "Unable to export capabilities\n" ); + + return rc; +} +__initcall (capability_export_names); +#endif /* CONFIG_SYSFS */
Where do you remove these files? Or will that never happen?
thanks,
greg k-h
Re: [PATCH] exporting capability code/name pairs (try #5.1)
Quoted 19 lines · Greg KH
Quoted 18 lines · Kohei KaiGai
Quoted 17 lines · Greg KH
Quoted 16 lines · Serge E. Hallyn
Quoted 16 lines
--------
This patch enables to export code/name of capabilities supported on the running kernel.A newer kernel sometimes adds new capabilities, like
CAP_MAC_ADMINat 2.6.25. However, we have no interface to disclose what capabilities are supported on this kernel. Thus, we have to maintain libcap version in appropriate one synchronously.This patch enables libcap to collect the list of capabilities on run time, and provide them for users.
It helps to improve portability of library.It exports these information as regular files under
/sys/kernel/capability. The numeric node exports its name, the symbolic node exports its code.
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
Please consider to put this patch on the queue of 2.6.25.
Looks good, except don't you need to put the code in
commoncap.cunder a #ifdef SYSFS?Fair enough.
I added the #ifdef - #endif block in this patch.Not needed, if SYSFS is not build in, all of that code pretty much compiles away to nothing. So you can drop that.
Hmm..., I reverted these #ifdef and #endif in this version.
Quoted 4 lines
Quoted 4 lines
Quoted 2 lines
Also, this code can be cleaned up a lot by just using the basic kobject attributes, and not rolling your own types here.
I replaced my own defined
capability_attributebykobj_attribute.
Quoted 8 lines
Quoted 3 lines
It made the patch cleaned up, however, it also impossible to share a single
_show()method instance, becausekobj_attributedoes not have any private member. Is there any reason whykobj_attributedoes not have "void *private;"?Because no one has asked for it? :)
Or you can just do as the example in
samples/kobject/does it, no need for the void pointer as that code shows.
It shows us a good example in samples/kobject.
However, it is unsuitable to export the list of capabilities.
The shared _show() method (b_show) calls strcmp() once with the name of kobject attribute to switch its returning string.
If we have 34 of candidates to be returned, like the capability case, we have to call strcmp() 33 times in maximum.
If we can have a private member in kobj_attribute, we can found the content to be returned in a single step.
Quoted 8 lines
Review
Quoted 4 lines
(quoted diff) +4
-0+static struct kobj_attribute cap_version_attr = { + .attr = { .name = "version", .mode = 0444 }, + .show = capability_version_show, +};We do have macros for these kinds of things :)
Look at
ATTR()and friends.
OK, fixed.
I applied __ATTR() instead.
Quoted 36 lines
Quoted 36 lines
(quoted diff) +36
-0+static int __init capability_export_names(void) +{ + int rc = -ENOMEM; + + /* make /sys/kernel/capability */ + capability_kobj = kobject_create_and_add("capability", kernel_kobj); + if (!capability_kobj) + goto error0; + + /* make /sys/kernel/capability/names */ + rc = sysfs_create_group(capability_kobj, + &capability_name_attr_group); + if (rc) + goto error1; + + /* make /sys/kernel/capability/codes */ + rc = sysfs_create_group(capability_kobj, + &capability_code_attr_group); + if (rc) + goto error2; + + /* make /sys/kernel/capability/version */ + rc = sysfs_create_file(capability_kobj, + &cap_version_attr.attr); + if (rc) + goto error3; + + return 0; + +error3: + sysfs_remove_group(capability_kobj, &capability_code_attr_group); +error2: + sysfs_remove_group(capability_kobj, &capability_name_attr_group); +error1: + kobject_put(capability_kobj); +error0:
Quoted 8 lines
Review
Quoted 6 lines
(quoted diff) +6
-0+ printk(KERN_ERR "Unable to export capabilities\n"); + + return rc; +} +__initcall(capability_export_names); +#endif /* CONFIG_SYSFS */Where do you remove these files? Or will that never happen?
Removing these files are never happen.
Thanks,
--
Documentation/ABI/testing/sysfs-kernel-capability | 23 +++++ scripts/mkcapnames.sh | 44 ++++++++++ security/Makefile | 9 ++ security/commoncap.c | 94 +++++++++++++++++++++ 4 files changed, 170 insertions(+), 0 deletions(-)
Documentation/ABI/testing/sysfs-kernel-capability +23 -0
@@ -0,0 +1,23 @@ +What: /sys/kernel/capability +Date: Feb 2008 +Contact: KaiGai Kohei <[email protected]> +Description: + The entries under /sys/kernel/capability are used to export + the list of capabilities the running kernel supported. + + - /sys/kernel/capability/version + returns the most preferable version number for the + running kernel. + e.g) $ cat /sys/kernel/capability/version + 0x20071026 + + - /sys/kernel/capability/code/<numerical representation> + returns its symbolic representation, on reading. + e.g) $ cat /sys/kernel/capability/codes/30 + cap_audit_control + + - /sys/kernel/capability/name/<symbolic representation> + returns its numerical representation, on reading. + e.g) $ cat /sys/kernel/capability/names/cap_sys_pacct + 20 +
scripts/mkcapnames.sh +44 -0
44 lines not on this page · raw message
security/Makefile +9 -0
@@ -18,3 +18,12 @@ obj-$(CONFIG_SECURITY_SELINUX) += selinux/built-in.o obj-$(CONFIG_SECURITY_SMACK) += commoncap.o smack/built-in.o obj-$(CONFIG_SECURITY_CAPABILITIES) += commoncap.o capability.o obj-$(CONFIG_SECURITY_ROOTPLUG) += commoncap.o root_plug.o + +# cap_names.h contains the code/name pair of capabilities. +# It is generated using include/linux/capability.h automatically. +$(obj)/commoncap.o: $(obj)/cap_names.h +quiet_cmd_cap_names = CAPS $@ + cmd_cap_names = /bin/sh $(src)/../scripts/mkcapnames.sh > $@ +targets += cap_names.h +$(obj)/cap_names.h: $(src)/../scripts/mkcapnames.sh $(src)/../include/linux/capability.h FORCE + $(call if_changed,cap_names)
security/commoncap.c +94 -0
103 lines not on this page · raw message
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Re: [PATCH] exporting capability code/name pairs (try #5.1)
Quoted 16 lines · Kohei KaiGai
Quoted 4 lines · Greg KH
Quoted 4 lines
Quoted 2 lines
Also, this code can be cleaned up a lot by just using the basic kobject attributes, and not rolling your own types here.
I replaced my own defined
capability_attributebykobj_attribute.Quoted 8 lines
Quoted 3 lines
It made the patch cleaned up, however, it also impossible to share a single
_show()method instance, becausekobj_attributedoes not have any private member. Is there any reason whykobj_attributedoes not have "void *private;"?Because no one has asked for it? :)
Or you can just do as the example in
samples/kobject/does it, no need for the void pointer as that code shows.It shows us a good example in
samples/kobject.
Quoted 8 lines
However, it is unsuitable to export the list of capabilities.
The shared_show()method (b_show) callsstrcmp()once with the name of kobject attribute to switch its returning string.
If we have 34 of candidates to be returned, like the capability case, we have to callstrcmp()33 times in maximum.If we can have a private member in
kobj_attribute, we can found the content to be returned in a single step.
Ok, again, just send me a patch that adds this functionality and we will be very glad to consider it.
thnaks,
greg k-h
PATCH 1/1 exporting capability code/name pairs (try #6)
Quoted 5 lines
Quoted 2 lines
If we can have a private member in
kobj_attribute, we can found the content to be returned in a single step.Ok, again, just send me a patch that adds this functionality and we will be very glad to consider it.
[1/2] Add a private data field within kobj_attribute structure.
This patch add a private data field, declared as void *, within kobj_attribute structure. Anyone wants to use sysfs can store their private data to refer at _show() and _store() method.
It enables to share a single method function with several similar entries, like ones to export the list of capabilities the running kernel supported.
--
include/linux/kobject.h | 1 + include/linux/sysfs.h | 7 +++++++ 2 files changed, 8 insertions(+), 0 deletions(-)
include/linux/kobject.h +1 -0
@@ -130,6 +130,7 @@ struct kobj_attribute { char *buf);ssize_t (*store)(struct kobject *kobj,struct kobj_attribute *attr,const char *buf,size_t count); +void *data;/* a private field */ };extern struct sysfs_ops kobj_sysfs_ops;
include/linux/sysfs.h +7 -0
@@ -50,6 +50,13 @@ struct attribute_group { .store = _store, \ } +#define __ATTR_DATA (_name,_mode,_show,_store,_data) { \ + .attr = {.name = __stringify(_name), .mode = _mode }, \ + .show = _show, \ + .store = _store, \ + .data = (void *)(_data), \ +} +#define __ATTR_RO (_name) { \ .attr = { .name = __stringify(_name), .mode = 0444 }, \ .show = _name##_show, \
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Re: [PATCH] exporting capability code/name pairs (try #6)
Quoted 9 lines · Kohei KaiGai
Quoted 1 line
Quoted 1 line
If we can have a private member in
kobj_attribute, we can found thecontent
Quoted 4 lines
Quoted 1 line
to be returned in a single step.
Ok, again, just send me a patch that adds this functionality and we will be very glad to consider it.
[1/2] Add a private data field within
kobj_attributestructure.
Quoted 7 lines
This patch add a private data field, declared as void *, within
kobj_attribute
structure. Anyone wants to use sysfs can store their private data to refer at_show()and_store()method.
It enables to share a single method function with several similar entries, like ones to export the list of capabilities the running kernel supported.
But your patch 2/2 doesn't use this interface, why not?
include/linux/kobject.h struct kobj_attribute { · line 133
Quoted 13 lines
include/linux/kobject.h | 1 + include/linux/sysfs.h | 7 +++++++ 2 files changed, 8 insertions(+), 0 deletions(-)include/linux/kobject.h +1
-0@@ -130,6 +130,7 @@ struct kobj_attribute { char *buf);ssize_t (*store)(struct kobject *kobj,struct kobj_attribute *attr,const char *buf,size_t count); +void *data;/* a private field */
Hm, can you really use this?
Quoted 6 lines
include/linux/kobject.h +0
-0extern struct sysfs_ops kobj_sysfs_ops;include/linux/sysfs.h +0
-0
include/linux/sysfs.h struct attribute_group { · line 58
Quoted 9 lines
include/linux/sysfs.h +6
-0@@ -50,6 +50,13 @@ struct attribute_group { .store = _store, \ } +#define __ATTR_DATA (_name,_mode,_show,_store,_data) { \ + .attr = {.name = __stringify(_name), .mode = _mode }, \ + .show = _show, \ + .store = _store, \ + .data = (void *)(_data), \ +}
I don't see how this would be any different from the original? You are always passed a kobject, which can be embedded in anything else.
Could you also modify the documentation and the sample code to use this new field, showing how it is to be used, and testing that it works properly at the same time?
thanks,
greg k-h
Re: [PATCH] exporting capability code/name pairs (try #6)
Quoted 8 lines · Greg KH
Quoted 7 lines · Kohei KaiGai
Quoted 1 line
Quoted 1 line
If we can have a private member in
kobj_attribute, we can found thecontent
Quoted 3 lines
Quoted 1 line
to be returned in a single step.
Ok, again, just send me a patch that adds this functionality and we will be very glad to consider it.
[1/2] Add a private data field within
kobj_attributestructure.
Quoted 7 lines
Quoted 5 lines
This patch add a private data field, declared as void *, within
kobj_attributestructure. Anyone wants to use sysfs can store their private data to refer at_show()and_store()method.
It enables to share a single method function with several similar entries, like ones to export the list of capabilities the running kernel supported.But your patch 2/2 doesn't use this interface, why not?
Really?
The following two _show() methods shared by every capabilities refer the private member of kobj_attribute.
| +static ssize_t capability_name_show(struct kobject *kobj,
| + struct kobj_attribute *attr,
| + char *buffer)
| +{
| + /* It returns numerical representation of capability. */
| + return scnprintf(buffer, PAGE_SIZE, "%d\n", (int) attr->data);
| +}
| +
| +static ssize_t capability_code_show(struct kobject *kobj,
| + struct kobj_attribute *attr,
| + char *buffer)
| +{
| + /* It returns symbolic representation of capability. */
| + return scnprintf(buffer, PAGE_SIZE, "%s\n", (char *) attr->data);
| +}Quoted 4 lines
Quoted 4 lines
include/linux/kobject.h | 1 + include/linux/sysfs.h | 7 +++++++ 2 files changed, 8 insertions(+), 0 deletions(-)
Quoted 11 lines
include/linux/kobject.h struct kobj_attribute { · line 133
Quoted 9 lines
include/linux/kobject.h +1
-0@@ -130,6 +130,7 @@ struct kobj_attribute { char *buf);ssize_t (*store)(struct kobject *kobj,struct kobj_attribute *attr,const char *buf,size_t count); +void *data;/* a private field */ Hm, can you really use this?
Yes,
Quoted 9 lines
Quoted 9 lines
include/linux/kobject.h +0
-0extern struct sysfs_ops kobj_sysfs_ops;include/linux/sysfs.h +0
-0@@ -50,6 +50,13 @@ struct attribute_group { .store = _store, \ }
Quoted 9 lines
include/linux/sysfs.h struct attribute_group { · line 58
Quoted 6 lines
include/linux/sysfs.h +6
-0+#define __ATTR_DATA (_name,_mode,_show,_store,_data) { \ + .attr = {.name = __stringify(_name), .mode = _mode }, \ + .show = _show, \ + .store = _store, \ + .data = (void *)(_data), \ +}I don't see how this would be any different from the original? You are always passed a kobject, which can be embedded in anything else.
The intension of the latest patch is same as the version which uses capability_attribute structure.
It enables to store the content to be returned in the expanded field. Applying kobj_attribute killed needs to declare my own structure.
However, every entries had its own _show() method, generated by macros automatically, in the previous version. It fundamentally differ from the latest one.
Quoted 3 lines
Could you also modify the documentation and the sample code to use this new field, showing how it is to be used, and testing that it works properly at the same time?
OK, Please wait for a while.
Thanks,
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Re: [PATCH] exporting capability code/name pairs (try #6)
Quoted 24 lines · Kohei KaiGai
Quoted 17 lines · Greg KH
Quoted 7 lines · Kohei KaiGai
Quoted 1 line
Quoted 1 line
If we can have a private member in
kobj_attribute, we can found thecontent
Quoted 3 lines
Quoted 1 line
to be returned in a single step.
Ok, again, just send me a patch that adds this functionality and we will be very glad to consider it.
[1/2] Add a private data field within
kobj_attributestructure.Quoted 9 lines
This patch add a private data field, declared as void *, within
kobj_attribute
structure. Anyone wants to use sysfs can store their private data to refer at_show()and_store()method.
It enables to share a single method function with several similar entries,
like ones to export the list of capabilities the running kernel supported.Quoted 1 line
But your patch 2/2 doesn't use this interface, why not?
Really?
The following two_show()methods shared by every capabilities refer the private member ofkobj_attribute.
Quoted 15 lines
| +static ssize_t capability_name_show(struct kobject *kobj,
| + struct kobj_attribute *attr,
| + char *buffer)
| +{
| + /* It returns numerical representation of capability. */
| + return scnprintf(buffer, PAGE_SIZE, "%d\n", (int) attr->data);
| +}
| +
| +static ssize_t capability_code_show(struct kobject *kobj,
| + struct kobj_attribute *attr,
| + char *buffer)
| +{
| + /* It returns symbolic representation of capability. */
| + return scnprintf(buffer, PAGE_SIZE, "%s\n", (char *) attr->data);
| +}Ah, sorry, missed that. I also missed where this was set up as well :(
thanks,
greg k-h
Re: [PATCH] exporting capability code/name pairs (try #6.1)
In reply to Kohei KaiGaiQuoted 5 lines
Quoted 3 lines
Could you also modify the documentation and the sample code to use this new field, showing how it is to be used, and testing that it works properly at the same time?
OK, Please wait for a while.
[3/3] Add a new example of kobject/attribute
The attached patch can provide a new exmple to use kobject and attribute. The _show() and _store() method can refer/store the private data field of kobj_attribute structure to know what entries are refered by users. It will make easier to share a single _show()/_store() method with several entries.
--
samples/kobject/kobject-example.c | 32 ++++++++++++++++++++++++++++++++ 1 files changed, 32 insertions(+), 0 deletions(-)
samples/kobject/kobject-example.c +32 -0
@@ -77,6 +77,35 @@ static struct kobj_attribute baz_attribute =static struct kobj_attribute bar_attribute =__ATTR (bar,0666 , b_show, b_store); +/* +* You can store a private data within 'data' field of kobj_attribute. +* It enables to share a single _show() or _store() method with several +* entries. +*/ +static ssize_t integer_show (struct kobject *kobj, +struct kobj_attribute *attr, +char *buf) +{ +return scnprintf (buf,PAGE_SIZE ,"%d\n" , (int ) attr->data); +} + +static ssize_t integer_store (struct kobject *kobj, +struct kobj_attribute *attr, +const char *buf,size_t count) +{ +int code; + +sscanf (buf,"%du" , &code); + attr->data = (void *) code; +return count; +} + +static struct kobj_attribute hoge_attribute = +__ATTR_DATA (hoge,0666 , integer_show, integer_store,123 ); +static struct kobj_attribute piyo_attribute = +__ATTR_DATA (piyo,0666 , integer_show, integer_store,456 ); +static struct kobj_attribute fuga_attribute = +__ATTR_DATA (fuga,0444 , integer_show,NULL ,789 );/* * Create a group of attributes so that we can create and destory them all
@@ -86,6 +115,9 @@ static struct attribute *attrs[] = { &foo_attribute.attr, &baz_attribute.attr, &bar_attribute.attr, + &hoge_attribute.attr, + &piyo_attribute.attr, + &fuga_attribute.attr, NULL, /* need to NULL terminate the list of attributes */ };
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Re: [PATCH] exporting capability code/name pairs (try #6.1)
In reply to Kohei KaiGai[Sorry, I sent a patch with TABs translated into spaces.]
[1/3] Add a private data field within kobj_attribute structure.
This patch add a private data field, declared as void *, within kobj_attribute structure. Anyone wants to use sysfs can store their private data to refer at _show() and _store() method.
It enables to share a single method function with several similar entries, like ones to export the list of capabilities the running kernel supported.
Signature · 3 lines
include/linux/kobject.h | 1 + include/linux/sysfs.h | 7 +++++++ 2 files changed, 8 insertions(+), 0 deletions(-)
include/linux/kobject.h +1 -0
@@ -130,6 +130,7 @@ struct kobj_attribute { char *buf);ssize_t (*store)(struct kobject *kobj,struct kobj_attribute *attr,const char *buf,size_t count); +void *data;/* a private field */ };extern struct sysfs_ops kobj_sysfs_ops;
include/linux/sysfs.h +7 -0
@@ -50,6 +50,13 @@ struct attribute_group { .store = _store, \ } +#define __ATTR_DATA (_name,_mode,_show,_store,_data) { \ + .attr = {.name = __stringify(_name), .mode = _mode }, \ + .show = _show, \ + .store = _store, \ + .data = (void *)(_data), \ +} +#define __ATTR_RO (_name) { \ .attr = { .name = __stringify(_name), .mode = 0444 }, \ .show = _name##_show, \
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
PATCH 1/1 exporting capability code/name pairs (try #6)
In reply to Greg KHQuoted 21 lines · Greg KH
Quoted 20 lines · Kohei KaiGai
Quoted 11 lines · Greg KH
Quoted 7 lines
Quoted 2 lines
Also, this code can be cleaned up a lot by just using the basic kobject attributes, and not rolling your own types here.
I replaced my own defined
capability_attributebykobj_attribute.It made the patch cleaned up, however, it also impossible to share a single
_show()method instance, becausekobj_attributedoes not have any private member. Is there any reason whykobj_attributedoes not have "void *private;"?Because no one has asked for it? :)
Or you can just do as the example in
samples/kobject/does it, no need for the void pointer as that code shows.It shows us a good example in
samples/kobject.However, it is unsuitable to export the list of capabilities.
The shared_show()method (b_show) callsstrcmp()once with the name of kobject attribute to switch its returning string.
If we have 34 of candidates to be returned, like the capability case, we have to callstrcmp()33 times in maximum.
Quoted 5 lines
Quoted 2 lines
If we can have a private member in
kobj_attribute, we can found the content to be returned in a single step.Ok, again, just send me a patch that adds this functionality and we will be very glad to consider it.
In the attached patch, every attribute entry stores its capability identifier in numerical or symbolic representation within private data field of kobj_attribute structure.
The rest of them are unchanged.
----
[2/2] Exporting capability code/name pairs
This patch enables to export code/name of capabilities supported on the running kernel.
A newer kernel sometimes adds new capabilities, like CAP_MAC_ADMIN at 2.6.25. However, we have no interface to disclose what capabilities are supported on this kernel. Thus, we have to maintain libcap version in appropriate one synchronously.
This patch enables libcap to collect the list of capabilities on run time, and provide them for users.
It helps to improve portability of library.
It exports these information as regular files under /sys/kernel/capability. The numeric node exports its name, the symbolic node exports its code.
Please consider to put this patch on the queue of 2.6.25.
Thanks,
===================================================
[kaigai@saba ~]$ ls -R /sys/kernel/capability//sys/kernel/capability/:
codes names version
/sys/kernel/capability/codes:
0 10 12 14 16 18 2 21 23 25 27 29 30 32 4 6 8 1 11 13 15 17 19 20 22 24 26 28 3 31 33 5 7 9
/sys/kernel/capability/names:
cap_audit_control cap_kill cap_net_raw cap_sys_nice cap_audit_write cap_lease cap_setfcap cap_sys_pacct cap_chown cap_linux_immutable cap_setgid cap_sys_ptrace cap_dac_override cap_mac_admin cap_setpcap cap_sys_rawio cap_dac_read_search cap_mac_override cap_setuid cap_sys_resource cap_fowner cap_mknod cap_sys_admin cap_sys_time cap_fsetid cap_net_admin cap_sys_boot cap_sys_tty_config cap_ipc_lock cap_net_bind_service cap_sys_chroot cap_ipc_owner cap_net_broadcast cap_sys_module
[kaigai@saba ~]$ cat /sys/kernel/capability/version 0x20071026
[kaigai@saba ~]$ cat /sys/kernel/capability/codes/30 cap_audit_control
[kaigai@saba ~]$ cat /sys/kernel/capability/names/cap_sys_pacct 20
[kaigai@saba ~]$
===================================================
--
Documentation/ABI/testing/sysfs-kernel-capability | 23 +++++ scripts/mkcapnames.sh | 44 +++++++++ security/Makefile | 9 ++ security/commoncap.c | 99 +++++++++++++++++++++ 4 files changed, 175 insertions(+), 0 deletions(-)
Documentation/ABI/testing/sysfs-kernel-capability +23 -0
@@ -0,0 +1,23 @@ +What: /sys/kernel/capability +Date: Feb 2008 +Contact: KaiGai Kohei <[email protected]> +Description: + The entries under /sys/kernel/capability are used to export + the list of capabilities the running kernel supported. + + - /sys/kernel/capability/version + returns the most preferable version number for the + running kernel. + e.g) $ cat /sys/kernel/capability/version + 0x20071026 + + - /sys/kernel/capability/code/<numerical representation> + returns its symbolic representation, on reading. + e.g) $ cat /sys/kernel/capability/codes/30 + cap_audit_control + + - /sys/kernel/capability/name/<symbolic representation> + returns its numerical representation, on reading. + e.g) $ cat /sys/kernel/capability/names/cap_sys_pacct + 20 +
scripts/mkcapnames.sh +44 -0
44 lines not on this page · raw message
security/Makefile +9 -0
@@ -18,3 +18,12 @@ obj-$(CONFIG_SECURITY_SELINUX) += selinux/built-in.o obj-$(CONFIG_SECURITY_SMACK) += commoncap.o smack/built-in.o obj-$(CONFIG_SECURITY_CAPABILITIES) += commoncap.o capability.o obj-$(CONFIG_SECURITY_ROOTPLUG) += commoncap.o root_plug.o + +# cap_names.h contains the code/name pair of capabilities. +# It is generated using include/linux/capability.h automatically. +$(obj)/commoncap.o: $(obj)/cap_names.h +quiet_cmd_cap_names = CAPS $@ + cmd_cap_names = /bin/sh $(src)/../scripts/mkcapnames.sh > $@ +targets += cap_names.h +$(obj)/cap_names.h: $(src)/../scripts/mkcapnames.sh $(src)/../include/linux/capability.h FORCE + $(call if_changed,cap_names)
security/commoncap.c +99 -0
108 lines not on this page · raw message
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Re: [PATCH] exporting capability code/name pairs (try #6.1)
[Sorry, I sent a patch with TABs translated into spaces.]
In the attached patch, every attribute entry stores its capability identifier in numerical or symbolic representation within private data field of kobj_attribute structure.
The rest of them are unchanged.
----
[2/3] Exporting capability code/name pairs
This patch enables to export code/name of capabilities supported on the running kernel.
A newer kernel sometimes adds new capabilities, like CAP_MAC_ADMIN at 2.6.25. However, we have no interface to disclose what capabilities are supported on this kernel. Thus, we have to maintain libcap version in appropriate one synchronously.
This patch enables libcap to collect the list of capabilities on run time, and provide them for users.
It helps to improve portability of library.
It exports these information as regular files under /sys/kernel/capability. The numeric node exports its name, the symbolic node exports its code.
Please consider to put this patch on the queue of 2.6.25.
Thanks,
===================================================
[kaigai@saba ~]$ ls -R /sys/kernel/capability//sys/kernel/capability/:
codes names version
/sys/kernel/capability/codes:
0 10 12 14 16 18 2 21 23 25 27 29 30 32 4 6 8 1 11 13 15 17 19 20 22 24 26 28 3 31 33 5 7 9
/sys/kernel/capability/names:
cap_audit_control cap_kill cap_net_raw cap_sys_nice cap_audit_write cap_lease cap_setfcap cap_sys_pacct cap_chown cap_linux_immutable cap_setgid cap_sys_ptrace cap_dac_override cap_mac_admin cap_setpcap cap_sys_rawio cap_dac_read_search cap_mac_override cap_setuid cap_sys_resource cap_fowner cap_mknod cap_sys_admin cap_sys_time cap_fsetid cap_net_admin cap_sys_boot cap_sys_tty_config cap_ipc_lock cap_net_bind_service cap_sys_chroot cap_ipc_owner cap_net_broadcast cap_sys_module
[kaigai@saba ~]$ cat /sys/kernel/capability/version 0x20071026
[kaigai@saba ~]$ cat /sys/kernel/capability/codes/30 cap_audit_control
[kaigai@saba ~]$ cat /sys/kernel/capability/names/cap_sys_pacct 20
[kaigai@saba ~]$
===================================================
--
Documentation/ABI/testing/sysfs-kernel-capability | 23 +++++ scripts/mkcapnames.sh | 44 +++++++++ security/Makefile | 9 ++ security/commoncap.c | 99 +++++++++++++++++++++ 4 files changed, 175 insertions(+), 0 deletions(-)
Documentation/ABI/testing/sysfs-kernel-capability +23 -0
@@ -0,0 +1,23 @@ +What: /sys/kernel/capability +Date: Feb 2008 +Contact: KaiGai Kohei <[email protected]> +Description: + The entries under /sys/kernel/capability are used to export + the list of capabilities the running kernel supported. + + - /sys/kernel/capability/version + returns the most preferable version number for the + running kernel. + e.g) $ cat /sys/kernel/capability/version + 0x20071026 + + - /sys/kernel/capability/code/<numerical representation> + returns its symbolic representation, on reading. + e.g) $ cat /sys/kernel/capability/codes/30 + cap_audit_control + + - /sys/kernel/capability/name/<symbolic representation> + returns its numerical representation, on reading. + e.g) $ cat /sys/kernel/capability/names/cap_sys_pacct + 20 +
scripts/mkcapnames.sh +44 -0
44 lines not on this page · raw message
security/Makefile +9 -0
@@ -18,3 +18,12 @@ obj-$(CONFIG_SECURITY_SELINUX) += selinux/built-in.o obj-$(CONFIG_SECURITY_SMACK) += commoncap.o smack/built-in.o obj-$(CONFIG_SECURITY_CAPABILITIES) += commoncap.o capability.o obj-$(CONFIG_SECURITY_ROOTPLUG) += commoncap.o root_plug.o + +# cap_names.h contains the code/name pair of capabilities. +# It is generated using include/linux/capability.h automatically. +$(obj)/commoncap.o: $(obj)/cap_names.h +quiet_cmd_cap_names = CAPS $@ + cmd_cap_names = /bin/sh $(src)/../scripts/mkcapnames.sh > $@ +targets += cap_names.h +$(obj)/cap_names.h: $(src)/../scripts/mkcapnames.sh $(src)/../include/linux/capability.h FORCE + $(call if_changed,cap_names)
security/commoncap.c +99 -0
108 lines not on this page · raw message
Signature · 2 lines
OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
Re: [PATCH] exporting capability code/name pairs (try #5.1)
In reply to Greg KHQuoted 20 lines · Greg KH
Quoted 19 lines · Kohei KaiGai
Quoted 18 lines · Greg KH
Quoted 17 lines · Serge E. Hallyn
Quoted 17 lines
--------
This patch enables to export code/name of capabilities supported on the running kernel.A newer kernel sometimes adds new capabilities, like
CAP_MAC_ADMINat 2.6.25. However, we have no interface to disclose what capabilities are supported on this kernel. Thus, we have to maintain libcap version in appropriate one synchronously.This patch enables libcap to collect the list of capabilities on run time, and provide them for users.
It helps to improve portability of library.It exports these information as regular files under
/sys/kernel/capability. The numeric node exports its name, the symbolic node exports its code.Please consider to put this patch on the queue of 2.6.25.
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
Quoted 2 lines
Looks good, except don't you need to put the code in
commoncap.cunder a #ifdef SYSFS?Fair enough.
I added the #ifdef - #endif block in this patch.Not needed, if SYSFS is not build in, all of that code pretty much compiles away to nothing. So you can drop that.
Oops. Sorry.
-serge