On Sunday 28 January 2007 18:55, Beardudeguy wrote: > Seak, Teng-Fong wrote: > > [EMAIL PROTECTED] wrote: > >>> If > >>> it is a Linux OS with MMF running in Vmware or WINE then you should be > >>> able > >>> to ssh into it and kill the offending application. > >> > >> Is there an alternative of ssh for Windows?... > > > > Server editions of WinNT provide the option to install Telnet. So > > you could telnet inside and do a shutdown/reboot. But only for server > > editions ...... > > Windows XP Pro comes with Telnet. > > OpenSSH is available for windows, but not as a native binary. > http://www.openssh.com/windows.html
CopSSH is better (easier to install on Windows) package. http://www.itefix.no/phpws/index.php?module=pagemaster&PAGE_user_op=view_page &PAGE_id=12&MMN_position=149:149 However, any form of SSH on Windows does not run natively and it requires part of Cygwin to be installed to provide what in essense is a Linux environment for OpenSSH to run within. Login in by this means you get a Linux shell command line to do things within your Cygwin environment, which should be installed with limited access onto the rest of the Windows system for security purposes (privilege separation). You can of course configure the system so that you can start messing up with your Windows OS from within Cygwin, but at the same time you start opening up potential vulnerabilities. Such vulnerabilities are not to be disregarded if your ssh installation is poorly configured; i.e. using the default ssh port and weak passwords like "Tom1", "1234", etc. because a quick dictionary attack will soon crack your otherwise unbreakable sshd tunnel. Telnet does not offer secure key authentication like ssh does (although you need to configure sshd from its default setup to disable passwd authentication and use SKA instead). Hence, the previous comments with regards to vulnerabilities apply, only much worse: unlike ssh, telnet transmits plain text authentication credentials in the open. Any router, switch, proxy, server, ISP, etc. in the middle, can read your "1234" password and username. Telnet was a lovely tool back in the seventies when the planet had three IBM mainframes and all IT engineers knew each other in first name terms. In conclusion, you can set up your sshd and Cygwin installation to manipulate your Windows OS, but I wouldn't readily recommend it. On the other hand, I would always recommend to use VNC over ssh, unless you are using the paid for VNC versions, which offer encrypted authentication. -- Regards, Mick [demime 1.01d removed an attachment of type application/pgp-signature] _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
