From: Maayan Apelboim <Maayan.Apelboim@clarizen.com>
To: "cygwin@cygwin.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, 05 Mar 2019 08:19:00 -0000 [thread overview]
Message-ID: <AM6PR07MB533460CC230EFC21594F509595720@AM6PR07MB5334.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <271107546.20190227034559@yandex.ru>
To my understanding this feature should be working in older versions as well.
I have Cygwin running on production servers.
If I upgrade one I need to upgrade all, so I prefer to see if anyone has any suggestion before trying to upgrade.
Regards,
Maayan
-----Original Message-----
From: Andrey Repin [mailto:anrdaemon@yandex.ru]
Sent: Wednesday, February 27, 2019 2:46 AM
To: Houder <cygwin@cygwin.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
Greetings, Houder!
> On Tue, 26 Feb 2019 18:01:18, Andrey Repin wrote:
>> 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
> [snip]
>> Please try changing the cygsshd service configuration to run as "SYSTEM" user.
> Why, Andrey? He is running cygwin1.dll version 2.11.0 (as far as I can tell).
Sorry, I missed that bit. I normally assume people running an up to date system. Or at least update when they encounter issues.
--
With best regards,
Andrey Repin
Wednesday, February 27, 2019 3:45:05
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
next prev parent reply other threads:[~2019-03-05 8:19 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
2019-02-26 18:00 ` Houder
2019-02-27 1:17 ` Andrey Repin
2019-03-05 8:19 ` Maayan Apelboim [this message]
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=AM6PR07MB533460CC230EFC21594F509595720@AM6PR07MB5334.eurprd07.prod.outlook.com \
--to=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).