Heimdal iProp ?

[Nicolas Williams]

Wyllys,

We have two incremental replication systems here.

One is built entirely around standard MIT krb5 stuff with zero mods and
all as shell scripting. The other, newer, not-quite-complete system mods
kadmind to support logging to Unix domain datagram sockets and the rest
is built as Perl 5 scripting using a Perl interface to libkdb and
libkrb5.

The former system is very simple, stupid. It listens on a pipe to which
syslogd() logs kadmind messages and uses "kdb_util dump <princ>" +
kprop to do its work.

The latter cuts out syslogd, is more reliable and very much follows the
Heimdal iprop model. We are also considering adapting this system to be
multi-master, at least for password changes.

If there's any interest I'll see what we can do about opening up our
source to the newer system.

Cheers,

Nico


On Mon, Apr 08, 2002 at 10:21:47AM -0400, Wyllys Ingersoll wrote:
> 
> I was just wondering what the consensus view is on the Heimdal iProp
> protocol and software.  I know that there was an effort at MIT to
> do something similar that hasnt yet come to fruition.  So, I was
> wondering about the pros/cons of the Heimdal incremental DB propogation
> software.
> 
> 
> thanks,
>    Wyllys Ingersoll
> 
> _______________________________________________
> krbdev mailing list             krbdev at mit.edu
> http://mailman.mit.edu/mailman/listinfo/krbdev
-- 
-DISCLAIMER: an automatically appended disclaimer may follow. By posting-
-to a public e-mail mailing list I hereby grant permission to distribute-
-and copy this message.-

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.