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:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=rN3k
	cfiK5HM3xe7VUc3TGsL9nQBcDvBsVAC90HJhLmtMb4L8OAvgSmnPdRe9fV3HLlF8
	0DwFsMPlLeC7bVYBQtDBIoD8TVq6Qe+b2RGwzMHW9+Ao4GsOdhj73+3OwJKOah9g
	5gznOrwMVprVpIZnTmnRH5zePYD4UQO4HSY9hcA=
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: Sat, 12 Apr 2014 10:06:13 +1000
From: Duncan Roe <duncan_roe AT acslink DOT net DOT au>
To: cygwin AT cygwin DOT com
Subject: Re: Still testing needed: New passwd/group AD/SAM integration
Message-ID: <20140412000613.GE23945@dimstar.local.net>
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> <20140411123934 DOT GE23281 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140411123934.GE23281@calimero.vinschen.de>
User-Agent: Mutt/1.5.22 (2013-10-16)

On Fri, Apr 11, 2014 at 02:39:34PM +0200, Corinna Vinschen wrote:
> 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 systems so
> > > >I can use rsh and not be challenged for a password when the cygwin host 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 here, 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 ssh
> > 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?

Yes it's perfect. That's what I use.
>
> 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-2913048732-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=1049577(cathy) gid=1049701(vinschen) groups=1049701(vinschen),
>   559(+Performance Log Users),545(+Users),[...]
>
> That should be sufficient, shouldn't it?
>
I do that already. Good to hear it as sound practice from you though,

Cheers ... Duncan.

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