Date: Thu, 02 Oct 1997 00:30:27 +0930 From: Mike Smith <mike@smith.net.au> 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) Message-ID: <199710011500.AAA00618@word.smith.net.au> In-Reply-To: Your message of "Wed, 01 Oct 1997 13:54:27 %2B0200." <199710011154.NAA20125@bitbox.follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710011500.AAA00618>