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
From:	"Chris January" <chris AT atomice DOT net>
To:	<cygwin-developers AT cygwin DOT com>
Subject:	RE: gethostid anyone?
Date:	Mon, 10 Mar 2003 00:01:20 -0000
Message-ID:	<LPEHIHGCJOAIPFLADJAHIEIADGAA.chris@atomice.net>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To:	<20030308050421.GA27025@redhat.com>
Importance:	Normal

> Anyone interested in implementing a working gethostid?  It should be
> trivial to have it returned a munged IP address like linux but it
> might be more interesting if it returned something more unique than
> that.
>
> I was playing around with uuidgen to see if that could be used to
> generate something unique but it creates too many bits.  I thought
> it might be interesting to use it to seed a /etc/hostid file, though.
>
> Anyway, this would be a good project for anyone interested in contributing
> something.  It would also remove an XFAIL from the test suite.

I could probably come up with a patch for this.
How about using a hash of the following items:
1. Processor serial no. (if available)
2. MAC address of first ethernet card (if available)
3. Windows product id
4. Capacity of drive C:
5. Anything else lying around.

There would need to be an option to turn this off however as some privacy
freaks would probably complain despite the hashing.

Chris

- Raw text -