This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Testers needed: New passwd/group handling in Cygwin
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Corinna Vinschen <cygwin at cygwin dot com>
- Date: Wed, 26 Feb 2014 02:20:19 +0400
- Subject: Re: Testers needed: New passwd/group handling in Cygwin
- Authentication-results: sourceware.org; auth=none
- References: <20140213143849 dot GH2246 at calimero dot vinschen dot de> <87fvn7cb68 dot fsf at Rainer dot invalid> <20140225200414 dot GA4238 at calimero dot vinschen dot de> <87y50zaqjb dot fsf at Rainer dot invalid> <20140225215423 dot GA6065 at calimero dot vinschen dot de>
- Reply-to: cygwin at cygwin dot com
Greetings, Corinna Vinschen!
> Also, more radically, if we drop the functionality to define another
> group name for a group, we could drop the requirement to open an LDAP
> connection to fetch group information to the DC entirely(*). This would
> only affect domain groups, local groups could still have different
> names. But I'm already wondering for a couple of days if having a
> Cygwin group name different from the Windows group name is really
> necessary at all.
If you ask me, it not only unnecessary, but potentially confusing, if not
dangerous.
Given that you've presumable fixed the group name mangling on locale changes,
I think all the necessity for this functionality is now gone.
> I added this years ago for fun, but there's no
> serious reason I can think of which would require to keep up with this.
> (*) Assuming the group info is cached in the local LSA, which is
> pretty likely for the groups of the current user.
--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 26.02.2014, <02:17>
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