Trying to verify signature of Wasabi-1.1.12.3.deb package but it won´t find the file (THE FILE IS THERE)

Question

Ey there,

So, i have been trying for hours to install wasabi in Ubuntu without success. Having downloaded the files and following the guide i get to the point of not being able to verify the freaking signature.

I write the following command (taken from the installation guide i'm following at http://wasabiwallet.io):

gpg --verify Wasabi-1.1.12.3.deb

and the terminal tells me there is no such file (but the files is there... i'm sure

The text i get back is:

gpg: can´t open 'Wasabi-1.1.12.3.deb.asc: No such file or directory
gpg: verify signatures failed: No such file or directory

And so... I'm lost. I googled but did not find anything helpful. I just spend a couple days to install the VPN (a couple weeks ago) and remember my ex flatmate who was a computer wizard and still was to be seen losing his hair with Ubuntu once in a while... and i wonder why i even try to use it XD.

I hope someone here can help me.

TO BE CLEAR:

-Followed the Guide's steps

1. .deb file downloaded
2. .deb.asc file downloaded in same folder
3. PGP.txt imported

I give gpg --verify Wasabi-1.1.12.3.deb.asc (yes, i checked, File name is correct)

I receive:

gpg: can´t open 'Wasabi-1.1.12.3.deb.asc: No such file or directory
gpg: verify signatures failed: No such file or directory

Answer 1

Silly question, but you did read step 2 at least twice, right?

There is the .deb file and, under the green button, a blue "Signature" link that points to the .asc file. Both will need to be located in the same directory.

-rw-rw-r-- 1 jason jason 69997812 12月  7 23:22 Wasabi-1.1.12.3.deb
-rw-rw-r-- 1 jason jason      499 12月  7 23:23 Wasabi-1.1.12.3.deb.asc

Now you can then perform Step 3 and verify the .deb:

$ gpg --verify Wasabi-1.1.12.3.deb.asc

gpg: assuming signed data in 'Wasabi-1.1.12.3.deb'
gpg: Signature made 2020年12月07日 23時22分15秒 JST
gpg:                using RSA key 6FB3872B5D42292F59920797856348328949861E
gpg: Can't check signature: No public key

So long as the RSA key matches what is listed on the website, you can move on to the next step.