From owner-freebsd-security@freebsd.org Fri Sep 9 20:18:30 2016 Return-Path: Delivered-To: freebsd-security@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54522BD2476; Fri, 9 Sep 2016 20:18:30 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 21141399; Fri, 9 Sep 2016 20:18:29 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id DDD80273D6; Fri, 9 Sep 2016 20:13:04 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u89KD2bK067594; Fri, 9 Sep 2016 20:13:03 GMT (envelope-from phk@phk.freebsd.dk) To: Garrett Wollman cc: freebsd-arch@freebsd.org, freebsd-security@freebsd.org Subject: Re: Trying to think out a hack for NSS and pw(8) In-reply-to: <22483.5592.653250.726711@hergotha.csail.mit.edu> From: "Poul-Henning Kamp" References: <22483.5592.653250.726711@hergotha.csail.mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <67592.1473451982.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Fri, 09 Sep 2016 20:13:02 +0000 Message-ID: <67593.1473451982@critter.freebsd.dk> X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2016 20:18:30 -0000 -------- In message <22483.5592.653250.726711@hergotha.csail.mit.edu>, Garrett Woll= man w rites: > Puppet invokes pw(8) to actually perform the >modifications, but I suspect it also uses native code from the Ruby >standard library to actually do pre-modification lookups. >[...] >Looking at the code in both nss-pam-ldapd and libc, it seems like the >only plausible way to fix this is to add functionality to nsswitch >which would allow it to use different configurations depending on the >identity of the process invoking getpwnam(3) or getgrnam(3). You want to add a futher layer of complications to the the already far too complicated user/group/authentication code in FreeBSD, just because you don't want to look at Puppets Ruby code ? Really ? -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= .