All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Tricca <philip.b.tricca at intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] Some issues with tpm2-tss, tpm2-tools regarding packaging
Date: Thu, 22 Feb 2018 09:14:42 -0800	[thread overview]
Message-ID: <20180222171442.GB6409@intel.com> (raw)
In-Reply-To: 880372d3-738f-c18c-8409-f2bffa8fff27@redhat.com

[-- Attachment #1: Type: text/plain, Size: 1604 bytes --]

Javier,

On Thu, Feb 22, 2018 at 03:09:33PM +0100, Javier Martinez Canillas wrote:
> On 02/22/2018 01:34 PM, Matthias Gerstner wrote:

snip

> > - I wanted to verify the GPG signature of the tpm2-tools distribution
> >   tarball tpm2-tools-3.0.3.tar.gz, but cannot seem to find the matching
> >   public key 0x6DE2E9078E1F50C1 on the public key servers.
> >
> 
> Indeed. The same problem happens with tpm2-tss, so I guess neither Bill nor Philip
> have pushed their public GPG keys to a key server:
> 
> $ gpg --verify tpm2-tss-1.3.0.tar.gz.asc tpm2-tss-1.3.0.tar.gz
> gpg: Signature made Fri 08 Dec 2017 02:12:30 AM CET using RSA key ID C2E1D3BA
> gpg: Can't check signature: public key not found

I don't know how you've got gpg configured but my signing key is up on
the MIT PGP key server. Try:

gpg --keyserver hkp://pgp.mit.edu --search-keys 0xc2e1d3ba 

When I first started using PGP the MIT key server was the only one that
could cope with subkeys (0xc2e1d3ba is a subkey of 0x43dec7c3). That may
have changed since but I've never had cause to push my key to other
servers. What's the default key server for your distro? Do we need to
put our keys there too?

> $ gpg --verify tpm2-tools-3.0.3.tar.gz.asc tpm2-tools-3.0.3.tar.gz                    
> gpg: Signature made Mon 15 Jan 2018 11:08:10 PM CET using RSA key ID 8E1F50C1                                    
> gpg: Can't check signature: public key not found

I couldn't find Bills key either. I vaguely remember having a discussion
about this a while back but don't remember the resolution.

Philip

             reply	other threads:[~2018-02-22 17:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22 17:14 Philip Tricca [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-02-22 20:45 [tpm2] Some issues with tpm2-tss, tpm2-tools regarding packaging Roberts, William C
2018-02-22 20:31 Javier Martinez Canillas
2018-02-22 16:53 Scheie, Peter M
2018-02-22 16:47 Scheie, Peter M
2018-02-22 16:41 Philip Tricca
2018-02-22 15:06 Javier Martinez Canillas
2018-02-22 14:46 Matthias Gerstner
2018-02-22 14:09 Javier Martinez Canillas
2018-02-22 12:34 Matthias Gerstner

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=20180222171442.GB6409@intel.com \
    --to=tpm2@lists.01.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.