From owner-freebsd-security Sun Jul 7 12: 2:42 2002 Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3748437B400 for ; Sun, 7 Jul 2002 12:02:38 -0700 (PDT) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBFB843E31 for ; Sun, 7 Jul 2002 12:02:37 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=rip.psg.com.psg.com) by rip.psg.com with esmtp (Exim 4.05) id 17RHIr-000GP6-00; Sun, 07 Jul 2002 12:02:37 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Klaus Steden Cc: freebsd-security@FreeBSD.ORG Subject: Re: signal 8 (fp execption) in pgp 5 References: <20020707145020.D95654@cthulu.compt.com> Message-Id: Date: Sun, 07 Jul 2002 12:02:37 -0700 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >> yesterday's -stable and ports tree, rebuilt twice. >> % pgpk -l randy >> Type Bits KeyID Created Expires Algorithm Use >> sec+ 1024 0xB1331439 1994-04-04 ---------- RSA Sign & Encrypt >> uid Randy Bush >> 1 matching key found >> Received signal 8. > Yup. I tried PGP6, too, and found the same problem. Did some digging > around in the source, and at least with PGP6, I discovered it's a bug in > pgpRndUnix.c. Specifically, when loading a timer for use in an entropy > function (I think), there's a call to clock_getres() - using the > CLOCK_REALTIME clock, filling in a structure that gets returned to the > caller as 0, which triggers the FPE. > > I tried using CLOCK_VIRTUAL, which stopped the FPE, but returned an error > and thus didn't generate any randomness. makes sense. note that this just appeared on a system i built. my old system, same pgp port, works fine. so o it has to do with the install, order of install, etc. or o there is something that changed in the last week or two randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message