[19505] in Kerberos_V5_Development
Lookaside mechanism in KDC -- shared between processes?
daemon@ATHENA.MIT.EDU (Rick van Rein)
Thu Nov 10 11:04:31 2016
Message-ID: <58249A74.7080100@openfortress.nl>
Date: Thu, 10 Nov 2016 17:04:04 +0100
From: Rick van Rein <rick@openfortress.nl>
MIME-Version: 1.0
To: "krbdev@mit.edu" <krbdev@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
Hello,
For a project on the KDC code [1] I'm trying to understand how lookaside
processing in the KDC works, as implemented in kdc/replay.c --
specifically, how it reaches all the processes that run inside the KDC.
I found that the hash table is a static array, so it will be shared
among processes, but the entries are simply allocated with calloc() and
would therefore be specific to each process. So how can process A
detect that dispatch.c is active for a given KDC-REQ packet if that
packet is being dispatched from process B?
Thanks,
-Rick
[1] I'm trying to insert a link to a backend that uses DNSSEC/DANE for
realm crossover; it wants to avoid replaying a request about an
already-sought remote realm.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
