Package: heimdal-kdc
Version: 7.1.0+dfsg-13
Severity: normal

My kdc has been periodically (once every few weeks maybe) crashing.  I
finally got around to looking for core files and found one.  Here's
the backtrack:

#0  der_length_visible_string (data=0x18) at der_length.c:245
#1  0x00007f8dde132546 in length_PROV_SRV_LOCATION (data=<optimized out>) at 
asn1_krb5_asn1.c:7644
#2  0x00007f8dde13d370 in length_KRB_ERROR (data=data@entry=0x7fff59b22b80) at 
asn1_krb5_asn1.c:12827
#3  0x00007f8dde85bdab in krb5_mk_error_ext 
(context=context@entry=0x560faae820b0,
    error_code=<optimized out>, error_code@entry=-1765328324, e_text=<optimized 
out>,
    e_text@entry=0x7f8ddece5e67 "No client in request", e_data=0x0,
    server=server@entry=0x560faae87510, client_name=client_name@entry=0x0, 
client_realm=0x18,
    client_time=0x0, client_usec=0x0, reply=0x7fff59b23490) at mk_error.c:85
#4  0x00007f8ddecd63cb in _kdc_fast_mk_error 
(context=context@entry=0x560faae820b0,
    r=r@entry=0x7fff59b23050, error_method=error_method@entry=0x7fff59b22e80, 
armor_crypto=0x0,
    req_body=req_body@entry=0x7fff59b23080, 
outer_error=outer_error@entry=-1765328324,
    e_text=0x7f8ddece5e67 "No client in request", error_server=0x560faae87510, 
error_client_name=0x0,
    error_client_realm=0x18, csec=0x0, cusec=0x0, error_msg=0x7fff59b23490) at 
fast.c:331
#5  0x00007f8ddecd8957 in _kdc_as_rep (r=r@entry=0x7fff59b23050, 
reply=reply@entry=0x7fff59b23490,
    from=from@entry=0x560faae89e3c "IPv4:80.82.77.139", 
from_addr=from_addr@entry=0x560faae89db0,
    datagram_reply=datagram_reply@entry=1) at kerberos5.c:2231
#6  0x00007f8ddece3df9 in kdc_as_req (context=0x560faae820b0, 
config=0x560faae84a90,
    req_buffer=0x7fff59b23400, reply=0x7fff59b23490, from=0x560faae89e3c 
"IPv4:80.82.77.139",
    addr=0x560faae89db0, datagram_reply=1, claim=0x7fff59b233fc) at process.c:77
#7  0x00007f8ddece3f45 in krb5_kdc_process_request 
(context=context@entry=0x560faae820b0,
    config=config@entry=0x560faae84a90,
    buf=buf@entry=0x560faae8ab50 
"j\201n0\201k\241\003\002\001\005\242\003\002\001\n\244\201^0\\\240\a\003\005", 
len=len@entry=113, reply=reply@entry=0x7fff59b23490,
    prependlength=prependlength@entry=0x7fff59b2348c, from=0x560faae89e3c 
"IPv4:80.82.77.139",
    addr=0x560faae89db0, datagram_reply=1) at process.c:208
#8  0x0000560fa94039c8 in do_request (context=context@entry=0x560faae820b0,
    config=config@entry=0x560faae84a90, buf=buf@entry=0x560faae8ab50, 
len=len@entry=113,
    prependlength=<optimized out>, prependlength@entry=0, 
d=d@entry=0x560faae89d80) at connect.c:435
#9  0x0000560fa94042d5 in handle_udp (d=0x560faae89d80, config=0x560faae84a90, 
context=0x560faae820b0)
    at connect.c:495
#10 loop (context=context@entry=0x560faae820b0, 
config=config@entry=0x560faae84a90,
    d=<optimized out>, d@entry=0x560faae899c0, ndescr=<optimized out>, 
ndescr@entry=10, islive=4)
    at connect.c:947
#11 0x0000560fa940535f in start_kdc (context=<optimized out>, 
config=0x560faae84a90,
    argv0=<optimized out>) at connect.c:1184
#12 0x0000560fa94031b0 in main (argc=<optimized out>, argv=0x7fff59b23e88) at 
main.c:176

It appears the IP in this case belongs to a crawler, but I don't know
if that's always the case.  I have the core file if that would be
useful to someone.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages heimdal-kdc depends on:
ii  debconf                           1.5.62
ii  heimdal-clients                   7.1.0+dfsg-13
ii  krb5-config                       2.6
ii  libasn1-8-heimdal                 7.1.0+dfsg-13
ii  libc6                             2.24-12
ii  libcap-ng0                        0.7.7-3+b1
ii  libdb5.3                          5.3.28-12+b1
ii  libedit2                          3.1-20170329-1
ii  libgssapi3-heimdal                7.1.0+dfsg-13
ii  libhcrypto4-heimdal               7.1.0+dfsg-13
ii  libhdb9-heimdal                   7.1.0+dfsg-13
ii  libheimbase1-heimdal              7.1.0+dfsg-13
ii  libheimntlm0-heimdal              7.1.0+dfsg-13
ii  libkadm5srv8-heimdal              7.1.0+dfsg-13
ii  libkdc2-heimdal                   7.1.0+dfsg-13
ii  libkrb5-26-heimdal                7.1.0+dfsg-13
ii  libroken18-heimdal                7.1.0+dfsg-13
ii  libsl0-heimdal                    7.1.0+dfsg-13
ii  lsb-base                          9.20161125
ii  openbsd-inetd [inet-superserver]  0.20160825-2

Versions of packages heimdal-kdc recommends:
ii  logrotate  3.11.0-0.1

Versions of packages heimdal-kdc suggests:
ii  heimdal-docs  7.1.0+dfsg-13

-- Configuration Files:
/etc/default/heimdal-kdc changed:
KDC_ENABLED=yes
KDC_PARAMS="--config-file=/etc/krb5.conf"
KPASSWDD_ENABLED=yes
KPASSWDD_PARAMS=""
MASTER_ENABLED=no
SLAVE_ENABLED=no
SLAVE_PARAMS=""

/etc/logrotate.d/heimdal-kdc [Errno 2] No such file or directory: 
'/etc/logrotate.d/heimdal-kdc'

-- debconf information excluded

Reply via email to