Sorry, but this is bullshit (like most of the lsm changes). Either you
leave the capable in and say it's enough or you add your random hook
and remove that one. Just adding more and more hooks without thinking
gets us exactly nowhere except to an unmaintainable codebase.
Also is there a _real_ need to pass in all the arguments?
> return -EPERM;
> }
> + retval = security_ops->iopl(old, level);
> + if (retval) {
> + return retval;
> + }
> +
again (and another few times)
> + * @module_create:
> + * Check the permission before allocating space for a module.
> + * @name contains the module name.
> + * @size contains the module size.
> + * Return 0 if permission is granted.
> + * @module_initialize:
> + * Check permission before initializing a module.
> + * @mod contains a pointer to the module being initialized.
> + * Return 0 if permission is granted.
Umm, you can't tell me you deny someone to initialize a module he has
just created?
> + * @sethostname:
> + * Check permission before the hostname is set to @hostname.
> + * @hostname contains the new hostname
> + * Return 0 if permission is granted.
> + * @setdomainname:
> + * Check permission before the domainname is set to @domainname.
> + * @domainname contains the new domainname
> + * Return 0 if permission is granted.
You don't think this should maybe be just one hook?
> + * @ioperm:
> + * Check permission before setting port input/output permissions for the
> + * process for @num bytes starting from the port address @from to the
> + * value @turn_on.
> + * @from contains the starting port address.
> + * @num contains the number of bytes starting from @from.
> + * @turn_on contains the permissions value.
> + * Return 0 if permission is granted.
> + * @iopl:
> + * Check permission before changing the I/O privilege level of the current
> + * process from @old to @level.
> + * @old contains the old level.
> + * @level contains the new level.
> + * Return 0 if permission is granted.
Dito.
> + * @sysctl:
> + * Check permission before accessing the @table sysctl variable in the
> + * manner specified by @op.
> + * @table contains the ctl_table structure for the sysctl variable.
> + * @op contains the operation (001 = search, 002 = write, 004 = read).
> + * Return 0 if permission is granted.
Aha. So every LS module knows about every single sysctl in the
kernel. Common, this is silly guys (and girls if there any)!
> + * @swapon:
> + * Check permission before enabling swapping to the file or block device
> + * identified by @swap.
> + * @swap contains the swap_info_struct structure for the swap file and device.
> + * Return 0 if permission is granted.
> + * @swapoff:
> + * Check permission before disabling swapping to the file or block device
> + * identified by @swap.
> + * @swap contains the swap_info_struct structure for the swap file and device.
> + * Return 0 if permission is granted.
You might be allowed to swapon but not swapoff?
> diff -Nru a/kernel/sys.c b/kernel/sys.c
> --- a/kernel/sys.c Thu Sep 26 13:23:55 2002
> +++ b/kernel/sys.c Thu Sep 26 13:23:55 2002
> @@ -349,11 +349,17 @@
> asmlinkage long sys_reboot(int magic1, int magic2, unsigned int cmd, void * arg)
> {
> char buffer[256];
> + int retval;
>
> /* We only trust the superuser with rebooting the system. */
> if (!capable(CAP_SYS_BOOT))
> return -EPERM;
>
> + retval = security_ops->reboot(cmd);
> + if (retval) {
> + return retval;
> + }
> +
What's the point of cmd here? Someone might be allowed to halt the
system but not reboot?
[don't of stubfs snipped]
> +static int cap_swapon (struct swap_info_struct *swap)
> +{
> + return 0;
> +}
> +
> +static int cap_swapoff (struct swap_info_struct *swap)
> +{
> + return 0;
> +}
Live would be a lot simple if an unimplemented op would behave
as returning zero..
Christoph (not speaking for SGI, just using the fastest mailserver)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/