Date: Tue, 5 Mar 2024 16:26:45 -0500 From: mike tancsa <mike@sentex.net> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: sftp chroot RELENG_14 vs RELENG_13 broken? Message-ID: <91d1ac9a-8a4f-4d65-a3af-bbc4b36366cb@sentex.net> In-Reply-To: <3c5a230c-e776-4ff1-a396-3e3c182af056@sentex.net> References: <3c5a230c-e776-4ff1-a396-3e3c182af056@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/5/2024 4:03 PM, mike tancsa wrote: > Hi all, > > Trying to stand up a new vm with RELENG_14 and cant for some > reason get chrooted logging working with the sftp server built into > the base openssh. > > On a RELENG_13 box, the following config works > > OK, truss to the rescue! If I create /var/run/log and hard link the socket there, it works on releng14. I guess the next question is where and when did that behaviour change ? The man page on RELENG_14 still says On some systems, sftp-server must be able to access /dev/log for logging to work, and use of sftp-server in a chroot configuration therefore requires that syslogd(8) establish a logging socket inside the chroot directory. ---Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?91d1ac9a-8a4f-4d65-a3af-bbc4b36366cb>