On 8/15/25 09:33, 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 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.
Peace,
david
