From owner-freebsd-security@FreeBSD.ORG  Tue Feb  3 13:53:50 2015
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 874F1927
 for <freebsd-security@freebsd.org>; Tue,  3 Feb 2015 13:53:50 +0000 (UTC)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
 [66.111.4.27])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5650482
 for <freebsd-security@freebsd.org>; Tue,  3 Feb 2015 13:53:50 +0000 (UTC)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46])
 by mailout.nyi.internal (Postfix) with ESMTP id 9C77D20C10
 for <freebsd-security@freebsd.org>; Tue,  3 Feb 2015 08:53:49 -0500 (EST)
Received: from web3 ([10.202.2.213])
 by compute6.internal (MEProxy); Tue, 03 Feb 2015 08:53:49 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=message-id:x-sasl-enc:from:to
 :mime-version:content-transfer-encoding:content-type:in-reply-to
 :references:subject:date; s=smtpout; bh=2DYFQZrEVgt4m6CeAbJELHyw
 cXs=; b=Qk31xeU9i/drELqlzJu1sNCKxu6jeY7GbAx7a9uGHNKAo0hYiaTL/THU
 ba5gQUjNV7alXJln6LPFkW8OmWmHqiYMczOUmz0cR/cvbkjoL8DZadtcaV1Wci4p
 lxZGHlimkTE5m30nKLQBLYjW4gj2UM1EtqWaZS+qusbAkxmPgx8=
Received: by web3.nyi.internal (Postfix, from userid 99)
 id 6FF4A147142; Tue,  3 Feb 2015 08:53:49 -0500 (EST)
Message-Id: <1422971629.3446909.222482893.6AA0AE96@webmail.messagingengine.com>
X-Sasl-Enc: Z+OyD857DfRQRLZ3DpnjEm/cv8/G3XMOip2uJbdXBKxp 1422971629
From: Mark Felder <feld@FreeBSD.org>
To: freebsd-security@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-b6284d51
In-Reply-To: <1422971333.3444346.222480213.4886CF10@webmail.messagingengine.com>
References: <mailman.87.1422619202.67459.freebsd-security@freebsd.org>
 <20150202150721.E8553209@hub.freebsd.org>
 <20150202152243.GA29176@in-addr.com>
 <20150202164319.GL11558@ivaldir.etoilebsd.net>
 <alpine.BSF.2.00.1502020849580.24056@eboyr.pbz>
 <20150202185806.BD0AF865@hub.freebsd.org>
 <1422971333.3444346.222480213.4886CF10@webmail.messagingengine.com>
Subject: Re: Enumerating glibc dependencies
Date: Tue, 03 Feb 2015 07:53:49 -0600
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Feb 2015 13:53:50 -0000



On Tue, Feb 3, 2015, at 07:48, Mark Felder wrote:
> 
> Unless you're building a Frankenstein OS you should never come across a
> situation where a native FreeBSD binary is linked to glibc. (I'm not
> even sure it's possible!) Linux uses glibc for their libc reference, we
> use our own.

I forgot Debian K/FreeBSD existed which has a complete GNU base system.
So it has to be possible. But doesn't make it sane! :-)