Date: Thu, 29 Feb 2024 05:12:29 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 269025] fortune doesn't honor hushlogin Message-ID: <bug-269025-227-jNBCkbCfID@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-269025-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269025 Tatsuki Makino <tatsuki_makino@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tatsuki_makino@hotmail.com --- Comment #3 from Tatsuki Makino <tatsuki_makino@hotmail.com> --- I have wondered the same thing a very long time ago :) Existence of ~/.hushlogin changes the behavior of login(1) and sshd(8). https: //cgit.freebsd.org/src/tree/usr.bin/login/login.c?h=releng/14.0#n444 https: //cgit.freebsd.org/src/tree/crypto/openssh/session.c?h=releng/14.0#n824 login(1) also behaves differently depending on ~/.login_conf. It is enabled by writing me:hushlogin: https: //cgit.freebsd.org/src/tree/usr.bin/login/login.c?h=releng/14.0#n416 It seems that sshd(8) is not reading ~/.login_conf. It may have been read, but it seems that hushlogin has not been picked up. https: //cgit.freebsd.org/src/tree/crypto/openssh/session.c?h=releng/14.0#n1384 The existence of a file is one condition, but there are also conditions under which it is no longer needed when the file does not exist. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-269025-227-jNBCkbCfID>