eighthave
commented
10 years ago You need to import that key into your local gpg keyring in order for gpg to check signatures. This is what I'm seeing:
$ gpg --recv-keys FE4B2BDA
gpg: requesting key FE4B2BDA from hkps server hkps.pool.sks-keyservers.net
gpg: key FE4B2BDA: public key "Michael Shuler <michael@pbandjelly.org>" imported
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 5 signed: 47 trust: 0-, 0q, 0n, 0m, 0f, 5u
gpg: depth: 1 valid: 47 signed: 133 trust: 20-, 0q, 0n, 16m, 11f, 0u
gpg: depth: 2 valid: 76 signed: 200 trust: 74-, 0q, 0n, 2m, 0f, 0u
gpg: next trustdb check due at 2014-04-01
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
$ gpg --fingerprint FE4B2BDA
pub 4096R/FE4B2BDA 2009-07-15
Key fingerprint = A26E 528B 271F 19B9 E5D8 E19E A278 B781 FE4B 2BDA
uid Michael Shuler <michael@pbandjelly.org>
uid Michael Shuler <mshuler@gmail.com>
sub 4096R/25A883ED 2009-07-15On 03/30/2014 09:48 AM, Mark Murphy wrote:
I cloned the repo, ran
git submodule update --init --recursive, then tried to runmake. That gave me:cd ca-certificates && git verify-tag `git describe --abbrev=0 --tags` gpg: Signature made Sun 20 Jan 2013 07:47:44 PM EST using RSA key ID FE4B2BDA gpg: Can't check signature: public key not found make: *** [debian-verify] Error 1Is there some other preparation step needed to build the BKS store via
make?Thanks!
Reply to this email directly or view it on GitHub: https://github.com/guardianproject/cacert/issues/9
PGP fingerprint: 5E61 C878 0F86 295C E17D 8677 9F0F E587 374B BE81
I cloned the repo, ran
git submodule update --init --recursive, then tried to runmake. That gave me:Is there some other preparation step needed to build the BKS store via
make?Thanks!