Date: Tue, 27 Jun 100 11:04:02 -0400 (EDT) From: mwlucas@exceptionet.com To: larry@interactivate.com (Lawrence Sica) Cc: freebsd-security@freebsd.org, freebsd-questions@freebsd.org Subject: Re: ssh server for WinNT Message-ID: <200006271504.LAA23677@easeway.com> In-Reply-To: <3958C483.CC13F865@interactivate.com> from Lawrence Sica at "Jun 27, 0 08:13:07 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> > ssh server for NT would make. Ok, you can control many of the network > > stuff from CLI but beside that, you'd still have the need for a > > solution such as VNC or PcAnywhere to control the settings only > > avaiable by the GUI (one could argue that's possible to control the > > system by hacking the registry which should be doable from CLI but who > > would be so masochistic? ;-). > well you could, if your feeling unsafe about say pcAnywhere's encryption > use ssh to setup a tunnel. F-secure puts out an nt ssh server i think. I find my NT SSH useful. Simply being able to start and stop services on a command line is quite helpful. I could use Telnet, but the NT Telnet daemon is a pain. Since many of our servers are development environments, console time is at a premium. Being able to connect in and make a quick change is nice. I also do things such as configure NT SNMP via SSH; that's all command-line driven. ==ml -- Michael Lucas | Exceptionet, Inc. | www.exceptionet.com "Exceptional Networking" | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200006271504.LAA23677>