Hide Forgot
+++ This bug was initially created as a clone of Bug #1175511 +++ Description of problem: wbinfo -K <user> causes a segfault Version-Release number of selected component (if applicable): 4.1.13-1 How reproducible: 100% Steps to Reproduce: 1. In cases where kerberos auth fails, do: 2. wbinfo -K <user> 3. Actual results: Enter vverma7's password: plaintext kerberos password authentication for [vverma7] failed (requesting cctype: FILE) Segmentation fault (core dumped) Expected results: Additional info: Backtrace: (gdb) r Starting program: /usr/bin/wbinfo -K vverma7 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Enter vverma7's password: plaintext kerberos password authentication for [vverma7] failed (requesting cctype: FILE) Program received signal SIGSEGV, Segmentation fault. wbinfo_auth_krb5 (username=0x5555557625e0 "vverma7", cctype=0x55555555e588 "FILE", flags=28690) at ../nsswitch/wbinfo.c:1572 1572 d_fprintf(stderr, Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.6-14.fc21.x86_64 libtdb-1.3.1-1.fc21.x86_64 libtevent-0.9.21-3.fc21.x86_64 (gdb) bt #0 wbinfo_auth_krb5 (username=0x5555557625e0 "vverma7", cctype=0x55555555e588 "FILE", flags=28690) at ../nsswitch/wbinfo.c:1572 #1 0x00005555555584bb in main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at ../nsswitch/wbinfo.c:2557 (gdb) p *error Cannot access memory at address 0x1 (gdb) q --- Additional comment from David Woodhouse on 2014-12-17 18:56:21 EST --- Oh, this system has sssd-libwbclient installed, and it was using that. Removing it makes it use the real libwbclient which works. --- Additional comment from David Woodhouse on 2014-12-17 19:04:35 EST --- If you're going to install a higher-priority 'alternative' for Samba's libraries, please make sure they *work*.
Upstream ticket: https://fedorahosted.org/sssd/ticket/2537
This doesn't look like it fixes things. It stops wbinfo from *crashing*, sure. But it still doesn't *work*.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0441.html