From owner-ssh@clinet.fi Fri Jul 10 18:58:38 1998 Received: from lohi.clinet.fi (majordom@lohi.clinet.fi [194.100.0.7]) by hutcs.cs.hut.fi (8.8.8/8.8.8) with ESMTP id SAA21362; Fri, 10 Jul 1998 18:58:37 +0300 (EET DST) Received: (from majordom@localhost) by lohi.clinet.fi (8.9.1/8.9.0) id SAA21753 for ssh-outgoing; Fri, 10 Jul 1998 18:52:41 +0300 (EEST) X-Authentication-Warning: lohi.clinet.fi: majordom set sender to owner-ssh@clinet.fi using -f Received: from chat.tyenet.com (chat.tyenet.com [209.91.131.28]) by lohi.clinet.fi (8.9.1/8.9.0) with SMTP id SAA21746 for ; Fri, 10 Jul 1998 18:52:38 +0300 (EEST) Received: from tyenet.com [209.91.131.6] by chat.tyenet.com with ESMTP (SMTPD32-4.04) id A7796080292; Fri, 10 Jul 1998 11:47:05 EDT Message-ID: <35A637D4.68E99AE6@tyenet.com> Date: Fri, 10 Jul 1998 11:48:36 -0400 From: "Michael T. Babcock" Organization: Tyenet Technologies X-Mailer: Mozilla 4.05 [en] (Win95; U) MIME-Version: 1.0 To: "ssh@clinet.fi" Subject: Re: ssh installation References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ssh@clinet.fi Precedence: bulk Actually, installing ssh and sshd on a LAN that is internet-connected is quite useful. We have replaced all rsh-related utilities with their ssh equivalents. It is impossible to rsh to our network remotely, but we can still do rsh-style communication over our lan. Marcin Okraszewski wrote: > >'ssh' is an 'rsh' replacement. you can use 'ssh' and 'sshd' in a > >situation where 'rsh' and 'rshd' are appropriate (but insecure). > >generally you use it to access remote hosts across a public network > >(like the internet, or a shared residence hall ethernet), not between > >machines on a LAN. you're already mounting the home directories from a > >remote machine anyway, so ssh from the workstations, to say, 'YYY", your > >NIS server, seems pointless. -- _____/~-=##=-~\_____ -=+0+=-< Michael T. Babcock >-=+0+=- ~~~~~\_-=##=-_/~~~~~ http://w3.tyenet.com/mbabcock/ ICQ: 4835018