[963] in Kerberos_V5_Development
Source routing (well, IP_OPTION) support?
daemon@ATHENA.MIT.EDU (John Hawkinson)
Wed Dec 27 11:23:27 1995
Date: Wed, 27 Dec 95 11:22:09 -0500
To: krbdev@MIT.EDU
From: John Hawkinson <jhawk@MIT.EDU>
This morning I acutely felt the need for a kerberos suite that
supported loose source routing. Determined for the moment to implement
this, I think I need some guidance.
Being strictly client-side, the desired effect is for krb5_sendto_kdc
to call setsockopt() after socket() and before connect().
What's the right way to do this? I'm tempted to have a function
pointer to _krb5_os_context and have that called inbetween socket()
and connect() with the socket and struct sockaddr_in, to allow generic
support for mucking w/ IP_OPTIONS, TOS, or anything else that the
application wants.
Is this reasonable? Should it be architected differently?
Thanks.
--jhawk
ps: I finally started working on the krb5 decoder for tcpdump
(stealing lots from the snmp decoder). Getting there slowly but
surely...
