Verification fail #1116
Comments
|
The same for me Also tried to import key, but had no success: At the end got - "gpg: verify signatures failed: Unexpected error" |
|
ok, looks like this is my mistake, I've tried to use Public Key instead of signature from here https://github.com/bisq-network/exchange/releases/tag/v0.6.2 |
|
ManfredKarrer : "Bisq-0.6.2.dmg.asc" doesn't provide any signatures upon GPG keychain sign verification on mac os x Please just confirm that it's signed instead of closing the topic. |
|
Just checked again and is valid for me: gpg --digest-algo SHA256 --verify Bisq-0.6.2.dmg{.asc*,} |
|
I get this hash 433d2636b73a0857433ce5c045ef8097a79e7cb4e899c3c5e8543288740d4e0a
for the .dmg file
running it manually through terminal.
But verifying the sign through GPG keychain, there's no signature showing. Im a novice so can't say why. Just get somebody else to verify it and then fine.
Again it's probably me, just nice to double check again.
Sent with [ProtonMail](https://protonmail.com) Secure Email.
… -------- Original Message --------
Subject: Re: [bisq-network/exchange] Verification fail (#1116)
Local Time: January 3, 2018 11:00 PM
UTC Time: January 3, 2018 10:00 PM
From: ***@***.***
To: bisq-network/exchange ***@***.***>
HanZeno ***@***.***>, Author ***@***.***>
Reopened [#1116](#1116).
—
You are receiving this because you authored the thread.
Reply to this email directly, [view it on GitHub](#1116 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AhLPRLs3yAT5vf8Cexf_4GxymlPkPLFYks5tG_hwgaJpZM4RLmEX).
|
|
That is a different hash I get. How are you creating it? |
|
Yes exactly:
Bisq-0.6.1.dmg
$ shasum -a 256 /Users/naturalenergy/Downloads/Bisq-0.6.1.dmg
433d2636b73a0857433ce5c045ef8097a79e7cb4e899c3c5e8543288740d4e0a
Bisq-0.6.2.dmg (just redownloaded)
$ shasum -a 256 /Users/naturalenergy/Downloads/Bisq-0.6.2.dmg
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Sent with [ProtonMail](https://protonmail.com) Secure Email.
… -------- Original Message --------
Subject: Re: [bisq-network/exchange] Verification fail (#1116)
Local Time: January 3, 2018 11:49 PM
UTC Time: January 3, 2018 10:49 PM
From: ***@***.***
To: bisq-network/exchange ***@***.***>
HanZeno ***@***.***>, Author ***@***.***>
That is a different hash I get. How are you creatin git?
$ shasum -a 256 Bisq-0.6.2.dmg
4b774299d0fe8f2da5e3bd09b90bc1d72d21f203dadc80fdc3c5475e1f8cb3eb
—
You are receiving this because you authored the thread.
Reply to this email directly, [view it on GitHub](#1116 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AhLPROEJFe8An_uGJXrwrYkEeVDJPIQ6ks5tHAQRgaJpZM4RLmEX).
|
|
You downloaded from https://github.com/bisq-network/exchange/releases/tag/v0.6.2? |
|
Ps: Don't run the file if the hash does not match 4b774299d0fe8f2da5e3bd09b90bc1d72d21f203dadc80fdc3c5475e1f8cb3eb |
|
You downloaded from https://github.com/bisq-network/exchange/releases/tag/v0.6.2?
YES
… I downloaded again from https://bisq.network/downloads/ and got the same hash as above.
Do you have a proxy or anything or VPS?
USUALLY YES, BUT NOT THE REDOWNLOAD I JUST DID OF V0.6.2
Can you try from another internet connection or computer?
WILL TRY AGAIN TMRW FROM ANOTHER COMPUTER AND LET YOU KNOW
Please let me know once you found out what caused the issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, [view it on GitHub](#1116 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AhLPRDqW9reT-MQ8G8WzkCCZLLAuojxKks5tHA28gaJpZM4RLmEX).
|
|
I just downloaded again from https://github.com/bisq-network/exchange/releases/tag/v0.6.2 as well as from the bisq.network download page (links to the same URL). Both result in hash: 4b774299d0fe8f2da5e3bd09b90bc1d72d21f203dadc80fdc3c5475e1f8cb3eb |
|
Manfred,
4b774299d0fe8f2da5e3bd09b90bc1d72d21f203dadc80fdc3c5475e1f8cb3eb
got the correct hash now. New download, new connection, from github.
Sent with [ProtonMail](https://protonmail.com) Secure Email.
… -------- Original Message --------
Subject: Re: [bisq-network/exchange] Verification fail (#1116)
Local Time: January 4, 2018 12:39 AM
UTC Time: January 3, 2018 11:39 PM
From: ***@***.***
To: bisq-network/exchange ***@***.***>
HanZeno ***@***.***>, Author ***@***.***>
Yes just downloaded again from https://github.com/bisq-network/exchange/releases/tag/v0.6.2 as well as from the bisq.network download page (links to the same URL). Both result in hash: 4b774299d0fe8f2da5e3bd09b90bc1d72d21f203dadc80fdc3c5475e1f8cb3eb
—
You are receiving this because you authored the thread.
Reply to this email directly, [view it on GitHub](#1116 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AhLPRI71f8Qvpu63mlguhxhXW068NsGFks5tHA-6gaJpZM4RLmEX).
|
|
Did you find out what has changed? Check your internet connection to not be MITM attacked... |
|
1) am not too tech savy, so I calculated the hash wrong by not being in the right directory I think.
$ shasum a- 256 from standard directory, not "Downloads", it gives a different hash..
2) just now with GPG I just got verification of the Bisq-0.6.2.dmg.asc file for the first time. Not sure what changed. Maybe restarting both GPG/computer
So everything seems to be ok, sorry for bothering you.
Anyway it's still too complicated for ordinary people to verify and get going .. and super important for anyone going on a peer to peer exchange not to have a sniffing crack on the installed version. Would be great if this verification process could be simpler. Decentralised exchanges will have a great future. I believe the centralised are going to have a MtGox repeat either by printing endless tethers, being shut down or simply exit scams (etc).
Looking forward anyway to get going with Bisq and spread the word! Keep up the great work
Greets!
[Skærmbillede 2018-01-04 kl. 21.32.45.png]
Sent with [ProtonMail](https://protonmail.com) Secure Email.
… -------- Original Message --------
Subject: Re: [bisq-network/exchange] Verification fail (#1116)
Local Time: January 4, 2018 8:24 PM
UTC Time: January 4, 2018 7:24 PM
From: ***@***.***
To: bisq-network/exchange ***@***.***>
HanZeno ***@***.***>, Author ***@***.***>
Did you find out what has changed? Check your internet connection to not be MITM attacked...
—
You are receiving this because you authored the thread.
Reply to this email directly, [view it on GitHub](#1116 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AhLPRDlJsqivU8PSaGtuGdtJHa3szPsmks5tHSTJgaJpZM4RLmEX).
|
|
Ah good it was nothing serious! |
|
Hi Manfred,
I had a idea today, qua protecting the market/adoption in BTC throughout the next run up from single point of exchange failures (Bitmex..)
What would it cost for "the team" to develop a derivative platform on top of Bisq code already in place?
Meaning you have an interface like Bitmex but the core technology/software model is based upon Bisq. We'd have to brainstorm about if it could be done, like democratisation of an insurance fund, multi sigged etc
Protecting people from system due liquidations will be important in the sense they're playing a major part in the inflationary impact of shorting leverage (Bitmex printing x100 leverage synthetic XBT .. and vice versa doing their system overload and barting to shakeout any pressure of people longing).
We obviously would need to exchange more ideas and if it could at all be technically done etc
Loving Bisq so far..
Han
Sent with [ProtonMail](https://protonmail.com) Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
…On Thursday, 4 January 2018 22:02, Manfred Karrer ***@***.***> wrote:
Ah good it was nothing serious!
I understand that for not tech-savvy people such things are hard, because of that we have added the in-app-downloader which does all that download and sig checks in the app. Then only the first time download need to be done manually.
—
You are receiving this because you authored the thread.
Reply to this email directly, [view it on GitHub](#1116 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AhLPRF72cUr8lU-FH-tMmT6NCat7kn-tks5tHTxfgaJpZM4RLmEX).
|
had gpg verification fail of Bisq-0.6.2.dmg.asc (F379A1C6.asc) today. Im noob at GPG so probably it's just me, but please have a look. Also maybe the verification guide could be written better.
The text was updated successfully, but these errors were encountered: