Why does mkpasswd -c use a different offset? Corinna?

[Corinna Vinschen]

On Oct 28 00:11, Houder wrote:
> Hi Corinna,
> 
> I am confused ... the output from mkpasswd -c is NOT the same as the output from mkpasswd -l -u <current user> on
> both my "Cygwin-32" and my "Cygwin-64".
> 
> As an example, the output on my "Cygwin-64":
> 
> 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=1000(Henri) gid=513(None) groups=513(None),545(Users),1007(HelpLibraryUpdaters)
> 
> 64-@@ grep Henri /etc/passwd
> Henri:unused:1000:513:U-Seven\Henri,S-1-5-21-91509220-1575020443-2714799223-1000:/home/Henri:/bin/bash
> 64-@@ mkpasswd -l -u Henri
> Henri:unused:1000:513:U-Seven\Henri,S-1-5-21-91509220-1575020443-2714799223-1000:/home/Henri:/bin/bash
> 
> 64-@@ mkpasswd -c
> Henri:unused:11000:10513:U-Seven\Henri,S-1-5-21-91509220-1575020443-2714799223-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
> 
> Note the difference between the output from 'mkpasswd -l -u Henri' and 'mkpasswd -c' (i.c. uid and gid). It is
> not what I expect (i.e. I do not understand).
> 
> 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

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20141028/b0d8db33/attachment.sig>