> what did your update involve?
>
> I would wager that it updated some krb thing which sshd links to, and
> that re-emerging openssh may fix it.
Thanks, it sure did.
> OTOH if you don't really use kerberos you could take it out of the USE
> flags and rebuild openssh
Yeah, I'm getting rid of ker
On Fri, 26 Aug 2005 15:52:05 +1200
Nick Rout wrote:
> what did your update involve?
>
> I would wager that it updated some krb thing which sshd links to, and
> that re-emerging openssh may fix it.
>
> OTOH if you don't really use kerberos you could take it out of the USE
> flags and rebuild ope
what did your update involve?
I would wager that it updated some krb thing which sshd links to, and
that re-emerging openssh may fix it.
OTOH if you don't really use kerberos you could take it out of the USE
flags and rebuild openssh
On Thu, 25 Aug 2005 20:11:12 -0700
Grant wrote:
> All 3 of m
All 3 of my systems running sshd are having the same problem after a
big world update. sshd won't start and returns this:
/usr/sbin/sshd: symbol lookup error: /usr/sbin/sshd: undefined symbol:
krb5_init_ets
There doesn't seem to be a bug on it and there is no ~x86 version of
mit-krb5 to try. Do
4 matches
Mail list logo