From owner-freebsd-current@freebsd.org  Fri Apr 20 13:42:31 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE141FA4B30
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Fri, 20 Apr 2018 13:42:30 +0000 (UTC)
 (envelope-from emaste@freebsd.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "freefall.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id A06A574B0F
 for <freebsd-current@freebsd.org>; Fri, 20 Apr 2018 13:42:30 +0000 (UTC)
 (envelope-from emaste@freebsd.org)
Received: by freefall.freebsd.org (Postfix, from userid 1079)
 id 97D11B7AC; Fri, 20 Apr 2018 13:42:30 +0000 (UTC)
Date: Fri, 20 Apr 2018 13:42:30 +0000
From: Ed Maste <emaste@freebsd.org>
To: freebsd-current@freebsd.org
Subject: HEADS-UP: Deprecation of legacy (v3) password database support
Message-ID: <20180420134230.GB62725@freebsd.org>
Mail-Followup-To: Ed Maste <emaste@freebsd.org>,
	freebsd-current@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.9.2 (2017-12-15)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2018 13:42:31 -0000

FreeBSD password databases (/etc/pwd.db, /etc/spwd.db) can contain
records in one or both of two versions:
 * v3, a legacy architecture-dependent format
 * v4, the current architecture- and endian-independent format

When v4 support was added in 2003 (r113596) pwd_mkdb emitted both v3 and
v4 records in the output database.  In 2015 r283981 added a -l option to
control the emission of legacy v3 records; by default only v4 records
are emitted.

r283981's commit message states:

    The -l, -B and -L options are considered deprecated and will be
    removed in FreeBSD 12.0 release.

I'd expect little impact if the -l, -B and -L options are removed, as
r113596 is included in FreeBSD 5.1 and later.  If legacy support is
removed then software built on FreeBSD 5.0 or earlier will no longer be
able to make use of password file data (via getpwent, getpwnam, etc.).
Such software would still function inside of a jail that has a v3
password database, of course.

Is anyone using pwd_mkdb's -l option and relying on legacy password
database files in a non-jailed context?