DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=mimkNq/eJV/ALYEhWpNDRvsM+jZPGjZNXc9vucSoMu+DEJatUI8nV
	b+QteTOvfgxGuP/Robkh3QjORTn1UFanjaQIHTc3FswAlx9Xgb3KubCfceGS6CqV
	NraP3Cbvs24u1vUdhAT8Up1qDcUi2bPQriS5IHIOWrhtgnCHb9eNT8=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Tue, 2 Aug 2016 11:54:22 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: /dev/ptmx fails with Azure accounts
Message-ID: <20160802095422.GJ3470@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <579FB010 DOT 40202 AT towo DOT net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="NPukt5Otb9an/u20"
Content-Disposition: inline
In-Reply-To: <579FB010.40202@towo.net>
User-Agent: Mutt/1.6.2 (2016-07-01)

--NPukt5Otb9an/u20
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Aug  1 22:24, Thomas Wolff wrote:
> For Azure Domain users (and I do not really know what that means),
> pts handling does not seem to work, at least not for mintty, where forkpt=
y()
> fails.
> Please check https://github.com/mintty/mintty/issues/563 for a discussion,
> and my comment
> https://github.com/mintty/mintty/issues/563#issuecomment-235310199
>=20
> Also, there has been a similar report here:
> https://sourceware.org/ml/cygwin/2016-02/msg00046.html
>=20
> I have no idea how to establish a working startup of mintty for those use=
rs.

The problem here is that it's impossible to generate access
permissions for the pty with those weird accounts.  I like it
how Microsoft screws up otherwise working software with this
strange domain handling.

To fix this we have to be able to come up with a working user and group
account for these cases.  For that I need at least output from `whoami
/all'.  I wonder why supposedly nobody tried that after /fqdn didn't
work.

This may be fixable by somebody with such an account and willing to hack
on the Cygwin function pwdgrp::fetch_account_from_windows().  There's
already some code for the so-called "Windows accounts" which seem to
work in a similar fashion (albeit in this case the user has a local
account SID).

Alternatively I need at least a guinea pig with such an account,


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--NPukt5Otb9an/u20
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXoG3OAAoJEPU2Bp2uRE+gCscP/0BQpDFHrbbtqfXyyThukZZp
9NhInWrVY4xlMSn+4qdx5eSw2zq4AaEK/KLVYwv3cfUUncPfz+DC9P29oo5cEkIw
VIcVBG0iKb1tqIeEDVjvdH1dI1nHhXvtua0bQcZ0/T4vdQge+H1SpCm7NIRgSgZI
KO2JZF76Kv9Rx4x13lcCkVn6ZjO7meEDLkpPXQByqxf67MOvO0MR/xAR05aCPk+S
mfHsW2gkoSC8XRhC08TJ9rqakH2D5GYuRSbEn3loLf5v5yO2Ot118kCarZ3volqW
L9Q+OaA2ypTO7xgpwvy0TIxq8WBJyBJ6dUN5iPX4fpJnxtcHUqHZVDI8HSYODkVO
XoY40cDx0l2uHek3rECvNNwExagTiElED60Cdw3YXvELnsTMm5YGZV1YQ6QpJs8a
sc2OrTFR8v1GYHvJl9K60ttsDKvS5pKAX8+r3tq/hXmsNWD4kGo1w5qyeqjMei44
erskKxAkFk9AtzH3WzaqCLS3GPBU8K9qf4+TE52MJr40N0pXdDCsncwYBqpvMjE0
ls/g7HputdXRBmOvfczlg6YKaHfgiVuqY4ZPfsvsusSt9gk6GlycOVPPm2t4mJHD
kZSjDp79MHpXZQ5if6oyawjTsA+FOWFGEnMNE1uglU/NBDmvK1PsYt28UjBeWfaV
LhJLMKMwzgcqZ9gNVA62
=D1iD
-----END PGP SIGNATURE-----

--NPukt5Otb9an/u20--