Thanks Franco,
even though I don't like it to loose SSH during an upgrade I surely like hardening the system...
But how can I avoid being locked out prior to the upgrade? I was hoping there's a way to do that in preparation before running the 18.7 upgrade... Specifically because I got quite some machine's I only have SSH access to!
And yet so far all I found about it was:
in your above mentioned thread...
EDIT:
Had a support call with Jos on friday, he suggested to script it and have the script that change's my user's login shell run after the upgrade...
even though I don't like it to loose SSH during an upgrade I surely like hardening the system...
But how can I avoid being locked out prior to the upgrade? I was hoping there's a way to do that in preparation before running the 18.7 upgrade... Specifically because I got quite some machine's I only have SSH access to!
And yet so far all I found about it was:
Quote
o SSH access can be set for an arbitrary group as well under System: Administration for non-members of "admins" group. However, in both cases only SCP works due to a request in the forum to be more proactive regarding yielding of shell access rights. If you want a user to gain true SSH access you need to change their shell from "nologin" to an installed shell in their respective settings.
in your above mentioned thread...
EDIT:
Had a support call with Jos on friday, he suggested to script it and have the script that change's my user's login shell run after the upgrade...
"