RE: OpenSSH_3.4p1 and OpenSSH_2.5.2p2
From: Graeme Vetterlein (Graeme.Vetterlein@ntl.com)
Date: 02/25/03
- Previous message: Shay B. Cohen: "PKI for secure authentication"
- Maybe in reply to: Baharlouie, Masoud: "OpenSSH_3.4p1 and OpenSSH_2.5.2p2"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: Graeme Vetterlein <Graeme.Vetterlein@ntl.com> To: "'Baharlouie, Masoud'" <mbaharlo@Mobility.com>, "'secureshell@securityfocus.com'" <secureshell@securityfocus.com> Date: Tue, 25 Feb 2003 10:26:00 -0000
> -----Original Message-----
> From: Baharlouie, Masoud [mailto:mbaharlo@Mobility.com]
..
>
> I have successfully used my
> client to connect to
> other servers using same keys but those servers are running commercial
> versions of SSH (FSecure ver. 5.0) on Windows platform.
Just a thought. The 'public keys' needed by the commercial versions are
stored
in a different format: see ssh-keygen(1) the -e option. When you generate
public
keys for use with OpenSSH severs, you don't need the -e.
+ private key (openSSH format)
+ public key (openSSH format)
+ public key (SecSH format)
So the public key (file) you use on commercial system CANNOT be the same one
you use on the OpenSSH server.
-- Graeme The contents of this email and any attachments are sent for the personal attention of the addressee(s) only and may be confidential. If you are not the intended addressee, any use, disclosure or copying of this email and any attachments is unauthorised - please notify the sender by return and delete the message. Any representations or commitments expressed in this email are subject to contract. ntl Group Limited
- Next message: John Mendenhall: "Re: OpenSSH_3.5p1 server, some PC clients cannot connect"
- Previous message: Shay B. Cohen: "PKI for secure authentication"
- Maybe in reply to: Baharlouie, Masoud: "OpenSSH_3.4p1 and OpenSSH_2.5.2p2"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
