[39471] in Kerberos
Re: Restoring DB to alternate LDAP suffix
daemon@ATHENA.MIT.EDU (Greg Hudson)
Thu Jan 30 00:33:51 2025
Message-ID: <33440bd5-c7d5-4868-a616-297ec20c116e@mit.edu>
Date: Thu, 30 Jan 2025 00:33:29 -0500
MIME-Version: 1.0
To: Jake Scott <jake@poptart.org>
Cc: kerberos@mit.edu
Content-Language: en-US
From: "Greg Hudson" <ghudson@mit.edu>
In-Reply-To: <CAExmWciERhM+GREyppiJyvCo6_9Lf7hTvKKxR28Z2z6pYEmrVw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: kerberos-bounces@mit.edu
Content-Transfer-Encoding: 8bit
On 1/29/25 21:57, Jake Scott wrote:
> One thing — I did try restoring the dump to a file based database and
> then dump/restoring again to LDAP and the same issue happened so I
> assume that the LDAP data ends up in the file DB as well - is that also
> what you expect?
That's also expected. The LDAP KDB module synthesizes and interprets
the type-255 tl-data; other modules don't know anything about it, so
they just store it and replay it.
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
