Hi,
I'm not sure ssh-keyscan was ever defined to have bad RC in that case.
The man page is empty, and the bit that I found online says:

RC=0
No usage errors. ssh-keyscan might or might not have succeeded or failed to 
scan one, more or all of the given hosts.

RC=1
Usage error.

Yes it changed in between Trusty and Xenial but that I think is just an
upstream change.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1661745

Title:
  ssh-keyscan does not exit with non-zero return code on error

Status in openssh package in Ubuntu:
  New

Bug description:
  On xenial, ssh-keyscan returns zero indicating success, when the
  command fails.

  root@cp1:~# lsb_release -d
  Description:  Ubuntu 16.04.1 LTS

  root@cp1:~# ssh-keyscan -H -t ssh-rsa bad-host
  getaddrinfo bad-host: Name or service not known
  root@cp1:~# echo $?
  0

  On trusty, the exit status is non-zero as expected.

  root@integration-deployer:/home/ubuntu# lsb_release -d
  Description:  Ubuntu 14.04.5 LTS

  root@integration-deployer:/home/ubuntu# ssh-keyscan -H -t ssh-rsa bad-host
  getaddrinfo bad-host: Name or service not known
  root@integration-deployer:/home/ubuntu# echo $?
  255

  This is a incompatibility between Ubuntu 14.04 and 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1661745/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to