Date: Fri, 20 Oct 2023 06:26:18 +0900 From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> To: stable@freebsd.org Subject: Re: FreeBSD Errata Notice FreeBSD-EN-23:09.freebsd-update [REVISED] Message-ID: <20231020062618.9618dcfd42b083720d5dbd12@dec.sakura.ne.jp> In-Reply-To: <c0a1d1b3-171b-443d-bedb-a5a8938219eb@quip.cz> References: <20231003230335.0B92113333@freefall.freebsd.org> <aaabb189-b0df-4bd2-94d2-12d407b080b1@twcny.rr.com> <E5535DBD-9199-4151-A485-119E5CD02EA2@libassi.se> <765ea31d-8f07-4916-b6fd-ba220dec80dc@inoc.net> <c0a1d1b3-171b-443d-bedb-a5a8938219eb@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 19 Oct 2023 19:53:08 +0000 Miroslav Lachman <000.fbsd@quip.cz> wrote: > On 19/10/2023 16:19, Robert Blayzor wrote: > > On 10/4/23 00:45, Peter Libassi wrote: > >> Me too! My sshd_config is also customized and everytime there is a new > >> patch I need to run freebsd-update manually and get rid of the attempt > >> to trash the sshd config that could make my server unreachable over > >> the network. > >> > >> Why does the freebsd-update need a vanilla sshd_config? > > > > > > Or put your custom sshd config in another location and just update rc.conf: > > > > sshd_flags="-f /path/to/my/sshd_config" > > It is hackery workaround. freebsd-update must not overwrite user > modified files without safe merge of conflicts. yet it did it in the > past, for example pf.conf and some other vital files. > > Kind regards > Miroslav Lachman I don't think it hackery. What should have been is that default sshf_config to be in /etc/defaults and /etc/defaults/rc.conf points to it, and anyone needs custom settings to create sshd_config in /etc/ssh (or in somewhere else), like rc.conf case. -- Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20231020062618.9618dcfd42b083720d5dbd12>