From owner-freebsd-security  Sun Jun 28 23:58:22 1998
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA18577
          for freebsd-security-outgoing; Sun, 28 Jun 1998 23:58:22 -0700 (PDT)
          (envelope-from owner-freebsd-security@FreeBSD.ORG)
Received: from ghpc8.ihf.rwth-aachen.de (ghpc8.ihf.RWTH-Aachen.DE [134.130.90.8])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA18534
          for <freebsd-security@FreeBSD.ORG>; Sun, 28 Jun 1998 23:58:14 -0700 (PDT)
          (envelope-from tg@ghpc8.ihf.rwth-aachen.de)
Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.rwth-aachen.de [134.130.90.6])
	by ghpc8.ihf.rwth-aachen.de (8.8.8/8.8.6) with ESMTP id IAA25463;
	Mon, 29 Jun 1998 08:58:04 +0200 (CEST)
Received: (from tg@localhost)
	by ghpc6.ihf.rwth-aachen.de (8.8.8/8.8.5) id IAA02572;
	Mon, 29 Jun 1998 08:58:02 +0200 (CEST)
To: Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE>
Cc: freebsd-security@FreeBSD.ORG
Subject: Re: xlock
References: <199806290632.IAA00836@gilberto.physik.RWTH-Aachen.DE>
From: Thomas Gellekum <tg@ihf.rwth-aachen.de>
Date: 29 Jun 1998 08:58:02 +0200
In-Reply-To: Christoph Kukulies's message of "Mon, 29 Jun 1998 08:32:34 +0200 (MEST)"
Message-ID: <87btrcy9s5.fsf@ghpc6.ihf.rwth-aachen.de>
Lines: 11
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE> writes:

> 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.

Could you tell more about this?

tg

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe security" in the body of the message