https://k5wiki.kerberos.org/wiki?action=history&feed=atom&title=Projects%2FDB_Entry_Redesign 2026-04-22T08:54:08Z Revision history for this page on the wiki MediaWiki 1.27.4 https://k5wiki.kerberos.org/wiki?title=Projects/DB_Entry_Redesign&diff=3394&oldid=prev 2010-07-20T09:57:51Z

<p>New page: {{project-early}} This project has been split out of <a href="/wiki/Projects/Database_Access_Layer_cleanup" title="Projects/Database Access Layer cleanup">Projects/Database Access Layer cleanup</a>. ==Background== The current in-memory data structure for KDB principal entries is designe...</p> <p><b>New page</b></p><div>{{project-early}}<br /> <br /> This project has been split out of [[Projects/Database Access Layer cleanup]].<br /> <br /> ==Background==<br /> <br /> The current in-memory data structure for KDB principal entries is designed around the needs of the DB2 module. As a result, it is at times cumbersome to use by the KDB and kadmind, which must search through the tl_data table for information not originally represented in DB2 databases.<br /> <br /> ==Goals==<br /> <br /> This project is to redesign the in-memory structure for KDB principal entries, either by making it totally opaque, or just by making it more logical from the perspective of the KDC and kadmind. Specific desirables include:<br /> <br /> * Eliminate e_length, e_data, and tl_data, replacing them with the logical elements currently stored using tl_data.<br /> * Provide a well-defined place for module-specific entry data.<br /> * Abstract key data accesses through a functional interface, to better handle AD-style modules which store the password rather than a list of keys.</div>

Ghudson