Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
Message-ID:	<002501c2e403$e4803f00$78d96f83@pomello>
From:	"Max Bowsher" <maxb AT ukf DOT net>
To:	<cygwin-developers AT cygwin DOT com>
References:	<3E675F8D DOT 414B9BBD AT ieee DOT org> <20030306164822 DOT GT1193 AT cygbert DOT vinschen DOT de> <3E6780A9 DOT F1F32899 AT ieee DOT org>
Subject:	Re: uid > 64k
Date:	Thu, 6 Mar 2003 17:14:48 -0000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

>> Pierre A. Humblet wrote:
>>> there was again a report of uid > 64k.
>>>
>>> Why don't we patch mkpasswd to keep uids below 64k until Cygwin
>>> switches to uid32 ?

> Corinna Vinschen wrote:
>> How do you fold the ids into 64K?  You never know if you're already
>> overwriting another id.

Pierre A. Humblet wrote:
> Agreed. However most passwd files have a lot fewer entries than 64k.
> Thus I was thinking that randomizing the entries above 64k into the
> range 10000->64k (to avoid local and special users) should succeed
> with high probability.

It might not be a good idea for mkpasswd to change the uids of these users
on every run. Perhaps you could use a hash function on the SID, rather than
a random function?

Max.

- Raw text -