From owner-freebsd-chat  Sat Mar  1 23:08:40 1997
Return-Path: <owner-chat>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA26190
          for chat-outgoing; Sat, 1 Mar 1997 23:08:40 -0800 (PST)
Received: from alpha.risc.org (taob@[205.233.216.202])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA26185
          for <freebsd-chat@FreeBSD.ORG>; Sat, 1 Mar 1997 23:08:32 -0800 (PST)
Received: from localhost (taob@localhost)
          by alpha.risc.org (8.8.4/8.8.4) with SMTP
	  id CAA00901; Sun, 2 Mar 1997 02:08:11 -0500 (EST)
Date: Sun, 2 Mar 1997 02:08:11 -0500 (EST)
From: Brian Tao <taob@risc.org>
To: Snob Art Genre <ben@narcissus.ml.org>
cc: "John S. Dyson" <toor@dyson.iquest.net>,
        FREEBSD-CHAT-L <freebsd-chat@FreeBSD.ORG>
Subject: Re: RSA 56-bit key challenge 
In-Reply-To: <Pine.NEB.3.95.970301222642.1563C-100000@narcissus.ml.org>
Message-ID: <Pine.BSF.3.95.970302020653.775C-100000@alpha.risc.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-chat@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 1 Mar 1997, Snob Art Genre wrote:
> 
> get_keyspace: Operation timed out
> rc5-56-client: Error getting key.
> rc5-56-client: Sleeping 10 minutes...
> 
> Anything to worry about?

    There is only a single server handling keyblock requests and
gathering results from all the clients, so it tends to get kind of
busy.  On top of that, it is being intermittently synflooded so nobody
can get in.  Just leave the client running and your host connected,
and eventually it will get through.
--
Brian Tao (BT300, taob@risc.org)
"Though this be madness, yet there is method in't"