[2031] in Kerberos-V5-bugs
SGI ndbm routines confused--return too many entries
daemon@ATHENA.MIT.EDU (Sam Hartman)
Sat Jun 22 21:35:59 1996
Date: Sat, 22 Jun 1996 21:35:35 -0400
From: Sam Hartman <hartmans@MIT.EDU>
To: krb5-bugs@MIT.EDU
The database dump test fails on the build of krb5 in the
locker for the sgi_52 platform. It fails with a database record
incomplete error, because contents.dptr is null in krb5_kdb_iterate.
Apparently, what is happening is that after the 236th call to
dbm_nextkey, dbm_nextkey is getting confused. The 237th call returns
a bogus datum with the following properties:
* dsize is approximately 30000 (although not quite 32767)
* dptr points off into an RCS identification strings somewhere near
* des_SP_TABLE in libcrypto
I presume that either the krb5 dump code is stomping on
something (I didn't see anything obvious), or the SGI ndbm library is
broken. I am able to see 236 entries in the database when I execute
ldb, and I don't get an error. Either the error is not caught, or
there is no error. I'm going to play around with Perl and see what
keys are actually in the file.
--Sam
