X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Tony Benham Subject: Re: Connect browser via ssh tunnel to local server ? Date: Mon, 5 Nov 2007 17:20:39 +0000 (UTC) Lines: 18 Message-ID: References: <472F4DDB DOT DF7F9CFB AT dessent DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Brian Dessent dessent.net> writes: > Sure, just "ssh -D nnnn server" and then configure the browser to use a > socks proxy on localhost:nnnn, where nnnn is some available local port > number. Now all browser traffic goes through the tunnel, and the > internal site can be accessed in whatever way it would if you were > sitting at the console of the server. > > But what's this got to do with Cygwin? > > Brian > > I forgot to say the machine that hosts the apache server is a windows machine, that runs ssh under cygwin, so I use the cygwin/ssh to accept the remote connections from the linux machines. -- 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/