X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
To: cygwin@cygwin.com
Subject: Re: [OT] Remote assistance script?
Date: Thu, 10 Sep 2009 15:55:43 -0400
Message-ID: <j3mia55jrcffepmqdh1ij924iq5lmsgag5@4ax.com>
References: <0BB3850C15BD48E8BED69959150EAAFF@phoenix> <95cia597hr04hi9vect7vqkeum9hse792d@4ax.com>
In-Reply-To: <95cia597hr04hi9vect7vqkeum9hse792d@4ax.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-Archive: encrypt
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

> I'd go for an stunnel setup.  You can tunnel any TCP traffic over SSL
> (including e.g. ssh-- I've done it), and access to port 443 is just about
> guaranteed.

Or, you can just have your ssh server listen on port 443.  The only way
this wouldn't work is if either (1) port 443 is blocked, which is extremely
unlikely; or (2) you're behind an application firewall that detects and
blocks non-SSL traffic-- also extremely unlikely.  Even the firewall at the
agency where I work, which blocks non-HTTP traffic to port 80, doesn't do
that.

Good luck,
A.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple