On 8/15/25 09:42, Herbert J. Skuhra wrote:
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".
Hi,
*sigh* Fixed as of 08f5e06c5e3332de231 -- I have a test that exercises
this (setgroups_max in [0]) that I ran against the final version, but it
was missing the memset() there in the middle so it didn't notice that
every entry after the first hadn't been touched. Old sudo should work
again now, sorry about that.
Thanks,
Kyle Evans
[0] http://people.freebsd.org/~kevans/setgroups_test.c
