kadmin core dumping

I have had this problem for a very long time.  I really haven't found
anything I can point my finger at about this, but it seems like there is
something wrong with the key generation:

A simple thing like

kadmin -l
kadmin> init MCNEIL.COM

would core dump with

#11 0x0000000000000000 in ?? ()
#12 0x00000002009863ca in krb5_string_to_key_data_salt_opaque (
    context=0xc0f02010, enctype=201589254, password=
      {length = 6, data = 0x408d78}, salt=
        {salttype = KRB5_PW_SALT, saltvalue = {length = 26, data = 0x50f320}},
    opaque={length = 0, data = 0x0}, key=0x7)
    at /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/crypto.c:1007
#13 0x0000000200986321 in krb5_string_to_key_data_salt (context=0xcc182000,
    enctype=-955776509, password={length = 6, data = 0x408d78}, salt=
        {salttype = KRB5_PW_SALT, saltvalue = {length = 26, data = 0x50f320}},
    key=0x7fffffffe858)

I've always suspected that I have something old in my system that is
causing this.  Now I wonder if it isn't openssl from the ports.  For
some reason, kadmin is linked with libcrypto.so.3 instead of the
libcrypto.so in /usr/lib:

/usr/bin/kadmin:
        libkadm5clnt.so.7 => /usr/lib/libkadm5clnt.so.7 (0x200636000)
        libkadm5srv.so.7 => /usr/lib/libkadm5srv.so.7 (0x20073f000)
        libhdb.so.7 => /usr/lib/libhdb.so.7 (0x20084d000)
        libkrb5.so.7 => /usr/lib/libkrb5.so.7 (0x200960000)
        libroken.so.7 => /usr/lib/libroken.so.7 (0x200aa9000)
        libasn1.so.7 => /usr/lib/libasn1.so.7 (0x200bb9000)
        libcrypto.so.3 => /usr/local/lib/libcrypto.so.3 (0x200ce2000)
        libcrypt.so.2 => /lib/libcrypt.so.2 (0x200f30000)
        libcom_err.so.2 => /usr/lib/libcom_err.so.2 (0x201049000)
        libreadline.so.4 => /lib/libreadline.so.4 (0x20114b000)
        libncurses.so.5 => /lib/libncurses.so.5 (0x201285000)
        libldap-2.2.so.7 => /usr/local/lib/libldap-2.2.so.7
(0x2013e0000)
        liblber-2.2.so.7 => /usr/local/lib/liblber-2.2.so.7
(0x201519000)
        libc.so.5 => /lib/libc.so.5 (0x201628000)
        libsasl2.so.2 => /usr/local/lib/libsasl2.so.2 (0x20182c000)
        libssl.so.3 => /usr/local/lib/libssl.so.3 (0x201944000)

Could this be a problem, or is it just in there because sasl is?

Sean