From owner-freebsd-security Sun Jun 28 23:32:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15968 for freebsd-security-outgoing; Sun, 28 Jun 1998 23:32:36 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15961 for ; Sun, 28 Jun 1998 23:32:32 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id IAA00836 for freebsd-security@freebsd.org; Mon, 29 Jun 1998 08:32:34 +0200 (MEST) (envelope-from kuku) Date: Mon, 29 Jun 1998 08:32:34 +0200 (MEST) From: Christoph Kukulies Message-Id: <199806290632.IAA00836@gilberto.physik.RWTH-Aachen.DE> To: freebsd-security@FreeBSD.ORG Subject: xlock Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alarmed by recent buffer overflow attacks on Linux machines in my vicinity (an exploit for this is available) I thought about xlock under FreeBSD and would like to know whether the security hole has been sorted out under FreeBSD 2.2.x or what measures are advised to prevent it. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message