There are at least two possibilities here: Either the 3rd party is using ssh, a kind of secure telnet (that runs on port 22) Or the client is using an ssl encrypted connection to the telnet port (23) or any other port for that matter. If it is the latter case it's worth checking out "stunnel" which uses openssl to encrypt data over a standard port. Some protocols can't use this (eg ftp) as they don't use a single port. I think you'll need some more information though! - John Airey Internet Systems Support Officer, ITCSD, Royal National Institute for the Blind, Bakewell Road, Peterborough PE2 6XU, Tel.: +44 (0) 1733 375299 Fax: +44 (0) 1733 370848 [EMAIL PROTECTED] -----Original Message----- From: Ian Diddams [mailto:[EMAIL PROTECTED]] Sent: 08 November 2000 14:56 To: [EMAIL PROTECTED] Subject: I've been tasked into investigating a link a 3rd party may be making to our servers shortly over SSL. I've downloaded OpenSSL and installed it etc... but frankly I don;t know what I'm supposed to do with it! The 3rd party mentioned will basically be telneting in over an SSL link I am told (but nobody knows any more :-( ) ... so how exactly would such an arrangmet normally occur? Any ideas? Apologies for the ignorance, but I have to start somewhere (the 3rd party is not available for questioning AFAIUI). Ian ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
