linux-kernel - Re: [PATCH] Allow clients to set key perms in key_create_or

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <25831.1204883318@redhat.com>
Date:	Fri, 07 Mar 2008 09:48:38 +0000
From:	David Howells <dhowells@...hat.com>
To:	Arun Raghavan <arunsr@....iitk.ac.in>
Cc:	dhowells@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Allow clients to set key perms in key_create_or_update()

Arun Raghavan <arunsr@....iitk.ac.in> wrote:

> The key_create_or_update() function provided by the keyring code has a default
> set of permissions that are always applied to the key when created. This might
> not be desirable to all clients.
> 
> Here's a patch that adds a "perm" parameter to the function to address this,
> which can be set to KEY_PERM_UNDEF to revert to the current behaviour.

I'll get to this shortly.  I'm just creating another keyrings patch, so I'll
look at yours afterwards.

David
--
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/