From owner-freebsd-questions Tue Jun 27 8:42:51 2000 Delivered-To: freebsd-questions@freebsd.org Received: from bsdie.rwsystems.net (bsdie.rwsystems.net [209.197.223.2]) by hub.freebsd.org (Postfix) with ESMTP id 5E1FB37C0C2; Tue, 27 Jun 2000 08:42:41 -0700 (PDT) (envelope-from jwyatt@rwsystems.net) Received: from bsdie.rwsystems.net([209.197.223.2]) (1865 bytes) by bsdie.rwsystems.net via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Tue, 27 Jun 2000 10:34:46 -0500 (CDT) (Smail-3.2.0.106 1999-Mar-31 #1 built 1999-Aug-7) Date: Tue, 27 Jun 2000 10:34:34 -0500 (CDT) From: James Wyatt To: Gabriel Ambuehl Cc: Matt Watson , Danny , Ron Smith , freebsd-security@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Re[2]: ssh server for WinNT In-Reply-To: <846988849.20000627165800@buz.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A lot of useful things can be done with CLI on NT, especially when your scripting is in Perl... Couldn't you also use SSH to tunnel the VNC traffic, protecting it from snooping and providing multiple passwords for multiple users? I thought VNC passwords were sent clear and not rate-limited to prevent cracking. Just my 2 bits - Jy@ On Tue, 27 Jun 2000, Gabriel Ambuehl wrote: [ ... ] > Tuesday, June 27, 2000, 4:39:29 PM, you wrote: > > Since when is putty a ssh server? I coulda sworn it was a telnet/ssh1/etc > > client... but then again i have been wrong before :P > > You're right. It IS just a client. I'm just doubting how much sense a > 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? ;-). [ ... ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message