[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Possible message multiplexing problem

> There is a multiplex ID; it is the IP address and port number of the  
> socket in use.  Multiple processes should not send requests from the  
> same port, because then the replies will go to the same port, and  
> the OS will not know which process should get which packet.  This is  
> a fundamental design property of UDP about which the Kerberos  
> protocol can do nothing; separate proceses need to use separate ports.


Kerberos should have had a local context id generated by the client,  
just like dns, to separate out diffrent request from each other from  
the same process, which is the problem here.