From owner-freebsd-security  Fri May 30 16:41:48 1997
Return-Path: <owner-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA15961
          for security-outgoing; Fri, 30 May 1997 16:41:48 -0700 (PDT)
Received: from rich.isdn.bcm.tmc.edu (RICH.ISDN.BCM.TMC.EDU [128.249.250.34])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA15946
          for <security@freebsd.org>; Fri, 30 May 1997 16:41:44 -0700 (PDT)
Received: (from rich@localhost)
          by rich.isdn.bcm.tmc.edu (8.8.5/8.8.2) id SAA08966;
          Fri, 30 May 1997 18:41:27 -0500 (CDT)
Date: Fri, 30 May 1997 18:41:27 -0500 (CDT)
Message-Id: <199705302341.SAA08966@rich.isdn.bcm.tmc.edu>
From: Rich Murphey <rich@rich.isdn.bcm.tmc.edu>
To: perhaps@yes.no
CC: security@freebsd.org
In-reply-to: <199705301538.RAA08714@bitbox.follo.net> (message from Eivind
	Eklund on Fri, 30 May 1997 17:38:02 +0200 (MET DST))
Subject: Re: X libraries
Reply-to: rich@rich.isdn.bcm.tmc.edu
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

|Hopefully XFree will provide replacement libraries soon; if not, I'll
|try to do it, but I'm not presently equipped to compile new libraries
|for all FreeBSD versions.  (The XFree liason is Cc:'ed - can you
|comment on this, Rich?)

I guess I've missed other discussions about the bug.
We can include the patch for freebsd untill XFree86
picks it up if that's the consensus.  

Have you talked to anyone else with XFree86 about it?
Rich