Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <4096C223.172C7A7C@dessent.net> Date: Mon, 03 May 2004 15:05:23 -0700 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: "'cygwin AT cygwin DOT com'" Subject: Re: Run Windows application via ssh References: <1CA079E0A10FD7119DC20002A544C5BE5541C2 AT eesusciexs3 DOT eesus DOT jnj DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com > "Drash, Jim [NCSUS]" wrote: > > Actually ssh can work such miracles. Not by itself, of course. It is > trivially easy to run VNC (Pick your favorite variant) , or RDP, or > ICA over an encrypted ssh connection. I suppose that was my point. THe poster specifically didn't want to use VNC, and using Remote Desktop or similar is really out of the scope of Cygwin. All cygwin and ssh know or care about is transporting a stream of bytes over the network. Alternatively put, those methods all work equally well independently of ssh (ignoring the security issues) so it's really not fair to say that ssh is contributing at all to those solutions... The poster was asking "Make ssh do FOO" but the answer is "ssh can't do FOO, but BAR can do FOO (optionially with ssh as the transport.)" Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/