Date: Mon, 06 Feb 2017 13:53:34 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 209441] SSHd in FreeBSD 10.3 complains about PrintLastLog Message-ID: <bug-209441-8-5OkRHinrzf@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/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209441 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=revision&revision=247893 is sounds like this this should never worked in 10 and was only there as the configure script 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 the 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=revision&revision=296633 Given this I think this was unintended and there should a new commit to remove --disable-lastlog which was added here: https://svnweb.freebsd.org/base/head/crypto/openssh/FREEBSD-upgrade?r1=247892&r2=247891&pathrev=247892 -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209441-8-5OkRHinrzf>