From owner-freebsd-security Wed Feb 28 16: 7:51 2001 Delivered-To: freebsd-security@freebsd.org Received: from mr200.netcologne.de (mr200.netcologne.de [194.8.194.109]) by hub.freebsd.org (Postfix) with ESMTP id 3310837B718 for ; Wed, 28 Feb 2001 16:07:48 -0800 (PST) (envelope-from pherman@frenchfries.net) Received: from husten.security.at12.de (dial-213-168-72-57.netcologne.de [213.168.72.57]) by mr200.netcologne.de (Mirapoint) with ESMTP id ABX45128; Thu, 1 Mar 2001 01:07:46 +0100 (CET) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.2/8.11.2) with ESMTP id f2107h060872; Thu, 1 Mar 2001 01:07:44 +0100 (CET) (envelope-from pherman@frenchfries.net) Date: Thu, 1 Mar 2001 01:07:42 +0100 (CET) From: Paul Herman To: Nate Williams Cc: Subject: Re: ssh -t /bin/sh trick (was Re: ftp access) In-Reply-To: <15005.14720.989013.390180@nomad.yogotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 28 Feb 2001, Nate Williams wrote: > > I remember the days (FreeBSD 2.2.6, or so, using ssh from ssh.com) of > > having to write a small script in /etc/sshrc which checks for invalid > > shells to prevent what Brooks was describing. Back then, it *did* > > work. > > Strange. I'm using an older setup (2.2.8 client, 3.4 server), both > using SSH.com software, and it doesn't work. Back then the network was a mish-mash of FreeBSD and Linux servers. It could have just been a Linux sshd phenomenon. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message