From owner-freebsd-security Tue Sep 28 18:57:38 1999 Delivered-To: freebsd-security@freebsd.org Received: from pogo.caustic.org (pogo.caustic.org [216.69.69.123]) by hub.freebsd.org (Postfix) with ESMTP id 251A414DDD for ; Tue, 28 Sep 1999 18:57:34 -0700 (PDT) (envelope-from jan@caustic.org) Received: from localhost (jan@localhost) by pogo.caustic.org (8.9.3/ignatz) with ESMTP id SAA64942; Tue, 28 Sep 1999 18:57:16 -0700 (PDT) Date: Tue, 28 Sep 1999 18:57:15 -0700 (PDT) From: "f.johan.beisser" To: peter.jeremy@alcatel.com.au Cc: freebsd-security@FreeBSD.ORG Subject: Re: Help me win the MS-Proxy/ipfw war In-Reply-To: <99Sep29.091741est.40322@border.alcanet.com.au> 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, 29 Sep 1999, Peter Jeremy wrote: > One problem is that ssh is `export-controlled' (under whichever set of > regulations apply today) and isn't part of the standard FreeBSD system. > > That said, I had no real difficultly in adding the ssh _server_ to a > custom PicoBSD floppy. I'm not sure why you'd want want the client, > but I'm sure that would fit as well. WHOOOPS! thanks for catching that. i ment the server side. although, i have to admit having the client on there would be handy for creating secured tunnels to other networks aswell. -- jan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message