linux-kernel - Re: [PATCH 0/4] KEYS: validate key trust with owner and builtin keys only

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]

Date:	Wed, 11 Jun 2014 16:49:53 -0400
From:	Mimi Zohar <zohar@...ux.vnet.ibm.com>
To:	Dmitry Kasatkin <d.kasatkin@...sung.com>
Cc:	dhowells@...hat.com, jwboyer@...hat.com, keyrings@...ux-nfs.org,
	linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org, dmitry.kasatkin@...il.com
Subject: Re: [PATCH 0/4] KEYS: validate key trust with owner and builtin
 keys only

On Tue, 2014-06-10 at 15:49 +0300, Dmitry Kasatkin wrote: 
> On 10/06/14 15:45, Mimi Zohar wrote:
> > On Tue, 2014-06-10 at 11:48 +0300, Dmitry Kasatkin wrote: 
> >> Hi Mimi,
> >>
> >> As you asked ofline , here is possible equivalent and simpler alternative
> >> patches not requiring to have additional keyring.
> > Please indicate which branch these patches apply to.
> >
> > thanks,
> >
> > Mimi
> >
> >
> 
> on the top of your tree #next-trusted-keys-experimental, excluding 1/4
> patch, which is yours.
> I included it by mistake because patches were on the top of that and I
> used HEAD~3 instead of HEAD~2 to send them...

This patch set removes the separate 'owner' trusted keyring.  Please
rebase your patches without the HEAD patch - "f5b4ced KEYS: define an
owner trusted keyring" and re-post.

thanks,

Mimi


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