opsi-server package update for new apt keys

Our opsi server packages are built on the OpenBuildService, OBS for short. This OBS signs the packages with a key which expires in regular intervals of two years and has to be renewed. Now the time has come to renew the key again. The current key expires on November 9th. On the OBS we already renewed the key about a month ago. Unfortunately this does not happen automatically on Debian-based Linux systems.

There are two ways to get the new key now:

• update the opsi-server package
• get the key manually

The first option is done with a simple apt update && apt upgrade. The version of opsi-server is 4.2.0.73-1 and can be found in opsi 4.2 stable.

The key can be fetched manually with one of the following commands and placed in the apt store, depending on the operating system:

• Ubuntu 20-04

curl -fsSL https://download.opensuse.org/repositories/home:/uibmz:/opsi:/4.2:/stable/xUbuntu_20.04/Release.key | gpg --dearmor | sudo tee /usr/local/share/keyrings/opsi-obs.gpg > /dev/null

• Ubuntu 22-04

curl -fsSL https://download.opensuse.org/repositories/home:/uibmz:/opsi:/4.2:/stable/xUbuntu_22.04/Release.key | gpg --dearmor | sudo tee /usr/local/share/keyrings/opsi-obs.gpg > /dev/null

• Debian 10

curl -fsSL https://download.opensuse.org/repositories/home:/uibmz:/opsi:/4.2:/stable/Debian_10//Release.key | gpg --dearmor | sudo tee /usr/local/share/keyrings/opsi-obs.gpg > /dev/null

• Debian 11

curl -fsSL https://download.opensuse.org/repositories/home:/uibmz:/opsi:/4.2:/stable/Debian_11/Release.key | gpg --dearmor | sudo tee /usr/local/share/keyrings/opsi-obs.gpg > /dev/null

• UCS 4.4

curl -fsSL https://download.opensuse.org/repositories/home:/uibmz:/opsi:/4.2:/stable/Univention_4.4/Release.key | gpg --dearmor | sudo tee /usr/local/share/keyrings/opsi-obs.gpg > /dev/null

• UCS 5.0

curl -fsSL https://download.opensuse.org/repositories/home:/uibmz:/opsi:/4.2:/stable/Univention_5.0/Release.key | gpg --dearmor | sudo tee /usr/local/share/keyrings/opsi-obs.gpg > /dev/null

After that, the current key should now be installed and can be traced using apt-key list.