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 From: Sam Edge To: cygwin AT cygwin DOT com Subject: Re: Login as a different user? Date: Thu, 25 Apr 2002 08:58:32 +0100 Organization: . Reply-To: cygwin AT cygwin DOT com Message-ID: References: <3CC7916F DOT 6050001 AT elegant DOT nl> In-Reply-To: <3CC7916F.6050001@elegant.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Posting-Agent: Hamster/1.3.23.4 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3P832929853 You wrote in <3CC7916F DOT 6050001 AT elegant DOT nl> in gmane.os.cygwin on Thu, 25 Apr 2002 07:17:35 +0200: > I stumbled on this question too and foud out that using 'ssh -l > localhost' in combination with keychain works just fine. You don't even need keychain but of course you do need sshd running with enough privileges to create processes under other accounts. This is most easily done by running the sshd configuration script (/usr/bin/ssh-host-config) from an administrative login and allowing it to install sshd as an NT service. However, this opens up more potential avenues for your system to be accessed over the 'Net and you should consider using the ListenAddress directive to limit access to localhost. There's also a slight security risk just having any Cygwin process running with enhanced privileges. See the thread "Getting Cygwin into a corporation..." <01fd01c1ebba$23197580$0d76aec7 AT D4LHBR01> -- Sam Edge -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/