Date: Fri, 8 Aug 2025 15:22:44 +0200 From: Rodrigo Osorio <rodrigo@osorio.me> To: freebsd-current@freebsd.org Subject: Re: ssh errors, libgssapi_krb5 Message-ID: <79071b68-4e4a-4cdf-8633-8aa8faabafd2@osorio.me> In-Reply-To: <20250728180314.2BFB328C@slippy.cwsent.com> References: <aId7_7d5iFCxQhLI@freefall.freebsd.org> <701d3288-4aec-47bd-b7e2-4ee49bab3f2e@betaapp.fastmail.com> <aIeDuZzC0FJGG0II@freefall.freebsd.org> <20250728180314.2BFB328C@slippy.cwsent.com>
index | next in thread | previous in thread | raw e-mail
On 28/07/25 20:03, Cy Schubert wrote: > In message <aIeDuZzC0FJGG0II@freefall.freebsd.org>, Lexi Winter writes: >> Herbert: >>> On Mon, 28 Jul 2025, at 15:32, Lexi Winter wrote: >>>> dlopen: Cannot open "/usr/lib/libgssapi_krb5.so.121" >>>> git@git.le-fay.org: Permission denied (publickey,gssapi-with-mic). >>> =20 >>> Have you rebuilt ports like curl, git, etc.? >> this isn't related to ports, it happens with /usr/bin/ssh as well. >> i probably should have mentioned that. >> >> but oddly, after rebuilding main with no changes and updating again, ssh >> now works fine. >> >> but i don't really understand what broke it to begin with... what causes >> ssh to load libgssapi_something? > The DSO bump broke gssapi/mech. The mech file was updated last night to > point to the current DSO. > > Hi, I fall in the same issue and multiple ports still asking for 121 version. As Herbert suggest, I think impacted ports revision should be bumped to force recompilation. What @portmgr think about how to solve this issue ? regards, -- rodrigohome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?79071b68-4e4a-4cdf-8633-8aa8faabafd2>