From owner-freebsd-chat  Wed Oct  1 08:03:29 1997
Return-Path: <owner-freebsd-chat>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id IAA18447
          for chat-outgoing; Wed, 1 Oct 1997 08:03:29 -0700 (PDT)
Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA18439
          for <chat@FreeBSD.ORG>; Wed, 1 Oct 1997 08:03:19 -0700 (PDT)
Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1])
	by word.smith.net.au (8.8.7/8.8.5) with ESMTP id AAA00618;
	Thu, 2 Oct 1997 00:30:28 +0930 (CST)
Message-Id: <199710011500.AAA00618@word.smith.net.au>
X-Mailer: exmh version 2.0zeta 7/24/97
To: Eivind Eklund <perhaps@yes.no>
cc: Mike Smith <mike@smith.net.au>, softweyr@xmission.com, chat@FreeBSD.ORG
Subject: Re: Microsoft brainrot (was: r-cmds and DNS and /etc/host.conf) 
In-reply-to: Your message of "Wed, 01 Oct 1997 13:54:27 +0200."
             <199710011154.NAA20125@bitbox.follo.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 02 Oct 1997 00:30:27 +0930
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-chat@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > How do you feel about adding source-IP-based access control?  That and 
> > a local sshd in port-forwarding mode would just about do it.
> 
> I'd like to support SSL, too, as Windows users has to do quite a bit
> of work to get hold of SSH (unless a freeware port has come along -
> I've not looked at SSH for Windows for a while).  It isn't the
> ultimate priority, but it would make it much easier.  (Especially if
> those pesky export-restrictions fall over and die).

The only SSH port to Windows is the one marketted by F-Secure AFAIK.  
They have the exclusive rights to it, at any rate.

> > SSL is, AFAIK, subject to certain undesirable licensing conditions (not 
> > exportable, not available for commercial use, etc.) which may render it
> > unsuitable.
> 
> SSLeay isn't too much subject to this; it was developed outside the
> US.  We'd need it integrated in a web-server, though, and I don't know
> how the state of Apache-SSL is (Stronghold works just fine for my job,
> so I haven't looked at the freeware side of this).

Do you have the time to investigate this?  A small embedded server with 
this bolted on would be ideal.

mike