Re: Tectia Server 4.0 and OpenSSH 3.6.1 compatibility
nobody_at_nodomain.invalid
Date: 11/22/04
- Previous message: Richard E. Silverman: "Re: Port Forwarding and Multiple SSH Servers - WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!"
- Next in thread: Michael A Stahnke: "Re: Tectia Server 4.0 and OpenSSH 3.6.1 compatibility"
- Reply: Michael A Stahnke: "Re: Tectia Server 4.0 and OpenSSH 3.6.1 compatibility"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 22 Nov 2004 21:01:32 +0200
Scott McGerik wrote:
> Has anyone encountered compatibility issues between OpenSSH 3.6
> and ssh.com's Tectia Server 4.0? Particularly with regards to file
> transfers to/from using scp and sftp while using public key
> authentication?
>
OpenSSH scp is incompatible with Tectia Server. OpenSSH scp to SSH
Tectia Server does not work at all, so you have to use sftp. Scp2 of SSH
Tectia Client to OpenSSH server does interoperate.
Authentication agent forwarding between OpenSSH and SSH Tectia is not
interoperable.
SSH Tectia and OpenSSH use different public key file formats. For
public-key authentication to interoperate between OpenSSH and SSH
Tectia, you must convert your public key to the appropriate format.
For more info check KB articles #116, #1940 and #1949 (and maybe #1950
and #1951) at http://support.ssh.com
- Previous message: Richard E. Silverman: "Re: Port Forwarding and Multiple SSH Servers - WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!"
- Next in thread: Michael A Stahnke: "Re: Tectia Server 4.0 and OpenSSH 3.6.1 compatibility"
- Reply: Michael A Stahnke: "Re: Tectia Server 4.0 and OpenSSH 3.6.1 compatibility"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|