can't access remote shares when using ssh with rsa key - passwd -R / set(e)uid / LogonUser is not working as expected

Corinna Vinschen
Wed Mar 13 09:04:00 GMT 2019

Please, don't top-post.

On Mar 13 08:31, Maayan Apelboim wrote:
>> From: Corinna Vinschen
>> Sent: Wednesday, March 6, 2019 2:28 PM
>> To:
>> Subject: Re: can't access remote shares when using ssh with rsa key - passwd -R / set(e)uid / LogonUser is not working as expected
>> On Mar  6 10:09, Maayan Apelboim wrote:
>> > Well, it doesn't work OK unfortunately, but I'm not sure if I missed something in the process, or is it just not working properly.
>> > I'm a bit worried to upgrade to 3.0.2 at the moment cause it's a major version and will probably have new bugs that I wouldn't want to find in production.
>> > 
>> > Assuming we will eventually upgrade to latest version - My sshd 
>> > service is running with domain user cyg_server and we login with domains users via ssh - is it still OK to switch the sshd service's user to local system?
>> > Will we still be able to login with domain users via ssh?
>> Yes, that's the idea.  The new method using the official S4U logon technique runs under the SYSTEM account.  No need to have a special cyg_server account with potentially dangerous privileges anymore.
>> > Will it help with my network shares problem?
>> No.  Just like the old techniques using an LSA authentication module or creating a user token from scratch, S4U login does not create tokens with valid network credentials.  For some weird reason only Microsoft knows about, you still need a password login for that.
>> The other method, logging in by stored password, as described in
>> still works, though.
> Hi,
> I appreciate your detailed response, however, stored passwords doesn't work properly.
> I've read the article and ran passwd -R as described - no errors generated and I was able to find the relevant registry entry after running the command, but still can't access network shares (access denied).
> When I login with password network shares are available.

When you login with stored password, Cygwin performs the same LogonUser
call as if you login with password, so the same user token is generated.

Off the top of my head I don't know why it shouldn't work for you.  You
sure you have the correct password stored?  When you login and call
`id', what does it print?  Does it contain the "interactive" group or
the "network" group?  If the latter, then the internal LogonUser call
performed with stored password failed for some reason.


Corinna Vinschen
Cygwin Maintainer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <>

More information about the Cygwin mailing list