public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: "A. R. Vener" <salt@aero-vision.com>
To: blinux-list@redhat.com
Subject: Re: ssh
Date: Sat, 24 Nov 2001 17:09:51 -0500	[thread overview]
Message-ID: <20011124170951.A31288@cougar.aero-vision.com> (raw)
In-Reply-To: <Pine.BSF.4.42.0111212144140.88013-100000@server1.shellworld.net>; from ldavis@shellworld.net on Wed, Nov 21, 2001 at 09:44:24PM -0500

Fairly sure. I compiled my ssh package from source. It needed
the SSL library to compile. It generates an encryption key. When
using the debug or verbose mode I can see all the security handshaking
the client and server exchange.  From this I infer that it is
using the SSL protocol.



Rudy

On Wed, Nov 21, 2001 at 09:44:24PM -0500, Luke Davis wrote:
> Um, you sure it is using SSL?
> 
> On Tue, 20 Nov 2001, A. R. Vener wrote:
> 
> > ssh stands for secure shell. It uses the secure socket
> > layer (SSL) to establish a connection machines similar to
> > telnet or rsh. It also includes the secure copy (scp) protocol
> > as part of the suite.
> >
> > I've installed it on my machine and reccommend its use as
> > a replacement to telnet and password requiremed ftp since the
> > password transaction is also encrypted. This is not true for telnet, rsh or
> > ftp. If one of the machines is running an illicit sniffer your password can
> > be acquired by the sniffer operator when establishing a telnet or ftp
> > connection.
> >
> > You'll need to install first the OpenSSL library and then the
> > OpenSSH applications.
> >
> > Try cvhecking out http://www.openssh.com
> >
> > Have fun.
> >
> > rudy
> >
> >
> >
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://listman.redhat.com/mailman/listinfo/blinux-list
> >
> 
> 
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list




  parent reply	other threads:[~ UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Digital Talking Book Standard Martin G. McCormick
 ` Saqib Shaikh
   ` Peter Toneby
     ` Janina Sajka
       ` Peter Toneby
         ` Nicolas Pitre
           ` Peter Toneby
             ` Lloyd G. Rasmussen
             ` Nicolas Pitre
     ` Nicolas Pitre
       ` Peter Toneby
       ` Janina Sajka
         ` Nicolas Pitre
           ` Janina Sajka
             ` Nicolas Pitre
           ` Brent Harding
             ` Nicolas Pitre
     [not found]           ` <Pine.LNX.4.33.0111191409370.3206-100000@toccata.grg.afb.ne t>
             ` Brent Harding
     [not found]       ` <Pine.LNX.4.33.0111191147560.2815-100000@toccata.grg.afb.ne t>
         ` Brent Harding
           ` Nicolas Pitre
             ` Joel Zimba
               ` Brent Harding
             ` Brent Harding
               ` Nicolas Pitre
   ` philwh
 ` Janina Sajka
 ` Brent Harding
   ` Buddy Brannan
     ` Brent Harding
     [not found] ` <Pine.LNX.4.33.0111191114500.2815-100000@toccata.grg.afb.ne t>
   ` Brent Harding
     ` Luke Davis
       ` cbowman
         ` ssh A. R. Vener
           ` ssh cbowman
           ` ssh Luke Davis
             ` ssh Andor Demarteau
               ` ssh Luke Davis
               ` ssh Fredrik Larsson
                 ` ssh Luke Davis
                   ` ssh Fredrik Larsson
             ` ssh cbowman
               ` ssh A. R. Vener
             ` A. R. Vener [this message]
               ` ssh Luke Davis
         ` Digital Talking Book Standard Brent Harding
           ` cbowman
         ` Luke Davis
           ` cbowman
       ` Janina Sajka
     ` Pratik Patel
       ` Brent Harding

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011124170951.A31288@cougar.aero-vision.com \
    --to=salt@aero-vision.com \
    --cc=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).