Received: from SOUTH-STATION-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA05933; Wed, 27 Dec 95 11:23:48 EST
Received: from OPUS.MIT.EDU by MIT.EDU with SMTP
	id AA26004; Wed, 27 Dec 95 11:21:58 EST
Received: by opus.MIT.EDU (931110.SGI/4.7) id AA10327; Wed, 27 Dec 95 11:22:09 -0500
Date: Wed, 27 Dec 95 11:22:09 -0500
Message-Id: <9512271622.AA10327@opus.MIT.EDU>
To: krbdev@MIT.EDU
Subject: Source routing (well, IP_OPTION) support?
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...