linux-kernel - Re: [PATCH] Introduce is_owner_or_cap() to wrap CAP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070718171834.GA28855@vino.hallyn.com>
Date:	Wed, 18 Jul 2007 12:18:34 -0500
From:	"Serge E. Hallyn" <serge@...lyn.com>
To:	"Serge E. Hallyn" <serge@...lyn.com>
Cc:	Satyam Sharma <ssatyam@....iitk.ac.in>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Al Viro <viro@....linux.org.uk>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] Introduce is_owner_or_cap() to wrap CAP_FOWNER use with fsuid check

Quoting Serge E. Hallyn (serge@...lyn.com):
> Quoting Satyam Sharma (ssatyam@....iitk.ac.in):
> > From: Satyam Sharma <ssatyam@....iitk.ac.in>
> > 
> > [PATCH] Introduce is_owner_or_cap() to wrap CAP_FOWNER use with fsuid check
> > 
> > Introduce is_owner_or_cap() macro in fs.h, and convert over relevant
> > users to it. This is done because we want to avoid bugs in the future
> 
> I like the idea - it will make future user namespace/per-container
> capability patches much cleaner by localizing a lot of the changes.
> 
> (haven't tested the patch yet, but it looks trivial enough, and I will
> test later today)

tested fine for me.

thanks,
-serge
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/