From owner-freebsd-questions Thu Jan 18 10:29:55 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA23650 for questions-outgoing; Thu, 18 Jan 1996 10:29:55 -0800 (PST) Received: from jack.Colorado.EDU (jack.Colorado.EDU [128.138.149.29]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA23645 for ; Thu, 18 Jan 1996 10:29:42 -0800 (PST) Received: from jack (localhost [127.0.0.1]) by jack.Colorado.EDU (8.7.3/8.7.3/CNS-4.0) with SMTP id LAA14133 for ; Thu, 18 Jan 1996 11:26:50 -0700 (MST) Message-ID: <30FE90EA.6A90@Colorado.EDU> Date: Thu, 18 Jan 1996 11:26:50 -0700 From: "Mark G. M. O'Lear" Organization: University of Colorado X-Mailer: Mozilla 2.0b5 (X11; I; SunOS 5.4 sun4m) MIME-Version: 1.0 To: questions@freebsd.org Subject: Bug in xlockmore-2.11b.tgz Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org Precedence: bulk Hi, I noticed that xlock will generate a floating point exception error and die occasionally. I know that if you have the flame mode (either by -mode random, or -mode flame) up, you can just hit enough times (usually 10 or so) and it will die with a floating point exception error (not real good for security.) I think that it will do this on other modes, but I haven't verified it. I have only noticed it doing this when it generates a new pattern, not just running the old pattern over and over again. Is there any way to do a -mode random and add a flag to skip certain modes like flame? (not just for this reason) I got xlockmore-2.11b.tgz from the packages-2.1 directory. I am using FreeBSD 2.1.0-RELEASE with DES/Kerberos installed. Mark Mark.Olear@Colorado.EDU