Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1372105 > unrolled thread

Re: [RFC PATCH 11/12] certs: Add a secondary system keyring that can be added to dynamically [ver #3]

Started byMimi Zohar <zohar@linux.vnet.ibm.com>
First post2016-04-06 02:50 +0200
Last post2016-04-06 18:20 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [RFC PATCH 11/12] certs: Add a secondary system keyring that  can be added to dynamically [ver #3] Mimi Zohar <zohar@linux.vnet.ibm.com> - 2016-04-06 02:50 +0200
    Re: [RFC PATCH 11/12] certs: Add a secondary system keyring that can be added to dynamically [ver #3] David Howells <dhowells@redhat.com> - 2016-04-06 18:20 +0200

#1372105 — Re: [RFC PATCH 11/12] certs: Add a secondary system keyring that can be added to dynamically [ver #3]

FromMimi Zohar <zohar@linux.vnet.ibm.com>
Date2016-04-06 02:50 +0200
SubjectRe: [RFC PATCH 11/12] certs: Add a secondary system keyring that can be added to dynamically [ver #3]
Message-ID<rkJPs-3T2-9@gated-at.bofh.it>
On Wed, 2016-03-09 at 11:19 +0000, David Howells wrote:

> +#ifdef CONFIG_SECONDARY_TRUSTED_KEYRING
> +/**
> + * restrict_link_by_builtin_and_secondary_trusted - Restrict keyring
> + *   addition by both builtin and secondary keyrings
> + *
> + * Restrict the addition of keys into a keyring based on the key-to-be-added
> + * being vouched for by a key in either the built-in or the secondary system
> + * keyrings.
> + */
> +int restrict_link_by_builtin_and_secondary_trusted(
> +	struct key *keyring,
> +	const struct key_type *type,
> +	const union key_payload *payload)
> +{
> +	/* If we have a secondary trusted keyring, then that contains a link
> +	 * through to the builtin keyring and the search will follow that link.
> +	 */
> +	if (type == &key_type_keyring &&
> +	    keyring == secondary_trusted_keys &&
> +	    payload == &builtin_trusted_keys->payload)
> +		/* Allow the builtin keyring to be added to the secondary */
> +		return 0;
> +
> +	return restrict_link_by_signature(builtin_trusted_keys, type, payload);

Shouldn't thi be secondary_trusted_keys?

Mimi

> +}
> +#endif

[toc] | [next] | [standalone]


#1372645 — Re: [RFC PATCH 11/12] certs: Add a secondary system keyring that can be added to dynamically [ver #3]

FromDavid Howells <dhowells@redhat.com>
Date2016-04-06 18:20 +0200
SubjectRe: [RFC PATCH 11/12] certs: Add a secondary system keyring that can be added to dynamically [ver #3]
Message-ID<rkYls-6yQ-23@gated-at.bofh.it>
In reply to#1372105
Mimi Zohar <zohar@linux.vnet.ibm.com> wrote:

> > +	return restrict_link_by_signature(builtin_trusted_keys, type, payload);
> 
> Shouldn't thi be secondary_trusted_keys?

Yeah.  Good catch, thanks!

David

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web