The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AA8E81B4331F7F50 NO_PUBKEY 112695A0E562B32A

Hallo,

I had to rebuilt my pi OMV and I am stuck to a strange problem, which I had faced before but have no clue as how I got over it.

When I am trying to update I get erros such as "The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AA8E81B4331F7F50 NO_PUBKEY 112695A0E562B32A"

I check the /etc/apt/source.list.d and I found 2 more files than my main OMV system. Deleting those 2 files solved the problem but I do not know if they are needed in the first place or not:

openmediavault-kernel-backports.list

openmediavault-os-security

I followed some suggestions like uninstalling / reinstall omv extras but that did not fixed it

Zitat von gderf

Try running the following command in the shell:

Code

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 112695A0E562B32A

Not working.... getting another error :

Executing: /tmp/apt-key-gpghome.I1yDbwJDRK/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys 112695A0E562B32A

gpg: keyserver receive failed: Server indicated a failure

Zitat von gderf

Try it again because it worked for me, twice now.

Code

fred@omv:~$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 112695A0E562B32A
[sudo] password for fred: 
Executing: /tmp/apt-key-gpghome.l1XZPBAwYo/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys 112695A0E562B32A
gpg: key 4DFAB270CAA96DFA: "Debian Security Archive Automatic Signing Key (10/buster) <ftpmaster@debian.org>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
fred@omv:~$ 

Well, I did many time.... no luck. Checked DNS and resolution seemed ok. Use other server and still get the same problem.

Zitat von ryecoaaron

The install script is supposed to add those keys. So, either your system is reporting that it is not Raspbian or your network is blocking the hkp:// protocol. Based on the posts here, I'm guessing the latter but I will still check to see if RaspberryPi OS is not reporting as raspbian anymore.

Well..... I have reinstalled it in the meanwhile.... and until now everything working as they should.

None the less I am interested in 2 things (for future):
1) What port is hkp:// using cause I am firewalling everything?

2) How do I perform the os reporting check?