Date: Thu, 12 Oct 2000 11:55:54 -0400 From: "Francisco Reyes" <fran@reyes.somos.net> To: "Dag-Erling Smorgrav" <des@ofug.org>, "Poul-Henning Kamp" <phk@critter.freebsd.dk> Cc: "arch@FreeBSD.ORG" <arch@FreeBSD.ORG>, "Jeroen Ruigrok van der Werven" <jruigrok@via-net-works.nl>, "Kris Kennaway" <kris@citusc.usc.edu>, "Matt Dillon" <dillon@earth.backplane.com>, "Robert Watson" <rwatson@FreeBSD.ORG>, "Terry Lambert" <tlambert@primenet.com>, "Warner Losh" <imp@village.org> Subject: Re: cvs commit: src/etc inetd.conf Message-ID: <200010121549.LAA44352@sanson.reyes.somos.net> In-Reply-To: <72470.971194813@critter>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 10 Oct 2000 18:20:13 +0200, Poul-Henning Kamp wrote: >In message <xzphf6k4qzx.fsf@flood.ping.uio.no>, Dag-Erling Smorgrav writes: >>Poul-Henning Kamp <phk@critter.freebsd.dk> writes: >>> And as I pointed out earlier: having ssh doesn't help people who have >>> only a windows box to connect from. >> >>There are numerous ssh clients that run on Windows, and some of them >>are even not only free, but open-source as well (mindterm, for instance) > >I know, but I don't want to make the learning curve harder than >it need to be. Besides, it's not always possible to get permission >to install software on corporate windows machines. There is also the training involved. If a company has most/all the telnet/ftp boxes behind a firewall then for internal employees using ssh is added security but not as critical. francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200010121549.LAA44352>