Re: Status of Heimdal and Amavis
On Thu, Jan 30, 2003 at 09:57:52AM +1100, Brian May wrote:
> heimdal - I have got 5.1.1 compiling against unstable, but it does not
> detect krb4, because the libkrb (krb4) library cannot detect crypt, it
> would appear that libkrb4 needs to be linked against libcrypt. I have
> started discussing this issue with the appropriate maintainer.
I have worked around the bug in libkrb4, by manually linking
in with -lcrypt. Heimdal now builds on sid.
Heimdal appears to work fine, as far as I could test it on sid.
Hence I will upload it to Debian ASAP.
However, the version I compiled for woody is a different
story.
snoopy:unstable:~# netstat --tcp -a -n -p | grep kdc
tcp 0 0 226.122.44.64:4352 0.0.0.0:* LISTEN 8355/kdc
tcp 0 0 226.122.44.64:512 0.0.0.0:* LISTEN 8355/kdc
tcp 0 0 226.122.44.64:4992 0.0.0.0:* LISTEN 8355/kdc
tcp 0 0 226.122.44.64:4993 0.0.0.0:* LISTEN 8355/kdc
tcp 0 0 226.122.44.64:4994 0.0.0.0:* LISTEN 8355/kdc
tcp 0 0 203.12.237.97:750 0.0.0.0:* LISTEN 8355/kdc
tcp 0 0 203.12.237.110:750 0.0.0.0:* LISTEN 8355/kdc
tcp 0 0 203.12.237.97:4444 0.0.0.0:* LISTEN 8355/kdc
tcp 0 0 203.12.237.110:4444 0.0.0.0:* LISTEN 8355/kdc
tcp 0 0 226.122.44.64:4990 0.0.0.0:* LISTEN 8355/kdc
tcp 0 0 226.122.44.64:4991 0.0.0.0:* LISTEN 8355/kdc
snoopy:unstable:~# ifconfig | grep 226.122.44.64
snoopy:unstable:~# ping 226.122.44.64
PING 226.122.44.64 (226.122.44.64): 56 data bytes
--- 226.122.44.64 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
Why is KDC binding to addresses I don't have, to ports that
are not Kerberos ports? Why is it not listening to the Kerberos
ports? Why does this only happen when compiling against woody,
not sid?
(note: the 203.12.237.97 and 203.12.237.110 addresses are correct).
This is truely wierd.
--
Brian May <bam@debian.org>
Reply to: