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
| ||
|
Date: Fri, 03 Oct 2014 17:00:04 +0300 From: Dmitry Kasatkin <d.kasatkin@...sung.com> To: David Howells <dhowells@...hat.com> Cc: zohar@...ux.vnet.ibm.com, linux-ima-devel@...ts.sourceforge.net, linux-security-module@...r.kernel.org, jmorris@...ei.org, rusty@...tcorp.com.au, keyrings@...ux-nfs.org, linux-kernel@...r.kernel.org, dmitry.kasatkin@...il.com Subject: Re: [PATCH 3/4] module: search the key only by keyid On 03/10/14 16:40, David Howells wrote: > Dmitry Kasatkin <d.kasatkin@...sung.com> wrote: > >> BTW. But actually why signer is needed to find the key? >> Every key has unique fingerprint. > The SKID is by no means guaranteed unique, is not mandatory and has no defined > algorithm for generating it. SKID is unique. SKID == SHA1(PK) I understand that it may be missing for someone. But if it presents in the certificate it should not be a problem... >> Or you say that different certificates might have the same PK? >> What I would consider strange. But anyway, if PK is the same, then >> verification succeed. > Do note: We *do* need to get away from using SKIDs. We have situations where > we have to use a key that doesn't have one. > > David I understand that... What I claim is that if there is a SKID, it is unique and enough to identify certificate in the keyring... Integrity subsystem uses partial SKID and it MUST NOT be broken for compatibility. Dmitry -- 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/
Powered by blists - more mailing lists