Re: sshd-session (sshd on conect) crashes with signal 6

On Fri, Aug 15, 2025 at 09:41:25AM -0500, Kyle Evans wrote:
> ...
> > 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 haven't really had enough coffee this morning, can you expand on your
> concerns a little more, please?  These changes introduced an entirely new
> version of the syscalls and retained COMPAT14 versions so that, e.g., 14.x
> jails should still do what they've always done.
> 
> > (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.)
> > 
> 
> I think I'm missing some context, what problem is this referring to?
> 
> > This may become a more pressing issue when folks start upgrading from
> > 14 to 15.
> ....

From
https://lists.freebsd.org/archives/freebsd-current/2025-August/008401.html

| I also note that "sudo" claims my login isn't in sudoers; while that
| is (technically) true, it has been thus for years: I'm using group
| membership (in "wheel" -- as I have for decades), though "groups"
| seems to detect the group membership OK.

(I am not using jails.  I have machines set up to boot from any of
the 4 slices; slice 1 is presently stable/14; slice 4 is presently
head.  The file system where /usr/local resides remains the same,
regardless of which slice is booted.  Ports are built under stable/*.
Yeah, it's "old school" -- been doing this way for about 25 years.)

Peace,
david
-- 
David H. Wolfskill                              david@catwhisker.org
Of course firing the statistician will force the statistics to conform!

See https://www.catwhisker.org/~david/publickey.gpg for my public key.