You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: Installation » [SOLVED] How to report "gpg: BAD signature" » 2025-10-04 01:10:29
Yes, WSL2. That could be doing it. Thank you for checking that.
#2 Re: Installation » [SOLVED] How to report "gpg: BAD signature" » 2025-10-04 00:03:46
Thank you for the advice. I have now followed both steps.
The key refresh for key 680B5A1F661ECDBC showed 'not changed'.
The sha256sum of the ISOs match the checksum (722af7905595d9a1417f48f783d43dd40fe7da7a2e1d7998a8ea47df2d26941b).
Since the file is definitely correct, the 'BAD signature' error (from key 680B5A1F661ECDBC belonging to Ralph Ronnquist) indicates a problem with the signature file itself.
I am happy, because I have my ISO, so I can mark this solved unless you'd rather leave it open or if you want more info.
#3 Installation » [SOLVED] How to report "gpg: BAD signature" » 2025-10-03 21:48:36
- hellomello
- Replies: 5
I downloaded the daedalus file devuan_daedalus_5.0.1_amd64_netinstall.iso from two different servers (https servers) and got a Bad signature both times on the file, but I don't know how to put it into the bug reporting system since there is no package name. I think the bug report system might just kick it out if I report it without a package name. Is that correct? If not what package should I use, or how do I report it? Thanks.
Pages: 1
Board footer
