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 Date: Sun, 10 Jul 2005 23:35:14 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Eli Barzilay cc: cygwin AT cygwin DOT com Subject: Re: ssh problems In-Reply-To: <17105.47620.419723.654228@tulare.cs.cornell.edu> Message-ID: 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> <17105 DOT 47620 DOT 419723 DOT 654228 AT tulare DOT cs DOT cornell DOT edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 10 Jul 2005, Eli Barzilay wrote: > 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...) Since you don't seem to have followed the Cygwin problem reporting guidelines at , we don't know what version of Cygwin you've installed (please pay particular attention to the part in bold (about attaching the output of "cygcheck -svr"). Another WAG. If, as you say, it used to work before, you may be hitting traverse checking, which was turned on by default in a couple of newer Cygwin versions. The path to the necessary files may have been inaccessible to the SYSTEM user, though the files themselves were. This didn't matter for older Cygwin versions, but did in those ones. Try running sshd with 'notraverse' in $CYGWIN. If that solves your problem, remove 'notraverse' and open the access to whatever directories DevStudio needs (you can use, for example, SysInternals' filemon to find out what those are). Another thing to try is to get a system-owned shell and run DevStudio from it -- I'd guess you'll get the same errors. That may be problematic to do via VNC, though. In any case, try running the filemon tool and allow access to all of the files it reports to the "SYSTEM" user. I think that might fix your problem. As a last resort, again, since this used to work, try running sshd under strace (be prepared for a HUGE output file). Look through that trace to see when DevStudio runs -- if any Cygwin processes are invoked, see if they report access errors. This is something you'll need to do locally, though -- please don't send strace output to the list (if you have the web space, it may be ok to post a link to it, just in case someone is interested -- but only if Cygwin is involved). HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. /DA -- 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/