From owner-freebsd-bugs@freebsd.org  Mon Feb  6 15:17:04 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 414CBCD3B02
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Mon,  6 Feb 2017 15:17:04 +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 30FBC5ED
 for <freebsd-bugs@FreeBSD.org>; Mon,  6 Feb 2017 15:17:04 +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 v16FH2cu080339
 for <freebsd-bugs@FreeBSD.org>; Mon, 6 Feb 2017 15:17:04 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 209441] SSHd in FreeBSD 10.3 complains about PrintLastLog
Date: Mon, 06 Feb 2017 15:17:03 +0000
X-Bugzilla-Reason: AssignedTo
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: des@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: des@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-209441-8-WBFvdCdcSN@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209441-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-209441-8@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-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 15:17:04 -0000

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

Dag-Erling Sm=C3=83=C2=B8rgrav <des@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Open
           Assignee|freebsd-bugs@FreeBSD.org    |des@FreeBSD.org

--- Comment #8 from Dag-Erling Sm=C3=83=C2=B8rgrav <des@FreeBSD.org> ---
Miroslav: the problem is (or was, at the time) that the configure script lo=
oks
for the actual log files rather than the APIs.  If you try to build OpenSSH=
 on
a machine that was upgraded from an older FreeBSD version and still has old=
 log
files lying around, the configure script will enable lastlog and the build =
will
fail.  Conversely, it may incorrectly disable lastlog on a system that supp=
orts
it if you try to configure and build in a pristine chroot or jail (like
poudriere does), because the log files aren't created until someone logs in.

Steven: the bug is not that PrintLastLog doesn't work. It *can't* work, bec=
ause
FreeBSD doesn't have that API any more. The bug is that it is still documen=
ted.

--=20
You are receiving this mail because:
You are the assignee for the bug.=