From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20399 invoked by alias); 1 Oct 2004 00:26:52 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 20391 invoked from network); 1 Oct 2004 00:26:52 -0000 Received: from unknown (HELO sccrmhc13.comcast.net) (204.127.202.64) by sourceware.org with SMTP; 1 Oct 2004 00:26:52 -0000 Received: from [192.168.181.128] (c-67-172-156-222.client.comcast.net[67.172.156.222]) by comcast.net (sccrmhc13) with ESMTP id <2004100100265001600l26m3e>; Fri, 1 Oct 2004 00:26:51 +0000 Message-ID: <415CA434.9060904@phy.cmich.edu> Date: Fri, 01 Oct 2004 00:49:00 -0000 From: Eric McDonald User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) MIME-Version: 1.0 To: mskala@ansuz.sooke.bc.ca CC: Lincoln Peters , Xconq list Subject: Re: Map-related deja-vu References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004/txt/msg01297.txt.bz2 mskala@ansuz.sooke.bc.ca wrote: > Is this a problem? If so, we could easily put in a better seeding rule > and/or a better random number generator. As I recall from looking at the 'util.c' code once upon a time, Xconq uses a simple LCRNG. If we wanted something with a much longer cycle length, we could go for a Mersenne Twister or some such. Of course, that would not be suitable for cryptographic work, but neither is the current one. But, better seeding would probably be a good first step. Eric