From owner-freebsd-security@FreeBSD.ORG  Wed Apr 30 18:51:25 2014
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 16822863;
 Wed, 30 Apr 2014 18:51:25 +0000 (UTC)
Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com
 [IPv6:2a00:1450:400c:c00::233])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 857FF16FD;
 Wed, 30 Apr 2014 18:51:24 +0000 (UTC)
Received: by mail-wg0-f51.google.com with SMTP id z12so2156023wgg.22
 for <multiple recipients>; Wed, 30 Apr 2014 11:51:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=pETRVUJ2uqig6GYSxGvWF19xjlb2KAbhTY6N+Z4pbsw=;
 b=j4cXbxmz5fSjT7TMeeQUZg6bZCFmficXj8+LLbnOF7/kPBRE+CDDHe7a/1B5f7sMMN
 xZZRsrT1lW+m8Tnl/yVeiDMAfW/z7ZRTZrFgM8UiHfcVM2ffY3RSZq+vgjLIqiw/uHI9
 KRBzcqSS7gutVOFKzL8gKU+hbPuG44n8/2S/EddFv+ujPhTj8zxFSEEaT4+jw7EFQjop
 EE+mhgMBNBzZfwPMEDsgckL80+B98pbgr0PzhrBPd3NtxGqYLWsuxIZsrds3r0mLJ8vG
 d2insMn50BRrukvXMf2IgmXcu+FWL8EgR8jBYeI4zpVrHoVciHn4S5rCLFm+ixINasz/
 N6Ng==
MIME-Version: 1.0
X-Received: by 10.194.202.229 with SMTP id kl5mr199726wjc.86.1398883882733;
 Wed, 30 Apr 2014 11:51:22 -0700 (PDT)
Received: by 10.194.179.70 with HTTP; Wed, 30 Apr 2014 11:51:22 -0700 (PDT)
Date: Wed, 30 Apr 2014 14:51:22 -0400
Message-ID: <CAHQQXOM_OBzsiLLxtUTFY1KQNAftz-GRQv3tV6zD3iENt9+jcg@mail.gmail.com>
Subject: RE: FreeBSD Security Advisory FreeBSD-SA-14:07.devfs
From: Corey Smith <corsmith@gmail.com>
To: freebsd-security@freebsd.org, matthew@freebsd.org, d@delphij.net
X-Mailman-Approved-At: Wed, 30 Apr 2014 19:18:32 +0000
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.17
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.17
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: Wed, 30 Apr 2014 18:51:25 -0000

> It would be interesting to find out if we could teach net-snmpd to use
> alternative methods to access data it needs

It is not necessary if you build net-mgmt/net-snmp with the UNPRIVILEGED
knob set.

-Corey Smith