Date: Fri, 15 Aug 2025 16:42:09 +0200 From: "Herbert J. Skuhra" <herbert@gojira.at> To: David Wolfskill <david@catwhisker.org>, Kyle Evans <kevans@freebsd.org>, current@freebsd.org Subject: Re: sshd-session (sshd on conect) crashes with signal 6 Message-ID: <871ppcfxz2.wl-herbert@gojira.at> In-Reply-To: <aJ9FNjorqdJbQ9LS@albert.catwhisker.org> References: <595365288.15536127.1755259580702.JavaMail.zimbra@pickering.cz> <87349sg2om.wl-herbert@gojira.at> <aJ8xgjMuWqq1sWO5@albert.catwhisker.org> <74e3a0e5-9681-43a1-a45f-9ea45783599a@FreeBSD.org> <aJ9FNjorqdJbQ9LS@albert.catwhisker.org>
index | next in thread | previous in thread | raw e-mail
On Fri, 15 Aug 2025 16:33:26 +0200, David Wolfskill wrote: > > On Fri, Aug 15, 2025 at 08:23:24AM -0500, Kyle Evans wrote: > > ... > > Yes, very sorry about that- I've reverted the openssh change in > > 207cf8773aa7600b340cf673d973add10d9031e5. It needed to be reverted after > > the above-mentioned change anyways, but I forgot to roll that into it. > > Apologies- > > .... > > OK; thanks for the quick response: I confirm that that fixes ssh in my > case. > > However, I suspect that in the case (as for me) where (e.g.) sudo > is built under stable/14, but one attempts to use it under head > after main-n279619-9da2fe96ff2e will be "problematic," at best. > > (I just tested and confirmed that I was able to circumvent the problem > in my case by augmenting the "sudoers" file "%wheel" group entry with a > user-specific entry for me.) > > This may become a more pressing issue when folks start upgrading from > 14 to 15. I had to rebuild sysutils/sudo on arm64 only, because it failed with "$user is not in the sudoers file".home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?871ppcfxz2.wl-herbert>