DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=m89Atlz
	SyRZLA2wDbRfybwhRjd7kM8X1IFKSJqB++O7F/XfPOeX17CZjMhvYSZ7vqPAGA0c
	ZEKRNJdYhtrTZtO2jGoun7JQtP5fpplgTtv6aI22wMxKzTaKhd2F7hVBcYppSEtB
	n8Eo6lfS3zOBHCX1AQI1FQcZs8QuMPv6K96E=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
References: <CAJ1FpuNbULAo1Gb5Fo7w30PbxdZ9W=XFpiXAADCPqrhrM-TbEg@mail.gmail.com> <c627ae61-2b16-8c01-d0fe-31d48aae8821@yahoo.com> <CAJ1FpuO1nVEySyK1rc7c4AGx4+GsAHikBb54akebky8-yXM1HQ@mail.gmail.com> <35062835-c3cd-799e-d13a-16f954db2a19@yahoo.com> <02f492d9-b334-1dab-aedb-17a747ede36b@SystematicSw.ab.ca> <6b67157a-a9c8-1a72-8997-be9ea8a00a14@yahoo.com> <6e219349-6cd2-c632-09fd-b56779084438@yahoo.com> <99354c7d-ce38-0f77-e1f0-17b160b0465e@yahoo.com> <20190227205039.GF4133@calimero.vinschen.de> <5C775155.6060100@tlinx.org> <20190228093911.GG4133@calimero.vinschen.de>
In-Reply-To: <20190228093911.GG4133@calimero.vinschen.de>
From: Bill Stewart <bstewart@iname.com>
Date: Mon, 11 Mar 2019 15:26:27 -0600
Message-ID: <CANV9t=SUS2RU1NASRhF3J73LX6CkK=CSry+1RpYCFF_cofM8kg@mail.gmail.com>
Subject: Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"

On Thu, Feb 28, 2019 at 2:39 AM Corinna Vinschen  wrote:

> > Since windows seems to adhere to the rule:
> > "Case preserving", but "case ignoring", what does it
> > mean to make sure all user and group names are
> > case-correct?
>
> This all started here:
> https://cygwin.com/ml/cygwin/2019-02/msg00109.html
>
> followed up with
>
> https://cygwin.com/ml/cygwin/2019-02/msg00113.html
>
> tl;dr: The easy and fast way out didn't work for accounts from
> other domains than the machine's primary domain due to caching.
>
> So I thought it's a good idea to fetch the correct groupnames by an
> additional LDAP call, but the performance hit is apparently too high in
> some environments.

FWIW, not sure if you're using the IADsNameTranslate interface (
https://docs.microsoft.com/en-us/windows/desktop/api/iads/nn-iads-iadsnametranslate).
..

Example pseudo-code:

NameTranslate::Init(ADS_NAME_INITTYPE_GC, null);

Then:

accountName = 'domain\username';
NameTranslate::Set(ADS_NAME_TYPE_NT4, accountName);
caseCorrectedName = NameTranslate::Get(ADS_NAME_TYPE_NT4);  //
DOMAIN\UserName

Init depends on a available AD server (GC in this example), of course, but
seems pretty fast in my tests.

Bill

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