OpenSolaris

Printable Version Enter a New Search
Bug ID 6612490
Synopsis kdb5_util should not coredump if krb5.conf is misconfigured
State 10-Fix Delivered (Fix available in build)
Category:Subcategory kerberosv5_bundled:other
Keywords rtiq_reviewed
Responsible Engineer Mark Phalan
Reported Against snv_75
Duplicate Of
Introduced In solaris_10
Commit to Fix snv_82
Fixed In snv_82
Release Fixed solaris_nevada(snv_82) , solaris_10u6(s10u6_03) (Bug ID:2158244)
Related Bugs
Submit Date 3-October-2007
Last Update Date 31-January-2008
Description
When the krb5.conf file had the last brace commented out (by accident) in the [realms] section, if I attempted to run krb5_util command, it would repeatedly coredump even when using different arguments to command.  I suspect that other misconfiguration might also lead to coredumping as well.

krb5_util should not coredump if the krb5.conf file is misconfigured.  Here is some info about this issue:

# /usr/sbin/kdb5_util create -s
zsh: segmentation fault (core dumped)  /usr/sbin/kdb5_util create -s 

# pstack core
core 'core' of 824:     /usr/sbin/kdb5_util create -s
  fefc4f50 strlen   (1c7e5, ffbffc50, 0, 0, 0, 73) + 50
  ff00f084 fprintf  (2f318, 1c7e4, ff097c84, 8366c, ff092620, ff293548) + dc
  00014318 extended_com_err_fn (0, 96c73a88, 1c848, ffbffd10, 3000, 72954) + 34
  ff239708 com_err  (0, 96c73a88, 1c848, 96c73a88, 30740, 1c848) + 1c
  00014a8c main     (3, ffbffd84, 0, 1c400, 14000, 1c400) + 6a4
  00013d3c _start   (0, 0, 0, 0, 0, 0) + 108
kdb5_ldap_util has the same (dumping) behaviour.
Work Around
N/A
Comments
N/A