From owner-freebsd-amd64@freebsd.org  Mon Feb  6 13:53:35 2017
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@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 71F21CD203C
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Mon,  6 Feb 2017 13:53:35 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 61D88DD4
 for <freebsd-amd64@FreeBSD.org>; Mon,  6 Feb 2017 13:53:35 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v16DrYA1048862
 for <freebsd-amd64@FreeBSD.org>; Mon, 6 Feb 2017 13:53:35 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 209441] SSHd in FreeBSD 10.3 complains about PrintLastLog
Date: Mon, 06 Feb 2017 13:53:34 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 10.3-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: smh@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-209441-6-eUQB6VTqFK@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209441-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-209441-6@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 13:53:35 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209441

Steven Hartland <smh@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |re@FreeBSD.org,
                   |                            |smh@FreeBSD.org

--- Comment #7 from Steven Hartland <smh@FreeBSD.org> ---
Based on the commit message for
https://svnweb.freebsd.org/base?view=3Drevision&revision=3D247893 is sounds=
 like
this this should never worked in 10 and was only there as the configure scr=
ipt
incorrectly detected utmp / lastlog.

That said it appears that lastlog in sshd supports utmpx via getutxuser.

Digging some more it seems like this may well be a change in behaviour of t=
he
openssh DISABLE_LASTLOG from the upstream 7.2p1 change set:
e#diff-267d507f9cf4a70e051aaeecb89ad93bR509


This wasn't merged through until 7.2p2:
https://svnweb.freebsd.org/base?view=3Drevision&revision=3D296633

Given this I think this was unintended and there should a new commit to rem=
ove
--disable-lastlog which was added here:
https://svnweb.freebsd.org/base/head/crypto/openssh/FREEBSD-upgrade?r1=3D24=
7892&r2=3D247891&pathrev=3D247892

--=20
You are receiving this mail because:
You are on the CC list for the bug.=