X-Recipient:	archive-cygwin AT delorie DOT com
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=eKeeDjznrfv56KwgsfNQwrAycPjiSOQt2TaLLc1kEcMx5xZsyBI8M
	yCvzCFmlWAdYrtPktXQ971wi4NLxaslk72t60kdSXGOrOTQfunWHGRdGQ9UDWPAl
	SICQ0Uwwk6/Mau91bU71ALj5gVXVH20Xu2vVseucfMGh+lZrILCBH8=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; 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; s=default;
	bh=9nbGtv446Q6eKMraYBudGjk/g7w=; b=orj+MEH56spKpAVDboAQvWa1gHy/
	gaRKjneYRHhkZ4aoSfnC7KY9jc/RXKVlSekLh9lDqsDUXnnB6iSgVRRIOQ6BLsFb
	TXqnZl9lRrWbL7wCPNDiafxH6lYQS9hTq9XIyeLDjCsphTa1rux5mAqY1c/e8npu
	0XMrkEjs9wWTeIU=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
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
Date:	Fri, 11 Apr 2014 14:39:34 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Still testing needed: New passwd/group AD/SAM integration
Message-ID:	<20140411123934.GE23281@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20140410145323 DOT GB2437 AT calimero DOT vinschen DOT de> <5346E623 DOT 5000406 AT etr-usa DOT com> <20140410191120 DOT GL2437 AT calimero DOT vinschen DOT de> <20140411021652 DOT GC23945 AT dimstar DOT local DOT net> <534765CE DOT 1090009 AT etr-usa DOT com> <20140411062005 DOT GD23945 AT dimstar DOT local DOT net>
MIME-Version:	1.0
In-Reply-To:	<20140411062005.GD23945@dimstar.local.net>
User-Agent:	Mutt/1.5.21 (2010-09-15)

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

On Apr 11 16:20, Duncan Roe wrote:
> On Thu, Apr 10, 2014 at 09:47:26PM -0600, Warren Young wrote:
> > On 4/10/2014 20:16, Duncan Roe wrote:
> > >Yes, I'm one of those users. I need my login name to match the Linux s=
ystems so
> > >I can use rsh and not be challenged for a password when the cygwin hos=
t name is
> > >in ~/.rhosts
> >
> > If you switch to SSH, you can solve this by putting this into your
> > ~/.ssh/config file:
> >
> >      Host myremotehost
> >          User duncan_roe
> >
> > That is, you can override defaults (like login name) on a per-connection
> > basis.  Anything you can pass as an option to ssh(1) can be changed her=
e, so
> > you don't have to keep providing the option.
> >
> > With pre-shared keys, I don't think you'll see a difference in behavior
> > relative to rsh.
> >
> I don't want to switch to ssh. rsh is in an expect script, so providing s=
sh
> options every time would not be a problem. But I want to use rsh.

OTOH, if there *is* an official workaround which is, "use the /etc/passwd
file to chnage your username", wouldn't that be sufficient?

I understand your point, but the search problem in the Windows user DBs
as I outlined persists.

What I did a couple of weeks ago ws to change the mkpasswd tool so that
it creates the exact same passwd entries as you get when fetching them
directly from Windows.  For instance, the passwd entry generated for
my AD account inside of Cygwin will look like this:

corinna:*:1049577:1049701:Corinna Vinschen,U-VINSCHEN\corinna,S-1-5-21-2913=
048732-1697188782-3448811101-1001:/home/corinna:/bin/tcsh

Using the "new" mkpasswd, calling `mkpasswd -d -u corinna', I get the
exact same entry!  If I write this into /etc/passwd, I'm getting the
exact same correct uid and gid values, but I can change my username:

  $ mkpasswd -d -u corinna > /etc/passwd
  $ sed -i -e 's/^corinna:/cathy:/' /etc/passwd
  [logout/login]
  $ id
  uid=3D1049577(cathy) gid=3D1049701(vinschen) groups=3D1049701(vinschen),
  559(+Performance Log Users),545(+Users),[...]

That should be sufficient, shouldn't it?


Corinna

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

--SWTRyWv/ijrBap1m
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTR+KGAAoJEPU2Bp2uRE+glacP/2ZApEIlPXPVjL3ZzjKvDRTY
Bx37SLgUTClY+qJYN7fJkAwVXQX1WIdCc9eHhiN46RL9q3Wn8IgInL4Ho/3uL3eP
lTvYlqqX+HreIZZGc3+3MudivQMOmzIUKiCkMJdj5ilaLRuYXFqSlzjpF72gt6sg
tbtBfMGpTM1MTs9rEaoKQfDRhw3whn1Ubu3WhQY3lZdOtBtO0zwXLScfqafPc1wT
Vl+yDZFVGais4u/8uOhfmGxBMILa25oCMTKdckyaVq01MARSlfwixCrAturd/6dY
HZyInucFALJe0XwyS9RvN4N22dw1j5PAnmfQV/IgvBveNuKIPyQ1FmczVUeP4hNA
SGPXC06x3IGIKhXCdIt3psVKw3q9dzFYArXfYxfR5RTXt5/CtzZY9MdJ6NhV/y8K
XYdGNRJ3N1vr5Y0bd5ilYxSLrS6QS9nhRoFBYmvXH8IGeg1RXJ9XS0QG8+N5IuwV
dOTUkaj6Usa+OKmMsnxRBrQ5AmBERG/uFlms8yW54fjE4mXBbdt52ffhEnaE2IBf
4Tj9EBobGG+4ijdhZnH6TgZ5f8RAuDmCZljzyZDYIMBMdHot8NBrm4yApJqw43FP
zs4QFOc2xy7leFsxVj4z+7d68caCJq34TOgO2grWFmYFWBRD1KiVfW1XJcKlBA+J
eNhTi9jJVt2J6xNRFG6U
=g5JN
-----END PGP SIGNATURE-----

--SWTRyWv/ijrBap1m--

- Raw text -