Version-Release number of selected component: openssh-server-5.9p1-26.fc17 Additional info: backtrace_rating: 4 cmdline: 'sshd: unknown [priv]' crash_function: __asprintf_chk executable: /usr/sbin/sshd kernel: 3.6.8-2.fc17.x86_64 uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #2 __asprintf_chk at asprintf_chk.c:33 #3 asprintf at /usr/include/bits/stdio2.h:158 #4 file_exists_dotecryptfs at pam_ecryptfs.c:76 #5 pam_sm_authenticate at pam_ecryptfs.c:147 #6 _pam_dispatch_aux at pam_dispatch.c:110 #7 _pam_dispatch at pam_dispatch.c:407 #8 pam_authenticate at pam_auth.c:34 #9 sshpam_auth_passwd at auth-pam.c:1213 #10 auth_password at auth-passwd.c:116 #11 mm_answer_authpassword at monitor.c:933
Created attachment 713963 [details] File: backtrace
Created attachment 713964 [details] File: cgroup
Created attachment 713965 [details] File: core_backtrace
Created attachment 713966 [details] File: dso_list
Created attachment 713967 [details] File: environ
Created attachment 713968 [details] File: limits
Created attachment 713969 [details] File: maps
Created attachment 713971 [details] File: open_fds
Created attachment 713972 [details] File: proc_pid_status
Created attachment 713973 [details] File: smolt_data
Created attachment 713974 [details] File: var_log_messages
Thanks for reporting this. Do you know how to reproduce this crash?
(In reply to comment #12) > Thanks for reporting this. > Do you know how to reproduce this crash? I've since upgraded to openssh-5.9p1-29.fc17.x86_64 and the crashed happened again today. Unfortunately, I don't know what is the culprit that triggers this. Maybe it is related, maybe not, but both times it happened, I was using eduroam WiFi with a public IP address, whereas usually I'm behind some NAT (at work or at home). And today I had a Denyhosts report at about the same time as the crash report.
This should not be related. Could you attach /var/log/messages and /var/log/secure from time of the crash? Check if the logs (especially the second one) does not contain password in plaintext and if it does, replace it with *** thanks
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.