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: Wed, 06 Mar 2019 10:09:00 -0000 [thread overview]
Message-ID: <AM6PR07MB5334BEC016F182E1F97F817695730@AM6PR07MB5334.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <878sxt86kp.fsf@Rainer.invalid>
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?
Will it help with my network shares problem?
Thank you for your reply
-----Original Message-----
From: Achim Gratz [mailto:Stromeko@nexgo.de]
Sent: Tuesday, March 5, 2019 9:28 PM
To: 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
Maayan Apelboim writes:
> To my understanding this feature should be working in older versions
> as well.
If it works OK with 2.11.2, then wait a few moments for 3.0.2 to appear and it should work the same, plus you can then run the service under Local System instead of the special cyg_server user.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
--
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-06 10:09 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
2019-03-05 19:27 ` Achim Gratz
2019-03-06 10:09 ` Maayan Apelboim [this message]
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=AM6PR07MB5334BEC016F182E1F97F817695730@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).