Its been a very wierd day, so far, so bear with me. First of all, I was attempting to apply the fix for the buffer vuln in openssh by applying 3.7p1 (bug 28873 discusses that problem). After upgrading to new version (seems like its unrelated), ssh'ing to any host (including localhost) results in a Segmentation fault. I will attach the strace output shortly. Reverting back to the older net-misc/openssh-3.6.1_p2-r3 results in exactly the same behavior. So, something else is broken and not openssh itself. Secondly, incoming connections are totally buggered as well. Following appears in /var/log/sshd/current (I use metalog for my logging): Sep 16 14:43:13 [sshd] PAM unable to dlopen(/lib/security/pam_stack.so) Sep 16 14:43:13 [sshd] PAM [dlerror: /lib/security/pam_stack.so: undefined symbo l: _pam_make_env] Sep 16 14:43:13 [sshd] PAM adding faulty module: /lib/security/pam_stack.so Sep 16 14:43:13 [sshd] PAM unable to dlopen(/lib/security/pam_shells.so) Sep 16 14:43:13 [sshd] PAM [dlerror: /lib/security/pam_shells.so: undefined symb ol: pam_get_user] Sep 16 14:43:13 [sshd] PAM adding faulty module: /lib/security/pam_shells.so Sep 16 14:43:13 [sshd] PAM unable to dlopen(/lib/security/pam_nologin.so) Sep 16 14:43:13 [sshd] PAM [dlerror: /lib/security/pam_nologin.so: undefined sym bol: pam_get_item] Sep 16 14:43:13 [sshd] PAM adding faulty module: /lib/security/pam_nologin.so Sep 16 14:43:13 [sshd] error: PAM: Module is unknown So, now we've got pam into the mix as well. I have re-emerged by tuning down my CFLAGS optimizations to no avail. Any ideas?
Created attachment 17818 [details] emerge --info output
Created attachment 17819 [details] ssh strace output
Mine seg-faulted too. A co-worker of mine had no such trouble. Noting that he was using ICC rather than GCC, I tried re-emerging with ICC, and now 'ssh' no longer segfaults. I can't guarantee that's the cause-and-effect, of course, and I don't have time to investigate more closely at the moment, but there you have it. My first emerge was with gcc-3.3.1-r2. Zell
I'm seeing the same behaviour. In my desktop machine (gcc 3.3.1-r2) openssh segfaults, but in my server (gcc 3.2.3) it works fine.
My initial report was made with ACCEPT_KEYWORDS="~x86" (unstable). I am in the process of building stable versions of: sys-devel/binutils-2.14.90.0.6-r2 sys-devel/gcc-3.2.3-r1 Will let you know how I fare with the new gcc.
Just a FYI, this is a GCC 3.3.1-r2 issue got the same errors and going back to gcc-3.3.1 (had to download a binary package in order to go back). Please check out bug http://bugs.gentoo.org/show_bug.cgi?id=28875 You will likely need to rebuild all packages which were built with GCC 3.3.1-r2 check the forums or -dev mailing list for more information.
*** This bug has been marked as a duplicate of 28875 ***
