summaryrefslogtreecommitdiff
path: root/cloudinit/ssh_util.py
diff options
context:
space:
mode:
authorEduardo Otubo <otubo@redhat.com>2020-07-15 20:21:02 +0200
committerGitHub <noreply@github.com>2020-07-15 14:21:02 -0400
commite161059a18173e2b61c54dba9eab774401fb5f1f (patch)
treecd628210ff953adc001a8ff81a497026be703a83 /cloudinit/ssh_util.py
parent4fe576516d65feda17ba78e9265a8e494a195e7b (diff)
downloadvyos-cloud-init-e161059a18173e2b61c54dba9eab774401fb5f1f.tar.gz
vyos-cloud-init-e161059a18173e2b61c54dba9eab774401fb5f1f.zip
ssh exit with non-zero status on disabled user (#472)
It is confusing for scripts, where a disabled user has been specified, that ssh exits with a zero status by default without indication anything failed. I think exitting with a non-zero status would make more clear in scripts and automated setups where things failed, thus making noticing the issue and debugging easier. Signed-off-by: Eduardo Otubo <otubo@redhat.com> Signed-off-by: Aleksandar Kostadinov <akostadi@redhat.com> LP: #1170059
Diffstat (limited to 'cloudinit/ssh_util.py')
-rw-r--r--cloudinit/ssh_util.py4
1 files changed, 3 insertions, 1 deletions
diff --git a/cloudinit/ssh_util.py b/cloudinit/ssh_util.py
index 72e4e65e..89150acf 100644
--- a/cloudinit/ssh_util.py
+++ b/cloudinit/ssh_util.py
@@ -40,11 +40,13 @@ VALID_KEY_TYPES = (
"ssh-rsa-cert-v01@openssh.com",
)
+_DISABLE_USER_SSH_EXIT = 142
DISABLE_USER_OPTS = (
"no-port-forwarding,no-agent-forwarding,"
"no-X11-forwarding,command=\"echo \'Please login as the user \\\"$USER\\\""
- " rather than the user \\\"$DISABLE_USER\\\".\';echo;sleep 10\"")
+ " rather than the user \\\"$DISABLE_USER\\\".\';echo;sleep 10;"
+ "exit " + str(_DISABLE_USER_SSH_EXIT) + "\"")
class AuthKeyLine(object):