On Mar 15 11:36, Larry Hall (Cygwin) wrote: > On 3/15/2010 11:26 AM, rra...@comcast.net wrote: > >what am i missing > >i am sure you can see that i am very new to cygwin > >where to find documentation on this is appreciated > > Presuming that you're trying to use pubkey authentication, read the > sections having to do with switching user context in the Users Guide: > > <http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-setuid-overview> > > See the 3 options for configuring the service to do this. You need > method 3.
There are other solutions, like calling `net use' in the ssh session. But there's another important point here which also affects method 3. If the machine is running Vista or later, and if the user is an admin user, then the shares are usually attached to the non-elevated user token. However, the ssh session uses the elevated token (otherwise no admin could do admin stuff in an ssh session). This elevated user token usually doesn't have the shares attached and the effect looks like it's just not working, as before. But it's still expected outcome since the non-elevated and the elevated token have different logon session IDs. Sigh, I think I should really add this to the documentation or the FAQ at one point. Windows authentication is very tricky somehow. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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
