From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.44.254]) by listman.redhat.com (Postfix) with ESMTP id 4C9713F1D8 for ; Thu, 22 Nov 2001 22:21:44 -0500 (EST) Received: from mail.redhat.com (mail.redhat.com [199.183.24.239]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with SMTP id fAN3Lip19300 for ; Thu, 22 Nov 2001 22:21:44 -0500 Received: (from mail@localhost) by mail.redhat.com (8.11.0/8.8.7) id fAN3Lih14322 for blinux-list@listman.redhat.com; Thu, 22 Nov 2001 22:21:44 -0500 Received: from server1.shellworld.net (root@server1.shellworld.net [64.39.15.178]) by mail.redhat.com (8.11.0/8.8.7) with ESMTP id fAN3Lhw14318 for ; Thu, 22 Nov 2001 22:21:43 -0500 Received: from localhost (ldavis@localhost) by server1.shellworld.net (8.11.1/8.11.1) with ESMTP id fAN3LhU29222 for ; Thu, 22 Nov 2001 21:21:43 -0600 (CST) (envelope-from ldavis@shellworld.net) Date: Thu, 22 Nov 2001 22:21:43 -0500 (EST) From: Luke Davis To: blinux-list@redhat.com Subject: Re: ssh In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Loop: blinux-list@redhat.com Sender: blinux-list-admin@redhat.com Errors-To: blinux-list-admin@redhat.com X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.0.1 Precedence: bulk Reply-To: blinux-list@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: That is what I thought, thanks. Starting to think I had missed something big.:) Luke On Thu, 22 Nov 2001, Andor Demarteau wrote: > On Wed, 21 Nov 2001, Luke Davis wrote: > > > Um, you sure it is using SSL? > if he is not sure I am sure about it. > It doesn't use ssl for connecting. > For connecting it use the RSA-algorithm whihc also can be used for > authentication. > In that case, place a publci-RSAkey on the remote host. Then you can use > your RSA-privatekey to connect and thus you don't need a password on the > rmote host. > THis is actually a very good method to allow someone temporary root-access > by placing thre public-key in your .ssh.autorhized_keys file. > ssh is more a replacement for rsh/rexec/rlogin and not of telnet and ftp. > > One thing more, you can't replace an ftp-connection by ssh, unless you have > a shell-account on the remote site. > > > > 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 > > > >