Ticket File Cached in Memory?

Greg Hudson ghudson at MIT.EDU
Thu Aug 27 11:12:35 EDT 2009

On Thu, 2009-08-27 at 09:41 -0400, John W. M. Stevens wrote:
> The core design, in a few sentences, is that of an event messaging
> (as in: OO messaging) system (asynchronous, parameters allowed but
> no returns) between "peers" where each peer has to be a kind of
> server, in that it can accept connections, authenticate them, then
> hand off the connection to a sub-process to process.

One option for this kind of protocol is to assign each message a unique
identifier, and essentially do your own replay detection.  (This also
works to eliminate retransmits, although that may not be an issue in the
first place with your architecture.)

> Is the replay cache stored in a file that, in the default install, is
> given a temporary name and put into a temporary directory?

Yes, generally in /var/tmp.  The name isn't actually temporary; it's
generally something like /var/tmp/host_0, where "host" is the name of
the service and 0 is the uid of the process.

More information about the krbdev mailing list