(abusing my "ping" trick....just tell me if that's completely useless)
>From the bug log one may see at http://bugs.debian.org/200342...or below, it seems that this bug has great chances to be over for ages now.... and was just sleeping in the BTS. Just a bet as I am miles away from the needed skills to really check this..:-) Andrew, I know *you* can give a motivated advice about this. Would you take care of pointing us in the right direction (hoping this will be "just close this bug"....) Otherwise (if there's still a bug, we might need to report this in samba's bugzilla)) Hi. The net lookup command seems to depend on the internal krb5 symbol krb5_locate_kdc (not included in krb5.h). Moreover the prototype of krb5_locate_kdc that Samba is expecting is not consistent with the prototype of this symbol in current MIT Kerberos. So the net lookup kdc code never seems to work. MIT Kerberos does not expose a public API for the functionality desired by net lookup kdc. I'm not sure what to do about this, but I'm sure that calling internal symbols with the wrong arguments is clearly wrong. Bug report: Hi. The net lookup command seems to depend on the internal krb5 symbol krb5_locate_kdc (not included in krb5.h). Moreover the prototype of krb5_locate_kdc that Samba is expecting is not consistent with the prototype of this symbol in current MIT Kerberos. So the net lookup kdc code never seems to work. MIT Kerberos does not expose a public API for the functionality desired by net lookup kdc. I'm not sure what to do about this, but I'm sure that calling internal symbols with the wrong arguments is clearly wrong. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
