Justin T. Gibbs f4390542d7 Kerberos can now deal with multi-homed clients. ... Kerberos obtains a network address for the local host from the routing tables and uses it consistently for all Kerberos transactions. This ensures that packets only leave the *authenticated* interface. Clients who open and use their own sockets for encrypted or authenticated correspondance to kerberos services should bind their sockets to the same address as that used by kerberos. krb_get_local_addr() and krb_bind_local_addr() allow clients to obtain the local address or bind a socket to the local address used by Kerberos respectively. Reviewed by: Mark Murray <markm>, Garrett Wollman <wollman> Obtained from: concept by Dieter Dworkin Muller <dworkin@village.org>		1995-10-05 21:30:21 +00:00
..
addr_comp.h
admin_server.h
ChangeLog
conf-bsd386i.h
conf-bsdapollo.h
conf-bsdibm032.h
conf-bsdm68k.h
conf-bsdsparc.h
conf-bsdtahoe.h
conf-bsdvax.h
conf-ibm370.h
conf-pc.h
conf-pyr.h
conf-ultmips2.h
conf.h
des.h
highc.h
kadm.h
kdc.h
klog.h
kparse.h
krb_conf.h
krb_db.h
krb.h
lsb_addr_comp.h
Makefile
mit-copyright.h
osconf.h
passwd_server.h
principal.h
prot.h
rkinit_private.h
rkinit.h