public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Maayan Apelboim <Maayan.Apelboim@clarizen.com>, cygwin@cygwin.com
Subject: Re: can't access remote shares when using ssh with rsa key - passwd -R / set(e)uid / LogonUser is not working as expected
Date: Tue, 26 Feb 2019 15:33:00 -0000	[thread overview]
Message-ID: <1359661834.20190226180118@yandex.ru> (raw)
In-Reply-To: <AM6PR07MB5334474464EB7A737E9B3B7C957B0@AM6PR07MB5334.eurprd07.prod.outlook.com>

Greetings, Maayan Apelboim!

> Hi,

> I hope I'm mailing the proper mailing list..
> I am using password-less ssh login using RSA key to login windows servers from linux.
> I've read this article about network shares problems when using RSA key
> instead password and decided method 2 is most suitable for my case:
> https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-setuid-overview

> So I ran passwd -R for the relevant user, but still getting 'permission
> denied' when trying to access network shares.
> Tried restarting the ssh service and rebooting the server but it didn't help.

> I checked the registry as SYSTEM and I can see my user UID set in the right
> location.. (at least I think so, cause it doesn't exists in other servers).
> So it seems to me like the 'set(e)uid' / 'LogonUser' described in the article doesn't work as expected.

> Would appreciate any suggestions.

Please try changing the cygsshd service configuration to run as "SYSTEM" user.

> * Some sensitive data was edited in the cygcheck.out file
> * I don't have cygserver installed as a service - I used administrator user
> and didn't get any errors when running passwd -R


-- 
With best regards,
Andrey Repin
Tuesday, February 26, 2019 17:58:28

Sorry for my terrible english...


--
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

  reply	other threads:[~2019-02-26 15:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AM6PR07MB5334CE88B67F5421BA671C43957B0@AM6PR07MB5334.eurprd07.prod.outlook.com>
2019-02-26 13:39 ` Maayan Apelboim
2019-02-26 15:33   ` Andrey Repin [this message]
2019-02-26 18:00     ` Houder
2019-02-27  1:17       ` Andrey Repin
2019-03-05  8:19         ` Maayan Apelboim
2019-03-05 19:27           ` Achim Gratz
2019-03-06 10:09             ` Maayan Apelboim
2019-03-06 12:28               ` Corinna Vinschen
2019-03-06 12:35                 ` Corinna Vinschen
2019-03-13  8:32                 ` Maayan Apelboim
2019-03-13  9:04                   ` Corinna Vinschen
2019-03-14 10:41                     ` Maayan Apelboim
2019-03-14 11:11                       ` Corinna Vinschen
2019-03-18 13:53                         ` Maayan Apelboim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1359661834.20190226180118@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=Maayan.Apelboim@clarizen.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).