Update to the "Invalid Signature ..." problem in the Troubleshooting document

SatNOGS Software
1

The trouble shooting document: Troubleshooting - SatNOGS Wiki

gives a solution that no longer works: apt-key is now deprecated.

root@satnogs:/home/satnogs# apt-key --keyring /etc/apt/trusted.gpg add < k
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).

this page: repository - What commands (exactly) should replace the deprecated apt-key? - Ask Ubuntu
documents how to do this now.

Here’s what I did:

wget -qO - http://download.opensuse.org/repositories/home:/librespace:/satnogs-unstable/Raspbian_10/Release.key >k
gpg --no-default-keyring --keyring ./temp-keyring.gpg --import k
gpg --no-default-keyring --keyring ./temp-keyring.gpg --export --output k.gpg
mkdir /etc/apt/keyrings
mv k.gpg /etc/apt/keyrings/satnogs2.gpg
vi /etc/apt/sources.list.d/satnogs.list
insert a signed-by statement, as:
deb [signed-by=/etc/apt/keyrings/satnogs2.gpg] /repositories/home:/librespace:/satnogs/Raspbian_11 - openSUSE Download ./

If there’s a way I can update that document directly (e.g. with a pull request), please let me know.

Glen

1 Like
2

Hi @kc0iyt ,

thank you for offering to fix the documentation! Unfortunately the SatNOGS wiki login is broken for an embarrassingly long time, so editing is not possible. But it should be fixed in a few days and I’ll post an update here once it is done.

Beyond that, starting with the SatNOGS Image 2023111400 the “Invalid signature” error should not be possible to trigger anymore (until 2025 if there is no release made in the meantime). Since the wiki can’t be edited currently we don’t link to this latest release yet, thus leading to this bug still being visible.

Best wishes,
Fabian

1 Like
3

The SatNOGS wiki login is fixed now, so you should be able to edit the document directly by following this link (assuming you are logged-in): Troubleshooting - SatNOGS Wiki

I’ve also updated the documentation to link to the latest SatNOGS Image release, thus new station operators wont get the apt-key deprecation warning anymore.

2 Likes
4

I haven’t had my ground station up for over a year and I decided to get it back up and running.

I am getting the signatures were invalid error when I do a sudo apt update

I run through the steps above and I get this error after the second command line:

pi@raspberrypi:~ $ wget -qO - http://download.opensuse.org/repositories/home:/librespace:/satnogs-unstable/Raspbian_10/Release.key > k
pi@raspberrypi:~ $ gpg --no-default-keyring --keyring ./temp-keyring.gpg --import k
gpg: keybox './temp-keyring.gpg' created
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0

I opened the “k” file with nano and there is nothing there.

I’m not sure what to do now, any help?

Thanks,
-K3TZ

5

That is because the old old stable Raspbian 10 was dropped some time ago, the old stable Debian 11 is still around and we’re moving to stable Debian 12 now.
dist upgrading has a low success rate, so backing up the config and starting with a fresh image is the recommended way iirc.

6

Thanks for the reply, I think I accidentally fixed it by running sudo satnogs-setup, update, apply, and reboot. It did a lot of activity after the apply for about 5 minutes. After reboot, I ran sudo apt update and had no errors.

Not sure how that happened but I’ll take it :slight_smile:

73,
K3TZ