This page describes how passwords and SSH public keys of your WirnetTM gateway will be managed during the upgrade between Keros 5 and Keros 6
A mechanism exists to conserve passwords during the migration.
There were 2 accounts present in Keros 5:
admin: allows you to connect to the web interfaceroot: allows you to connect to the console (serial and SSH)In Keros 6, both accounts still exist, but do not have the same meaning as in Keros 5:
admin: allows you to connect to the console (serial and SSH) and to the web interface.root: allows you to connect to the console (serial only) and to the web interface.The
adminuser is part of thesudogroup, and can therefore use root privileges if required. Usingsudoon console or turning the administrative access on the web interface.
Connections to the
rootuser by password are not allowed.
The migration preserves passwords only for the admin account and if they are not considered weak.
root accountIn Keros 5, you may already have added your public SSH key into the gateway to connect to it.
This feature is only available for the root account.
The migration procedure will conserve the key after the upgrade. The key will allow to connect by SSH to the root account once in Keros 6.
admin accountBy default in Keros 5, you cannot access to your WirnetTM gateway by ssh using the admin account.
However, it is possible to do so in Keros 6.
You can prepare your WirnetTM gateway, before the migration in Keros 5, by adding your ssh public key for the admin account with the following commands:
mount -o remount,rw /keros
mkdir -p /keros/keros-installer-data/credentials
echo "pubkey" > /keros/keros-installer-data/credentials/admin.ssh_authorized_keys.user
During the migration, the file /keros/keros-installer-data/credentials/admin.ssh_authorized_keys.user will be moved to /home/admin/.ssh/authorized_keys and will allow to connect by SSH to the admin account once in Keros 6.