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: Thu, 04 Dec 2014 13:02:55 +0000 From: David Howells <dhowells@...hat.com> To: Dmitry Kasatkin <d.kasatkin@...sung.com> Cc: dhowells@...hat.com, Vivek Goyal <vgoyal@...hat.com>, mmarek@...e.cz, rusty@...tcorp.com.au, keyrings@...ux-nfs.org, linux-security-module@...r.kernel.org, zohar@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH 1/5] X.509: Extract both parts of the AuthorityKeyIdentifier Dmitry Kasatkin <d.kasatkin@...sung.com> wrote: > >> - struct asymmetric_key_id *authority; /* Authority key identifier (optional) */ > >> + struct asymmetric_key_id *auth_id; /* CA AuthKeyId matching ->id (optional) */ > >> + struct asymmetric_key_id *auth_skid; /* CA AuthKeyId matching ->skid (optional) */ > > A very minor nit. It might help if we put additional comment to explain what > > auth_id and auth_skid are composed of (like other key ids). > > > > auth_id /* akid issuer + akid serial */ > > auth_skid /* issuer + akid keyid */ > > > > Thanks > > Vivek > > > > Right, > > David did not address this in his v2 patchset... I decided against changing them on the basis that I'd prefer to show what they match over the way they are fabricated. The id and skid members do show how they are fabricated. If you really want, I can show both - but my thought is that if you look at how AuthorityKeyIdentifier is constructed, you can work it out reasonably easily. 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/
Powered by blists - more mailing lists