[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1593182191.7381.11.camel@HansenPartnership.com>
Date: Fri, 26 Jun 2020 07:36:31 -0700
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
Cc: Jerry Snitselaar <jsnitsel@...hat.com>,
linux-integrity@...r.kernel.org,
"Ferry Toth :" <ferry.toth@...inga.info>,
Peter Huewe <peterhuewe@....de>,
Jason Gunthorpe <jgg@...pe.ca>, Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrew Morton <akpm@...l.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] tpm_tis: Remove the HID IFX0102
On Fri, 2020-06-26 at 16:15 +0300, Jarkko Sakkinen wrote:
> I have an obstacle with that.
>
> I lost my previous PGP key a year ago and created a new one, which is
> not trusted yet by anyone [*]. I've backed this up now and have it
> stored inside Nitrokey Pro 2 in order to prevent this happening
> again.
I wouldn't do that. If the nitro key gets lost or breaks, you'll be in
the same position. Best practice is to have your key offline somewhere
in a secure vault (like an encrypted USB key in a bank vault) so you
can restore in case of loss and then present inside a token (so I use
the TPM2 for mine).
> Now the problem is that in order to get a kernel.org account, I need
> to be in the web of trust of the kernel maintainers.
>
> I can request an accunt only after I see face to face another kernel
> maintainers, so that I can proof that I am I.
>
> [*] http://keys.gnupg.net/pks/lookup?op=get&search=0x3AB05486C7752FE1
Well, I would sign this and send it back to you, except I can't. The
verification procedures require an encrypted email and you don't have a
working encryption key:
gpg --export -a 3AB05486C7752FE1 | gpg --encrypt -r 3AB05486C7752FE1 -a --output 3AB05486C7752FE1.gpg
gpg: 3AB05486C7752FE1: skipped: Unusable public key
gpg: [stdin]: encryption failed: Unusable public key
The reason is your main key is certification only (as is should be):
pub rsa4096/3AB05486C7752FE1
created: 2019-06-24 expires: 2023-06-24 usage: C
trust: unknown validity: full
but your only encryption subkey is revoked:
sub rsa2048/3A4EC6E56FDD3158
created: 2019-06-25 revoked: 2019-10-22 usage: E
You seem to have only one unrevoked, unexpired subkey which is an
authentication one, so you wouldn't even be able to sign with that key:
sub rsa2048/962F0565523E5DC5
created: 2019-06-26 expires: 2021-06-25 usage: A
James
Powered by blists - more mailing lists