Linux backports project
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: backports@vger.kernel.org
Subject: [Bug 105921] New: Backport releases GPG public key unavailable
Date: Tue, 13 Oct 2015 19:25:22 +0000	[thread overview]
Message-ID: <bug-105921-58281@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=105921

            Bug ID: 105921
           Summary: Backport releases GPG public key unavailable
           Product: Backports project
           Version: unspecified
    Kernel Version: 3.10.0-229.14.1.el7.x86_64 (Centos 7)
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Backports
          Assignee: backports@vger.kernel.org
          Reporter: bugzilla.kernel.org@gdavis.com
        Regression: No

The GPG public key is needed to verify the releases at:
http://drvbp1.linux-foundation.org/~mcgrof/rel-html/backports/

which is the download page referenced at:
https://backports.wiki.kernel.org/index.php/Main_Page

For instance, the release:
backports-3.19-rc1-1
is signed with key id 583D1332,
which doesn't seem to exist pgp.mit.edu or keyserver.pgp.com or
pool.sks-keyservers.net.

Various google searches did not yield any documentation on accessing the public
key.

-- 
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe backports" in

             reply	other threads:[~2015-10-13 19:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13 19:25 bugzilla-daemon [this message]
2015-10-13 20:21 ` [Bug 105921] Backport releases GPG public key unavailable bugzilla-daemon
2015-10-13 20:45 ` bugzilla-daemon
2015-10-13 20:52 ` bugzilla-daemon

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=bug-105921-58281@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=backports@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox