Updating software probe version (with .deb package)
Hi, I have a software probe which I installed by creating a Debian package from source (as described in INSTALL.rst). The documentation suggests that one should regularly update software probe versions, and I'm interested in upgrading mine -- I was reminded by my earlier question about 240/4, as I may be running a client version from prior to when the patch allowing 240/4 scans was merged. The documentation doesn't specifically mention how to upgrade; can I assume that making a new .deb from current sources, and then installing that with dpkg on a machine where an older .deb is installed, will maintain the credentials and identity of my existing probe? It won't wipe everything out and require me to re-register as a new software probe, right?
👋 On Fri, 30 Dec 2022 at 22:00, Seth David Schoen <schoen@loyalty.org> wrote:
The documentation doesn't specifically mention how to upgrade; can I assume that making a new .deb from current sources, and then installing that with dpkg on a machine where an older .deb is installed, will maintain the credentials and identity of my existing probe? It won't wipe everything out and require me to re-register as a new software probe, right?
Compile the updated version from source as per usual and install the application from the DEB package. Take note of the SSH key. https://atlas.ripe.net/docs/howtos/software-probes.html Found in /var/atlas-probe/etc The probe identifies itself using the SSH key. Unless the key is regenerated during the upgrade. The probe will continue to chug along. :) *If* the SSH key is regenerated. You can always go to the RIPE Atlas Portal. Log in to manage your probe. And update the probe with the new ssh public key. = No need to register a new one. Either backup up the SSH key, or update the probe settings with the new ssh public key
participants (2)
-
netravnen+ripelist＠gmail.com -
Seth David Schoen