http://bugzilla.mindrot.org/show_bug.cgi?id=1105
markus at openbsd.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Privledge Separation |Privilege Separation
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugzilla.mindrot.org/show_bug.cgi?id=1105 ------- Comment #7 from djm at mindrot.org 2005-10-17 19:16 ------- You mention trying different "architectures", what do you mean? What OS/Distribution are you using? (beyond "Linux"...) This doesn't look like the rekey bug - it looks like the child session is terminating normally from the perspective of sshd. So it is probably blowing up inside session.c:do_child() Given the bleeding-edge nature of your system, it isn't likely that we are going to be able to replicate your configuration easily and it is probable that your problem lies in glibc or gcc. gcc-4.x has been known miscompile OpenSSH (e.g. Bug #1080), so you might want to try a 3.x version if you can. Apart from this, your best bet would be attaching gdb or instrumenting session.c:do_child() with fprintf(stderr, "%d", __LINE__); calls to see how far it gets. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.mindrot.org/show_bug.cgi?id=1105 ------- Comment #8 from dtucker at zip.com.au 2005-10-17 22:54 ------- Is it possible that your shell is simply exiting for some reason? Could you try another shell (eg sash since that would eliminate shared library problems too). Also worth a try: run sshd under "strace -f" (but be aware that that the output of strace may contain passwords.) ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.mindrot.org/show_bug.cgi?id=1105 ------- Comment #9 from giffordj at linkline.com 2005-10-18 01:06 ------- Created an attachment (id=1004) --> (http://bugzilla.mindrot.org/attachment.cgi?id=1004&action=view) SSH Strace ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.mindrot.org/show_bug.cgi?id=1105 ------- Comment #10 from giffordj at linkline.com 2005-10-18 01:07 ------- Attached strace of the issue. Password removed ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.mindrot.org/show_bug.cgi?id=1105 ------- Comment #11 from dtucker at zip.com.au 2005-10-18 09:46 ------- All of the interesting things happened in one of the child processes and you didn't use the strace "-f" option to follow it after a fork. You also haven't answered questions about which options you built and are running OpenSSH with, the exact nature of your system (it sounds like a self-built one?), what you meant by trying this on multiple "architectures", or whether or not the problem occurs with an alternate shell. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.mindrot.org/show_bug.cgi?id=1105
------- Comment #12 from giffordj at linkline.com 2005-10-18 10:50 -------
Self built system - same build method I've used for years.
./configure --prefix=/usr --sysconfdir=/etc/ssh \
--libexecdir=/usr/sbin --with-md5-passwords \
--with-privsep-path=/var/lib/sshd
make
make install
Will be updating strace in a few minutes.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugzilla.mindrot.org/show_bug.cgi?id=1105 ------- Comment #13 from giffordj at linkline.com 2005-10-18 10:51 ------- Created an attachment (id=1005) --> (http://bugzilla.mindrot.org/attachment.cgi?id=1005&action=view) Updated strace log ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.mindrot.org/show_bug.cgi?id=1105 ------- Comment #14 from giffordj at linkline.com 2005-10-18 10:52 ------- Will test with a different shell. Will report back. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.mindrot.org/show_bug.cgi?id=1105 ------- Comment #15 from giffordj at linkline.com 2005-10-27 05:01 ------- Same issue, tested with ash, zsh, and tcsh ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.mindrot.org/show_bug.cgi?id=1105 ------- Comment #16 from dtucker at zip.com.au 2005-10-27 18:42 ------- (From update of attachment 1005)>Process 11732 attached >child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xfffff80000c92d70) = 11732[...]>[pid 11725] rt_sigtimedwait([?], ptrace: umoven: Input/output error >0x3, 0, 6) = 0Not sure if this is related or not. [...]>[pid 11725] waitpid(-1, [{WIFSIGNALED(s) && WTERMSIG(s) == SIGSEGV}], WNOHANG) = 11732Note that the child pid (11732) does not show up in the strace at all. It seems like the fork() fails for some reason (process limits?). Since you're running a custom system we can't reproduce the problem, and since no one else has reported anything similar then I'm afraid you're on your own. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.mindrot.org/show_bug.cgi?id=1105 ------- Comment #17 from giffordj at linkline.com 2005-11-12 15:29 ------- Updated: The last glibc snapshot(1107) seems to have corrected the issue. It now works on the 3 different architectures I had problems with. Don't know which patch to glibc fixed it, but It works now. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.mindrot.org/show_bug.cgi?id=1105
dtucker at zip.com.au changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Comment #18 from dtucker at zip.com.au 2005-11-12 16:06 -------
OK, thanks. Closing.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.