[Bug 88] scp for OpenSSH v3.0.2p1 fails to commercial SSH v3.1.0 server (new -t option to SSH's scp)

bugzilla-daemon at mindrot.org bugzilla-daemon at mindrot.org
Fri Feb 1 06:28:35 EST 2002


------- Additional Comments From brectanu at naxs.net  2002-02-01 06:28 -------
Not exactly.  Yes, ssh1/scp1 is not installed on the remote machine, however the
commant should NOT be using ssh1/scp1 on the remote machine - it should be using
SSH protocol 2.  This is the problem.  When OpenSSH sends the 'scp -v -t'
command to the remote machine (SSH v3.1.0), the remote version of SSH is now
interpreting the '-t' option as a SSH1 compatibility flag.  Pre-SSH v3.1.0 there
was not a '-t' option to scp and thus no problem.  Now, however, there is a
problem with the new version of comercial SSH and a conflicting '-t' option
between SSH and OpenSSH scp.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the openssh-unix-dev mailing list