Still testing needed: New passwd/group AD/SAM integration
Andrey Repin
anrdaemon@yandex.ru
Sun Apr 13 10:35:00 GMT 2014
Greetings, Corinna Vinschen!
> What bugs me a bit is what this means for applications which expect
> fixed usernames. Sshd, for instance, expects the fixed username
> "sshd" right now when using privilege separation. I discussed this
> with the OpenSSH devs, and they understand the problem, but they think
> this should be handled by a Cygwin-specific function. So there's some
> extra work in it for me to get OpenSSH up to speed with this change,
> but I fear I'm not the only one. The more configurable stuff like this
> is, the more complicated it gets maintaining some packages.
I really don't see a problem. Is this implementation-dependent issue?
99% you are operating within "current domain" and do not need to specify
domain prefix at all.
I know I only ever had to specify domain prefix, when logging to the RPC pipe
of a domain server from a standalone station. And that was only because
Windows break login sequence while there's no account with same login/password
in local SAM.
When I'm already on a domain system, I just specify a username without a
prefix and go forth.
--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 13.04.2014, <14: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
More information about the Cygwin
mailing list