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=aUvvfR1ujMjF912nlwZJLvvMVYCFqPWUodI9m/JbzJRtffDgX2jCo
	cHGR/0pULb9KdLLELtgIa1FE++k/BZlbBcGNcybS36ENDZOQ7c34ynEQ5nllowdA
	FvlDJqTxdbwVVJN+8nqluKYrHuxA6j4iE3D6tvI0TaC94NhmYyWyHw=
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, 28 Oct 2014 10:28:12 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Why does mkpasswd -c use a different offset? Corinna?
Message-ID: <20141028092812.GE20607@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <f069d5205a8a3fe87d00afa81537a959 DOT squirrel AT webmail DOT xs4all DOT nl>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="3rx43rDlPB5nB2+S"
Content-Disposition: inline
In-Reply-To: <f069d5205a8a3fe87d00afa81537a959.squirrel@webmail.xs4all.nl>
User-Agent: Mutt/1.5.23 (2014-03-12)

--3rx43rDlPB5nB2+S
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Oct 28 00:11, Houder wrote:
> Hi Corinna,
>=20
> I am confused ... the output from mkpasswd -c is NOT the same as the outp=
ut from mkpasswd -l -u <current user> on
> both my "Cygwin-32" and my "Cygwin-64".
>=20
> As an example, the output on my "Cygwin-64":
>=20
> 64-@@ uname -a
> CYGWIN_NT-6.1 Seven 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 Cygwin
> 64-@@ id
> uid=3D1000(Henri) gid=3D513(None) groups=3D513(None),545(Users),1007(Help=
LibraryUpdaters)
>=20
> 64-@@ grep Henri /etc/passwd
> Henri:unused:1000:513:U-Seven\Henri,S-1-5-21-91509220-1575020443-27147992=
23-1000:/home/Henri:/bin/bash
> 64-@@ mkpasswd -l -u Henri
> Henri:unused:1000:513:U-Seven\Henri,S-1-5-21-91509220-1575020443-27147992=
23-1000:/home/Henri:/bin/bash
>=20
> 64-@@ mkpasswd -c
> Henri:unused:11000:10513:U-Seven\Henri,S-1-5-21-91509220-1575020443-27147=
99223-1000:/home/Henri:/bin/bash
> 64-@@ mkpasswd -C
> Seven\Henri:unused:11000:10513:U-Seven\Henri,S-1-5-21-91509220-1575020443=
-2714799223-1000:/home/Henri:/bin/bash
>=20
> Note the difference between the output from 'mkpasswd -l -u Henri' and 'm=
kpasswd -c' (i.c. uid and gid). It is
> not what I expect (i.e. I do not understand).
>=20
> Please, enlighten me ...

It's a bug.  Funny that this has never been reported before.

It shouldn't matter anymore, though, because mkpasswd is changing
significantly with 1.7.33.  I would suggest to take a look into the
current test release 1.7.33-0.3.  The mkpasswd command will produce
the same uid and gid values as the values generated by the Cygwin
DLL in "db" mode to avoid collisions.


Corinna

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

--3rx43rDlPB5nB2+S
Content-Type: application/pgp-signature

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

iQIcBAEBAgAGBQJUT2GsAAoJEPU2Bp2uRE+gA0oP/167iAv9mCKYJGbESazemWgV
znsLhHlAYaltBzP3AhNYmjdU2XStD0fjjVQfsDVSyY3HoxFFr60pTtAUlkTmDqP5
97qlnL12Bv0wFFuQSOfB97v+N0PPoP/tKmn1Clyk1sd5Al6Zz5TaZSPno26AMj80
WkjpdtH0ZcRJjwaDOhamswj0FX+zfwRwjqK+jU9P3K5wiZLWB07JFZ6AoR1kTqoj
Gzz7Nj+G1DGN5tgGh0UstrnE5pofx77uxA1Gu4X1QUppoNN79y+mNdOfP9UWC3bE
hg+/gvUec8UTmF+p8bwSmcBFv0v3WVPvMetE2/Sm7FRkyc4bd4Ih3doMDl8pnKxA
V2ook+u+zi0qm2Mm70xT34XWF0YXle6vgnCkoRt3uWBfjTaenyyAkXinDNCe52aE
CCMN32+uBsNFFmQZzqiykcu275sfVZZDmxY7Un5LK3Is5ad8VxHsh+G4HpKWIsCE
JgqJ/9J66SyUGD7f3n3v5bMcdunsQArwM2HDPFYNItj/olZ1JkI/3gM8gpPbOFft
LD25akKkw8W7ufN4jMPoyIPTj5lL1FBdXppfZdf4XqPmolHWWIwoumnF+56jCnTy
cgeJofil3gMQy/WPUFI98Cn8VGFHb2oaQVXMoGrtDysD4ffnT/iILoWDQiEB7Als
xwwE5Az5hSWGa6iqOkfm
=+b20
-----END PGP SIGNATURE-----

--3rx43rDlPB5nB2+S--