From owner-freebsd-java@FreeBSD.ORG Thu Oct 2 04:26:31 2003 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A13E16A4B3 for ; Thu, 2 Oct 2003 04:26:31 -0700 (PDT) Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2225243FAF for ; Thu, 2 Oct 2003 04:26:30 -0700 (PDT) (envelope-from past@noc.ntua.gr) Received: from ajax.noc.ntua.gr (ajax.noc.ntua.gr [147.102.220.1]) by ulysses.noc.ntua.gr (8.12.9p1/8.12.9) with ESMTP id h92BPqUo078031; Thu, 2 Oct 2003 14:25:52 +0300 (EEST) (envelope-from past@noc.ntua.gr) Received: from noc.ntua.gr (hal.noc.ntua.gr [147.102.220.45]) by ajax.noc.ntua.gr (8.12.9p1/8.12.9) with ESMTP id h92BPp36074751; Thu, 2 Oct 2003 14:25:51 +0300 (EEST) (envelope-from past@noc.ntua.gr) Message-ID: <3F7C0B3F.8010806@noc.ntua.gr> Date: Thu, 02 Oct 2003 14:25:51 +0300 From: Panagiotis Astithas Organization: NTUA/NMC User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030924 X-Accept-Language: el, en-us, en MIME-Version: 1.0 To: Matthew Seaman References: <3F7C0299.1000001@noc.ntua.gr> <20031002111011.GC13305@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <20031002111011.GC13305@happy-idiot-talk.infracaninophile.co.uk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: James Adams cc: freebsd-java@freebsd.org Subject: Re: SSL on Java 1.4.1 native port X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2003 11:26:31 -0000 Matthew Seaman wrote: > On Thu, Oct 02, 2003 at 01:48:57PM +0300, Panagiotis Astithas wrote: > > >>I' ve had similar symptoms using SSL+Tomcat and I overcame them using >>rndcontrol to put some more interrupts (ethernet & clock, IIRC) to seed >>the PRNG. > > > Using the clock interrupt won't introduce any randomness into the > PRNG... The randomness that is derived from interrupts comes out of > the unpredictability of the time gap between them. That obviously > doesn't apply to the clock interrupt. Of course, you are right. Now that I am checking, I see that I actually use etherenet & ata. Cheers, -- Panagiotis Astithas Electrical & Computer Engineer, PhD Network Management Center National Technical University of Athens, Greece