linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: Zoran Markovic <zmarkovic@sierrawireless.com>,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: James Morris <jmorris@namei.org>, "Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: [RFC PATCH] smack: fix access permissions for keyring
Date: Tue, 27 Nov 2018 12:18:54 -0800	[thread overview]
Message-ID: <922bb08b-60e5-d43a-d48e-5b54575efa8b@schaufler-ca.com> (raw)
In-Reply-To: <1539818744-30912-1-git-send-email-zmarkovic@sierrawireless.com>

On 10/17/2018 4:25 PM, Zoran Markovic wrote:
> Function smack_key_permission() only issues smack requests for the
> following operations:
>  - KEY_NEED_READ (issues MAY_READ)
>  - KEY_NEED_WRITE (issues MAY_WRITE)
>  - KEY_NEED_LINK (issues MAY_WRITE)
>  - KEY_NEED_SETATTR (issues MAY_WRITE)
> A blank smack request is issued in all other cases, resulting in
> smack access being granted if there is any rule defined between
> subject and object, or denied with -EACCES otherwise.
>
> Request MAY_READ access for KEY_NEED_SEARCH and KEY_NEED_VIEW.
> Fix the logic in the unlikely case when both MAY_READ and
> MAY_WRITE are needed. Validate access permission field for valid
> contents.

Do you have any test cases for this?

> Signed-off-by: Zoran Markovic <zmarkovic@sierrawireless.com>
> Cc: Casey Schaufler <casey@schaufler-ca.com>
> Cc: James Morris <jmorris@namei.org>
> Cc: "Serge E. Hallyn" <serge@hallyn.com>
> ---
>  security/smack/smack_lsm.c | 12 +++++++++---
>  1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/security/smack/smack_lsm.c b/security/smack/smack_lsm.c
> index 340fc30..77e405f 100644
> --- a/security/smack/smack_lsm.c
> +++ b/security/smack/smack_lsm.c
> @@ -4326,6 +4326,12 @@ static int smack_key_permission(key_ref_t key_ref,
>  	int request = 0;
>  	int rc;
>  
> +	/*
> +	 * Validate requested permissions
> +	 */
> +	if (perm & ~KEY_NEED_ALL)
> +		return -EINVAL;
> +
>  	keyp = key_ref_to_ptr(key_ref);
>  	if (keyp == NULL)
>  		return -EINVAL;
> @@ -4349,10 +4355,10 @@ static int smack_key_permission(key_ref_t key_ref,
>  	ad.a.u.key_struct.key = keyp->serial;
>  	ad.a.u.key_struct.key_desc = keyp->description;
>  #endif
> -	if (perm & KEY_NEED_READ)
> -		request = MAY_READ;
> +	if (perm & (KEY_NEED_READ | KEY_NEED_SEARCH | KEY_NEED_VIEW))
> +		request |= MAY_READ;
>  	if (perm & (KEY_NEED_WRITE | KEY_NEED_LINK | KEY_NEED_SETATTR))
> -		request = MAY_WRITE;
> +		request |= MAY_WRITE;
>  	rc = smk_access(tkp, keyp->security, request, &ad);
>  	rc = smk_bu_note("key access", tkp, keyp->security, request, rc);
>  	return rc;


      reply	other threads:[~2018-11-27 20:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17 23:25 [RFC PATCH] smack: fix access permissions for keyring Zoran Markovic
2018-11-27 20:18 ` Casey Schaufler [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=922bb08b-60e5-d43a-d48e-5b54575efa8b@schaufler-ca.com \
    --to=casey@schaufler-ca.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=serge@hallyn.com \
    --cc=zmarkovic@sierrawireless.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).