question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

gpg: Can't check signature: No public key, keyserver search failed: Not found

See original GitHub issue

From https://github.com/iancoleman/bip39/releases https://github.com/iancoleman/bip39/releases/download/0.5.4/bip39-standalone.html https://github.com/iancoleman/bip39/releases/download/0.5.4/signature.txt.asc

.../iancoleman/bip39 $ gpg --verify signature.txt.asc
gpg: Signature made 2021-10-18 19:07:56 -0400 EDT
gpg:                using RSA key 5AD5C88083708E93A2966FF49FF1B58CA7B9E6A5
gpg:                issuer "ian@iancoleman.io"
gpg: Can't check signature: No public key

.../iancoleman/bip39 $ gpg --search A7B9E6A5
gpg: data source: https://162.213.33.8:443
gpg: key "A7B9E6A5" not found on keyserver
gpg: keyserver search failed: Not found

.../iancoleman/bip39 $ gpg --search 0xA7B9E6A5
gpg: data source: https://162.213.33.8:443
gpg: key "0xA7B9E6A5" not found on keyserver
gpg: keyserver search failed: Not found

.../iancoleman/bip39 $ gpg --search ian@iancoleman.io
gpg: data source: https://162.213.33.8:443
(1)     Ian Coleman <ian@iancoleman.io>
        Ian Coleman <coleman.ian@gmail.com>
          4096 bit RSA key B89A317AB798EB23, created: 2017-07-18
Keys 1-1 of 1 for "ian@iancoleman.io".  Enter number(s), N)ext, or Q)uit > 1
gpg: key B89A317AB798EB23: "Ian Coleman <ian@iancoleman.io>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

.../iancoleman/bip39 $ gpg --verify signature.txt.asc
gpg: Signature made 2021-10-18 19:07:56 -0400 EDT
gpg:                using RSA key 5AD5C88083708E93A2966FF49FF1B58CA7B9E6A5
gpg:                issuer "ian@iancoleman.io"
gpg: Can't check signature: No public key

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:9 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
petjalcommented, Oct 21, 2021

diff_bip39-standalone_0.5.3_0.5.4.html.txt

Doesn’t look like Ian’s kidnappers have done anything too malicious between 0.5.3 and 0.5.4.

0reactions
petjalcommented, Oct 21, 2021

(reminding myself that I should probably find or re-create my revocation certificate…found it, phew) image

Read more comments on GitHub >

github_iconTop Results From Across the Web

Unable to verify the kernel signature "gpg: Can't check ...
In order to compile a new kernel on my Debian jessie, I am trying to verify the GPG key , following ...
Read more >
GPG can't check signature - Ask Ubuntu
I believe the conventional solution is to install the GnuPG keys of Debian Developers package: sudo apt-get install debian-keyring.
Read more >
[SOLVED] Cannot Verify ISO GPG Says No Public Key ...
gpg : w/o user IDs: 1 gpg: Can't check signature: No public key. I am running this in my Downloads directory, where the...
Read more >
gpg: Can't check signature: No public key - Linux Mint Forums
1. Download the public key, which you've done. 2. Import the key into your keyring: gpg --import 5B7CC9A2.asc
Read more >
aptly mirror – gpgv: Can't check signature: public key not found
you must import the GPG key from your old server in trustedkeys.gpg (even if you have already imported it in the new server...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found