GPG Server Error when trying to update RetroPie packages

va_lemon

@BuZz If I go to keyserver.ubuntu.com and search for key DC9D77FF8208FFC51D8F50CCF1B030906A3B0D31 it says not found.

mitu

It works if you search by 0x<hash>: http://keyserver.ubuntu.com/pks/lookup?search=0xDC9D77FF8208FFC51D8F50CCF1B030906A3B0D31&fingerprint=on&exact=on&op=index
You can get the key from the search and import it locally, since it looks like your connection to the keyserver is not working properly.

va_lemon

@mitu @BuZz Thanks to both of you for your incredible help. I imported the RetroPie public key which I was able to get by searching for 0xDC9D77FF8208FFC51D8F50CCF1B030906A3B0D31 on keyserver.ubuntu.com. The RetroPie Setup script is updating packages properly now.

Now I'm curious as to why I'm able to access keyserver.ubuntu.com and search for the key from my desktop browser but get an error when using gpg on the Pi.

mitu

@va_lemon said in GPG Server Error when trying to update RetroPie packages:

Now I'm curious as to why I'm able to access keyserver.ubuntu.com and search for the key from my desktop browser but get an error when using gpg on the Pi.

They're using different protocols - your browser is using HTTP(s), while gpg uses HKP (a similar protocol, but on a different port).

I wonder if

sudo gpg --keyserver hkps://keyserver.ubuntu.com:443 --recv-keys DC9D77FF8208FFC51D8F50CCF1B030906A3B0D31

would work for you ?

pumrum

I ran into a similar issue today with a fresh install of RetroPie 4.6 on a RPi 3. I run a completely restricted iptables firewall, only allowing the Pi to connect on a small number of outgoing and incoming ports (22, 53, 68, 80, 123, 443). I found that I had to open port 11371 to allow the RetroPie setup script to update, which then allowed it to connect to the key server. I've been using the same firewall configuration for a few years on earlier versions of RetroPie without issues, but I found that I just also started to encounter the issue on my RetroPie 4.5 build, which has been in use since March 2020 without issue. Update problem probably started within the last 1-2 months.

I think that begs the question -- did the retropie script get changed to not use port 80 for retrieving GPG keys? If so, could we politely request that it be changed back, unless there's a compelling reason to use the default port. It's always best to try to minimize the number of holes you need to poke through your firewall, and I suspect there are going to be a handful of people who may not even be allowed to connect out on port 11371.

mitu

@pumrum said in GPG Server Error when trying to update RetroPie packages:

I think that begs the question -- did the retropie script get changed to not use port 80 for retrieving GPG keys?

The signing and verification of binary packages (with GPG) has been added recently - starting with version 4.6.8.

BuZz

I'll adjust it to use port 80

BuZz

This is now done.

retronaff

I'm having this issue currently. Cannot authenticate the GPG keys when I try to run /retropie_packages.sh sd12 install_bin

I get a 'gpgL no valid OpenGPP data found.
gpg: the signature could not be verified.

I just want to play super mario =O

mitu

@retronaff This is not the same error - it looks like a corrupted/wrong downloaded file.
Please open a separate topic and provide the info asked in https://retropie.org.uk/forum/topic/3/read-this-first.

Btw, you can play Super Mario without updating RetroPie, the necessary emulators are already installed on the image.

retronaff

@mitu when i run emulationstation i get this error ;no available video device' ' error initializing sdl!'