search

aliascash / alias-wallet-archive

The content of this repository was reunited with the history of it's ancestors. It's archived now to keep all former release artifacts. The new repository is available at https://github.com/aliascash/alias-wallet
https://alias.cash/
59 stars 22 forks source link

Spectrecoin-3.0.14-73b56ca0-RaspbianLight - problem with keys #206

Closed Shekelme closed 3 years ago

Shekelme commented 5 years ago

Right after starting the Raspberry with newly-flashed SD card with Spectrecoin-3.0.14-73b56ca0-RaspbianLight image I performed 'apt update' command. It returned the following messages related to public keys:

pi@raspberrypi:~ $ sudo apt update Get:1 http://ftp.debian.org/debian stretch-backports InRelease [91.8 kB] Get:2 http://archive.raspberrypi.org/debian stretch InRelease [25.4 kB] Get:3 http://raspbian.raspberrypi.org/raspbian stretch InRelease [15.0 kB] Err:1 http://ftp.debian.org/debian stretch-backports InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7638D0442B90D010 NO_PUBKEY 04EE7237B7D453EC Get:4 http://raspbian.raspberrypi.org/raspbian stretch/main armhf Packages [11.7 MB] Reading package lists... Done W: GPG error: http://ftp.debian.org/debian stretch-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7638D0442B90D010 NO_PUBKEY 04EE7237B7D453EC E: The repository 'http://ftp.debian.org/debian stretch-backports InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. I fixed it with instructions from this page: https://raspberrypi.stackexchange.com/questions/12258/where-is-the-archive-key-for-backports-debian-org

But it could be very nice if all that stuff work right out of the box.

HLXEasy commented 5 years ago

@Shekelme Could you provide some more details what you did exactly? I'm unable to get the error fixed as gpg always returned with something like

gpg: keyserver receive failed: No data

or

gpg: no valid OpenPGP data found.

Any ideas?

Shekelme commented 5 years ago

@HLXEasy, unfortunately I have nothing to say beyond the instructions given at the link above...

HLXEasy commented 3 years ago

As of 4.3.1 not using backports anymore.