[3533] in Kerberos
c_sock and s_sock in mk_priv
daemon@ATHENA.MIT.EDU (Porlin Kang)
Tue Jul 12 23:46:47 1994
To: kerberos@MIT.EDU
Date: Tue, 12 Jul 1994 22:48:06 -0400
From: Porlin Kang <pk2k+@andrew.cmu.edu>
Hello,
I am trying to use rpc as the communication channel, instead of sockets.
However, krb_mk_priv and rd_priv needs the c_sock and s_sock of
the client and server. If all mk_priv needs is just the ip address
without port, then everything will be fine (I could make a call to map
hostname to ip addr).
Could anyone please tell me if ip port is really needed by the mk_priv
and rd_priv ? I looked into mk_priv.c and found that c_sock->sin_port
is manipulated by lsb_addr_comp.h macros. And these macros have something
to do with LSB. The comment in mk_priv.c stated that this is intended to
fix some broken old code.
So, it seems to me that port # is not important in the c_sock and s_sock
of the mk_priv call. So, to use this call, I will fill the c_sock and s_sock
with the ip address, and ignore the port (because I am using rpc with
a dynamic port mapping). Is this devastating ?
thanks in advance,
-porlin
