This bug was fixed in the package openssh - 1:8.0p1-2
---
openssh (1:8.0p1-2) experimental; urgency=medium
* Fix interop tests for recent regress changes.
-- Colin Watson Fri, 14 Jun 2019 14:32:12 +0100
** Changed in: openssh (Ubuntu)
Status: Triaged => Fix Released
--
Upstream commit in 8.0:
commit c2c18a39683db382a15b438632afab3f551d50ce
Author: d...@openbsd.org
Date: Sat Jan 26 22:35:01 2019 +
upstream: make ssh-keyscan return a non-zero exit status if it
finds no keys. bz#2903
OpenBSD-Commit-ID:
Note that this has the potential of breaking existing scripts, so it's
probably not a good SRU candidate.
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
** Changed in: openssh (Debian)
Status: Confirmed => Fix Released
--
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
** Changed in: openssh (Debian)
Status: New => Confirmed
--
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
** Changed in: openssh (Debian)
Status: Unknown => New
--
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
** Bug watch added: Debian Bug tracker #374980
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=374980
** Also affects: openssh (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=374980
Importance: Unknown
Status: Unknown
** Bug watch added: OpenSSH Portable Bugzilla
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I appreciate the quality of this bug report and I'm sure
it'll be helpful to others experiencing the same issue.
This sounds like an upstream bug to me. Please can you verify this by
building directly from the
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
9 matches
Mail list logo
