[Bug 209441] SSHd in FreeBSD 10.3 complains about PrintLastLog
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue May 10 23:56:20 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209441
Bug ID: 209441
Summary: SSHd in FreeBSD 10.3 complains about PrintLastLog
Product: Base System
Version: 10.3-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: bin
Assignee: freebsd-bugs at FreeBSD.org
Reporter: 000.fbsd at quip.cz
CC: freebsd-amd64 at FreeBSD.org
CC: freebsd-amd64 at FreeBSD.org
I had "PrintLastLog yes" in my sshd_config for many years but after upgrade to
10.3 I got this error message:
/etc/ssh/sshd_config line 112: Unsupported option PrintLastLog
It is confusing because "#PrintLastLog yes" is still included in default
sshd_config file and mentioned in manpage.
Is it error in default config or error in sshd? What should be fixed?
I found in /usr/src/crypto/openssh/servconf.c
#ifdef DISABLE_LASTLOG
{ "printlastlog", sUnsupported, SSHCFG_GLOBAL },
#else
{ "printlastlog", sPrintLastLog, SSHCFG_GLOBAL },
#endif
Does it means that new sshd in FreeBSD 10.3 was (un)intentionally compiled with
"DISABLE_LASTLOG" (--disable-lastlog)
We have own buildserver with svnup /usr/src and buildworld & buildkernel and
installkernel & installworld
# cat /etc/src.conf
WITHOUT_KERNEL_SYMBOLS=yes
# cat /etc/make.conf
WITH_PKGNG= yes
SVN_UPDATE=yes
SVN="/usr/local/bin/svnup"
SVNFLAGS=""
WITH_GHOSTSCRIPT_VER=9
DEFAULT_VERSIONS= perl=5.20 mysql=5.5m php=55 python=2.7 apache=2.4
## https://wiki.freebsd.org/Ports/Options/OptionsNG
## OptionsNG sets DOCS, EXAMPLES and NLS as default - we do not need them
OPTIONS_UNSET= X11 GUI CUPS DOCS EXAMPLES NLS
## cd /usr/ports/www/apache22 && make print-closest-mirrors
MASTER_SITE_APACHE_HTTPD?= http://apache.miloslavbrada.cz/httpd/
http://mirror.hosting90.cz/apache/httpd/
ftp://mirror.hosting90.cz/apache/httpd/ http://www.eu.apache.org/dist/httpd/
## closest PHP mirror
MASTER_SITE_PHP= http://cz.php.net/%SUBDIR%/
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-amd64
mailing list