Core dump when executing kdb5_util create command in Nevada
I the nevada builds before 82, if the /etc/krb5/krb5.conf file is misconfigured, executing kdb5_util create command encounters a SIGSEGV and dumps core. This issue is fixed in b82.
The most likely cause in my opinion is the comments in the krb5.conf file. Just a run a check if a delimiter or required directive is commented out.
The comments in the file are not the issue.
I was the engineer who fixed this bug. The bug was:
6612490 kdb5_util should not coredump if krb5.conf is misconfigured
I'm not sure why this isn't showing up on bugs.opensolaris.org. I opened a bug against MIT's Kerberos for the same issue where you can see the root cause/fix etc:
http://krbdev.mit.edu/rt/Ticket/Display.html?id=5873
Posted by Mark Phalan on February 01, 2008 at 06:28 PM IST #
Mark,
Thanks for the info and the bug fix. What I meant was that contrary to Solaris 10, values like default_realm are commented in Nevada vt default. I missed removing the comment for a closing } and that caused the core dump. On removing it, it worked fine. :-)
Posted by Madhan Kumar on February 01, 2008 at 09:52 PM IST #
Madhan,
Sorry I misunderstood you. The reason that the default_realm and other parts of krb5.conf are now commented-out is because we introduced "zero-conf" for kerberos clients - something I really must blog about...
Posted by Mark Phalan on February 01, 2008 at 10:46 PM IST #