# Cannot validate binary

**URL:** <https://forum.gitea.com/t/cannot-validate-binary/1528>\
**Category:** Install/Maintain/Configure\
**Created:** [September 30, 2019, 4:25am UTC](https://forum.gitea.com/t/cannot-validate-binary/1528 "2019-09-30T04:25:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![HarryTheBotter](https://avatars.discourse-cdn.com/v4/letter/h/839c29/32.png) [@HarryTheBotter](https://forum.gitea.com/u/HarryTheBotter)\
**Post date:** [September 30, 2019, 4:25am UTC](https://forum.gitea.com/t/cannot-validate-binary/1528/1 "2019-09-30T04:25:30Z")

</div>

As stated in

[https://docs.gitea.io/en-us/install-from-binary/](https://docs.gitea.io/en-us/install-from-binary/)

there’s a way to verify the binary. That’s waht I attempt here, but it fails.

On a linux box I do

```auto
wget -O gitea https://dl.gitea.io/gitea/1.9.3/gitea-1.9.3-linux-amd64

```

resulting in a gitea binary. When I try to verify it, I got to download the key first:

```auto
gpg --keyserver pgp.mit.edu --recv 7C9E68152594688862D62AF62D9AE806EC1592E2

```

I either get

gpg: keyserver receive failed: No data

Ok, keyserver not willing to respond. I’ll try again. When I finally succeed it says

gpg: key 2D9AE806EC1592E2: 5 signatures not checked due to missing keys  
gpg: key 2D9AE806EC1592E2: public key “Teabot [teabot@gitea.io](mailto:teabot@gitea.io)” imported  
gpg: no ultimately trusted keys found  
gpg: Total number processed: 1  
gpg: imported: 1

Sounds good, but there’s no keyfile writte to my directory?

1. The binary to verify I got from the download is named “gitea”, not “gitea-1.9.3-linux-amd64”? Is that ok?
2. There’s no keyfile “gitea-1.9.3-linux-amd64.asc” ?

Anyways. Do I have that key in my keyring now?

gpg --list-keys

```auto
uid [unknown] Teabot <teabot@gitea.io>
sub rsa4096 2018-06-24 [E] [expires: 2020-06-23]
sub rsa4096 2018-06-24 [S] [expires: 2020-06-26]

```

Ok, let’s export it and verify:

gpg --export -a “Teabot” \> public.key  
gpg --verify public.key gitea

```auto
gpg: verify signatures failed: Unexpected error

```

What’s wrong? I put down the whole process of how I obtained and exported the key, because I’m not too familiar with the process and the installation instructions cannot be followed through literally.

---

<div class="post-metadata">

**Author:** ![buddyspencer](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/buddyspencer/32/4770_2.png) [@buddyspencer](https://forum.gitea.com/u/buddyspencer)\
**Post date:** [October 1, 2019, 8:09am UTC](https://forum.gitea.com/t/cannot-validate-binary/1528/2 "2019-10-01T08:09:49Z")

</div>

> [@HarryTheBotter](#):
>
> wget -O gitea [https://dl.gitea.io/gitea/1.9.3/gitea-1.9.3-linux-amd64](https://dl.gitea.io/gitea/1.9.3/gitea-1.9.3-linux-amd64)

This is the reason why your file is named `gitea`. If you don’t use the `-O gitea` parameter, the binary is named as it should be.

Regarding the keyfile issue, I can’t really help out there because it seems that the server itself have troubles. It tried to search the key on [http://pgp.mit.edu](http://pgp.mit.edu/) but it fails with a 503 error.