| commit | 168627e1877317db86471a4b0360dccd9f469aaa | |
| author | Günther Deschner <gd@samba.org> | |
| Mon, 13 Jan 2014 14:59:26 +0000 (13 15:59 +0100) | ||
| committer | Günther Deschner <gd@samba.org> | |
| Fri, 7 Mar 2014 15:16:54 +0000 (7 16:16 +0100) | ||
| tree | 07e185c09679ece83b013fde4f73f5b5ab4b1b4a | treesnapshot (tar.gz zip) |
| parent | f7883ae02a4e8935a44396f776712cebfd411e52 | commitdiff |
s3-kerberos: remove print_kdc_line() completely.
Just calling print_canonical_sockaddr() is sufficient, as it already deals with
ipv6 as well. The port handling, which was only done for IPv6 (not IPv4), is
removed as well. It was pointless because it always derived the port number from
the provided address which was either a SMB (usually port 445) or LDAP
connection. No KDC will ever run on port 389 or 445 on a Windows/Samba DC.
Finally, the kerberos libraries that we support and build with, can deal with
ipv6 addresses in krb5.conf, so we no longer put the (unnecessary) burden of
resolving the DC name on the kerberos library anymore.
Guenther
Signed-off-by: Günther Deschner <gd@samba.org>
Reviewed-by: Andreas Schneider <asn@samba.org>
Just calling print_canonical_sockaddr() is sufficient, as it already deals with
ipv6 as well. The port handling, which was only done for IPv6 (not IPv4), is
removed as well. It was pointless because it always derived the port number from
the provided address which was either a SMB (usually port 445) or LDAP
connection. No KDC will ever run on port 389 or 445 on a Windows/Samba DC.
Finally, the kerberos libraries that we support and build with, can deal with
ipv6 addresses in krb5.conf, so we no longer put the (unnecessary) burden of
resolving the DC name on the kerberos library anymore.
Guenther
Signed-off-by: Günther Deschner <gd@samba.org>
Reviewed-by: Andreas Schneider <asn@samba.org>
| source3/libads/kerberos.c | diffblobblamehistory |