Xenial is now in Extended Security Maintenance and this bug doesn't
qualify for it, so this bug won't be fixed in that release.
** Changed in: openssh (Ubuntu Xenial)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Also affects: openssh (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu Xenial)
Status: New => Triaged
** Changed in: openssh (Ubuntu)
Status: Triaged => Fix Released
** Changed in: openssh (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: openssh (Ubuntu)
Status: New => Triaged
** Changed in: openssh (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618719
Title:
scp1 repo
(i.e. the problem is that scp1 is trying to use /usr/bin/ssh rather than
/usr/bin/ssh1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618719
Title:
scp1 reports ssh1 is not supported
To manage not
Yes, that's a bug in the version that shipped with xenial, fixed later
in 1:7.2p2-6 (so fixed in yakkety). You can work around it using "scp1
-S /usr/bin/ssh1 -1".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
