From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13401 invoked by alias); 11 Nov 2014 16:55:24 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 13389 invoked by uid 89); 11 Nov 2014 16:55:24 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: calimero.vinschen.de Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 11 Nov 2014 16:55:23 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 0FC708E12EE; Tue, 11 Nov 2014 17:55:21 +0100 (CET) Date: Tue, 11 Nov 2014 16:55:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: RFC: 1.7.33 problem with user's home directory Message-ID: <20141111165521.GU2782@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20141110205216.GJ2782@calimero.vinschen.de> <0B8D23F7-0258-472D-BF38-860402FD3CDC@etr-usa.com> <20141111101821.GO2782@calimero.vinschen.de> <20141111111437.GB28012@calimero.vinschen.de> <87tx25u1o6.fsf@Rainer.invalid> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="V4yrq4dHtCqH+JvC" Content-Disposition: inline In-Reply-To: <87tx25u1o6.fsf@Rainer.invalid> User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2014-11/txt/msg00238.txt.bz2 --V4yrq4dHtCqH+JvC Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1162 On Nov 11 17:44, Achim Gratz wrote: > Corinna Vinschen writes: > >> Looks good, but maybe allow the AD attribute to be explicitly named (e= .g. > >> cygwinHomeDirectory). > > > > Cygwin schema extension? :) >=20 > I don't see why not, given that there's the possibility of having > different information for Windows, Cygwin and UNIX in the same AD. It's a bit complicated. You need a way to distinguish the name of an attribute from simple values like "home", or "cygwin" as Andrey proposes. My simply Cygwin-internal LDAP interface has no way of providing arbitrary attribute strings either, so that needs to be extended first. Microsoft themselves use XML strings in some attribute blobs for TS settings and stuff, so maybe the description field should be sufficient. I'm wondering if we really need other attributes then. > But > more realistically, one of the extensionAttributes that Exchange plugs > in anyway could keep that information. I have no experience with Exchange, so I can't tell. Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --V4yrq4dHtCqH+JvC Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUYj94AAoJEPU2Bp2uRE+gxEYP/03eN4TKxocAee8vKK/lcfvs 6doLd4+HszlHT6fdjB54/86764PccvhZS/MNo8/BaPDqutyCc/0PW64mm9QQFDjo jgn12Lsmy1Al1wuawxICTWxxKQw2mP6sFiPdDRKJgYwReD3Lx2vRncR4qiUtDiOO +RLVMKKo3heoVy0VuQz5rTCRQiEn1MhxsQNmiyhbCbUtR3MlIAJQGL+9Oj0yNoUX 9Kr0Hxl5bcYirfosjkKBYknNtyUFtK6F3xD5kNLwjD1Y3ZUW80EQbu7y37M8DSsH 4/0qymFG1bEoSbbBp7NU2DKbUbzA9i7Z2qicn1s0uzREktWErE2tB59HtzBoeJoY 7lGRu14OHIsyupDEfk3GozrmRAychzQbMGtqRkTN+5EcC51LlladnHAz4txHkxo7 tn1xmWnyXFGDw91CeY/S1f7twQX0b/256DCBXERDZsy7h/q/4DfJ6qgIIxGSJ73H vLnNoZ++0m2HGjrinN8eveseF+hBXtnCo7spYVnQteT8/8nMRS28K/M6Td9f6dpZ IBmrt2wDtkJ2uaWAyAf6OnijWqy83Vt89E2ZE7rN9hbKyg8Zn/vH+RT8oJ6ejBZ3 dX46lw+dCuZiMHJjDZXpowkdZMXxjo+JeBx9ysFsXxFPH9BzSeZZ5BX6qccp98JS Jv3g16jG1+GWloMyOS1e =n872 -----END PGP SIGNATURE----- --V4yrq4dHtCqH+JvC--