From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Jerry Snitselaar <jsnitsel@redhat.com>,
linux-integrity@vger.kernel.org,
"Ferry Toth :" <ferry.toth@elsinga.info>,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@osdl.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] tpm_tis: Remove the HID IFX0102
Date: Fri, 26 Jun 2020 07:36:31 -0700 [thread overview]
Message-ID: <1593182191.7381.11.camel@HansenPartnership.com> (raw)
In-Reply-To: <20200626131523.GB7853@linux.intel.com>
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
next prev parent reply other threads:[~2020-06-26 14:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 2:31 [PATCH v2] tpm_tis: Remove the HID IFX0102 Jarkko Sakkinen
2020-06-25 6:21 ` Jerry Snitselaar
2020-06-25 21:02 ` Jarkko Sakkinen
2020-06-25 21:19 ` Jerry Snitselaar
2020-06-25 21:23 ` James Bottomley
2020-06-26 13:15 ` Jarkko Sakkinen
2020-06-26 14:36 ` James Bottomley [this message]
2020-07-02 23:37 ` Jarkko Sakkinen
2020-06-26 13:08 ` Jarkko Sakkinen
2020-06-30 19:15 ` Jerry Snitselaar
2020-07-02 23:38 ` Jarkko Sakkinen
2020-07-06 11:46 ` Peter.Huewe
2020-07-06 14:00 ` Jarkko Sakkinen
2020-07-06 14:43 ` Jarkko Sakkinen
2020-07-06 14:47 ` Jarkko Sakkinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1593182191.7381.11.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@osdl.org \
--cc=arnd@arndb.de \
--cc=ferry.toth@elsinga.info \
--cc=gregkh@linuxfoundation.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=jsnitsel@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).