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: Eli Barzilay MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17105.47620.419723.654228@tulare.cs.cornell.edu> Date: Sun, 10 Jul 2005 20:15:00 -0400 To: Larry Hall Cc: cygwin AT cygwin DOT com Subject: Re: ssh problems In-Reply-To: <200507091454.38902.lhall@rfk.com> References: <17099 DOT 10669 DOT 464228 DOT 125667 AT tulare DOT cs DOT cornell DOT edu> <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050705221013 DOT 08cdd6b0 AT pop DOT prospeed DOT net> <17099 DOT 18679 DOT 819770 DOT 637448 AT tulare DOT cs DOT cornell DOT edu> <200507091454 DOT 38902 DOT lhall AT rfk DOT com> On Jul 9, Larry Hall wrote: > When running through sshd, you're running via a service. Authenticating > without a password means that Windows won't authenticate as the user you are. > The reverse is also true. So it's possible that VS needs access to some > information that it doesn't have access to without being authenticated by > Windows. I could hazard a guess or two as to what that might be but a > better approach would be to just check the MSDN and on-line sources for > the different access restrictions of services that don't authenticate with > Windows. Sorry that's not much help, beyond the idea itself. For unrelated reasons, I will be debugging this thing remotely via vnc. This makes he whole deal a lot more complex. But the thing is that I won't mind a dirty solution -- is there a way to do this by reducing security somehow? Perhaps there is a way to start sshd in a different way? (After all, this thing *used* to work just fine with an older cygwin installation...) -- ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: http://www.barzilay.org/ Maze is Life! -- 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/