From: "A. R. Vener" <salt@aero-vision.com>
To: blinux-list@redhat.com
Subject: Re: ssh
Date: Sat, 24 Nov 2001 17:23:44 -0500 [thread overview]
Message-ID: <20011124172344.B31288@cougar.aero-vision.com> (raw)
In-Reply-To: <Pine.SOL.4.21.0111221848330.14974-100000@lance.netdoor.com>; from cbowman@netdoor.com on Thu, Nov 22, 2001 at 06:49:51PM -0600
No because you need to set up both ends of the connection
to perform authentication.
The ssh packages include scp or secure copy. I use this only
when copying files to and from one of my accounts to another
over the internet. I use scp so that I don't need to expose my
password.
For most internet file transfers, ftp is fine because most
use anonymous ftp. If you have to transfer files to or from a
machine which requires you to vhave a login and password you are better
off using ssh/scp with that machine.
rudy
> hi, I just had a thought when reading this. is it posable to download with
> ssh, or to grab files on the net with this insted of ftp? thanks alot.
> charles
>
>
> On Wed, 21 Nov 2001, 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
> >
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
next prev 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
` A. R. Vener [this message]
` ssh A. R. Vener
` 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=20011124172344.B31288@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).