[Bug 1213] ssh-keyscan exits in mid-way
https://bugzilla.mindrot.org/show_bug.cgi?id=1213 Damien Miller d...@mindrot.org changed: What|Removed |Added Blocks||2266 -- You are receiving this mail because: You are watching someone on the CC list of the bug. You are watching the assignee of the bug. ___ openssh-bugs mailing list openssh-bugs@mindrot.org https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 2266] Bugs intended to be fixed in 6.8
https://bugzilla.mindrot.org/show_bug.cgi?id=2266 Damien Miller d...@mindrot.org changed: What|Removed |Added Depends on||1213 -- You are receiving this mail because: You are watching the assignee of the bug. You are watching the reporter of the bug. ___ openssh-bugs mailing list openssh-bugs@mindrot.org https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 1213] ssh-keyscan exits in mid-way
https://bugzilla.mindrot.org/show_bug.cgi?id=1213 Damien Miller d...@mindrot.org changed: What|Removed |Added Attachment #2197|0 |1 is obsolete|| Assignee|unassigned-b...@mindrot.org |d...@mindrot.org Status|NEW |ASSIGNED --- Comment #49 from Damien Miller d...@mindrot.org --- Created attachment 2533 -- https://bugzilla.mindrot.org/attachment.cgi?id=2533action=edit Don't fatal on getaddrinfo failures This looks simple to fix. -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug. ___ openssh-bugs mailing list openssh-bugs@mindrot.org https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 2340] Openssh issue: unable to ssh the solaris server from ldap users
https://bugzilla.mindrot.org/show_bug.cgi?id=2340 --- Comment #9 from Moin sultankha...@gmail.com --- Created attachment 2534 -- https://bugzilla.mindrot.org/attachment.cgi?id=2534action=edit sshd terminal logs Hi, = /path/to/sshd -p [someport] -De -oLogLevel=debug3 /dev/null /dev/null logfile ssh -vvv -o preferredauthentications=keyboard-interactive -p [someport] yourserver = I could login successfully but nothing was written in logfile, but have attached the terminal logs. -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug. ___ openssh-bugs mailing list openssh-bugs@mindrot.org https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 2340] Openssh issue: unable to ssh the solaris server from ldap users
https://bugzilla.mindrot.org/show_bug.cgi?id=2340 --- Comment #10 from Darren Tucker dtuc...@zip.com.au --- oops, missed the 2 to redirect stderr. That should have read: /path/to/sshd -p [someport] -De -oLogLevel=debug3 /dev/null /dev/null 2logfile however what you've posted indicates it worked, so I don't think it's going to be helpful either. The only other difference I can think of is the controlling terminal. You could test this by running sshd under something like setsid (assuming Solaris has it): setsid /usr/sbin/sshd -p [someport] -De -oLogLevel=debug3 /dev/null /dev/null 2logfile If that doesn't work, try setting loglevel=debug3 in sshd_config, restarting and then grepping the log messages out of syslog by process ID (but note that there will be at least 3 pids, so you'll need to get them all). -- You are receiving this mail because: You are watching someone on the CC list of the bug. You are watching the assignee of the bug. ___ openssh-bugs mailing list openssh-bugs@mindrot.org https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 2062] Add support for a ForceShell sshd option
https://bugzilla.mindrot.org/show_bug.cgi?id=2062 Iain Morgan imor...@nas.nasa.gov changed: What|Removed |Added Attachment #2207|0 |1 is obsolete|| --- Comment #1 from Iain Morgan imor...@nas.nasa.gov --- Created attachment 2535 -- https://bugzilla.mindrot.org/attachment.cgi?id=2535action=edit Updated patch -- You are receiving this mail because: You are watching the assignee of the bug. ___ openssh-bugs mailing list openssh-bugs@mindrot.org https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 2340] Openssh issue: unable to ssh the solaris server from ldap users
https://bugzilla.mindrot.org/show_bug.cgi?id=2340 --- Comment #8 from Darren Tucker dtuc...@zip.com.au --- Short answer as a workaround: put ChallengeResponseAuthentication no and KbdInteractiveAuthentication no into sshd_config and restart sshd. Longer answer: There's two different methods of password-type authentication: PasswordAuthentication (the simplest) and keyboard-interactive (which is more complicated but more capable). Your debug logs show password works but keyboard-interactive doesn't. 3.if you can run the server in debug mode at the same time --- was able to login now this is a bit odd: your keyboard-interactive works when the server is running in debug mode. Unfortunately this makes it hard to figure out what's going on. My guess is that something in the PAM stack is trying to use stdin or stdout (which, if true, is a bug in a PAM module). Please try redirecting the sshd stdin and stdout then try logging in: /path/to/sshd -p [someport] -De -oLogLevel=debug3 /dev/null /dev/null logfile ssh -vvv -o preferredauthentications=keyboard-interactive -p [someport] yourserver and attach both logs to this bug. -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug. ___ openssh-bugs mailing list openssh-bugs@mindrot.org https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 1213] ssh-keyscan exits in mid-way
https://bugzilla.mindrot.org/show_bug.cgi?id=1213 --- Comment #50 from Daniel Richard G. sk...@iskunk.org --- Okay, tried again with your patch. Here's what I see: [...] # A.B.C.46 SSH-1.99-OpenSSH_4.2 # A.B.C.47 SSH-1.99-OpenSSH_4.2 # A.B.C.47 SSH-1.99-OpenSSH_4.2 # A.B.C.47 SSH-1.99-OpenSSH_4.2 # A.B.C.48 SSH-1.99-OpenSSH_4.2 # A.B.C.48 SSH-1.99-OpenSSH_4.2 # A.B.C.48 SSH-1.99-OpenSSH_4.2 A.B.D.162: Connection closed by remote host # A.B.D.26 SSH-2.0-OpenSSH_5.8p2_hpn13v11 FreeBSD-20110503 Connection closed by A.B.D.26 (exit status 255) I ran this at two different times of day, and got the same host in that last Connection closed error. As the error is non-specific, here's the backtrace: #0 0x76802d50 in _exit () from /lib64/libc.so.6 #1 0x77fc2048 in cleanup_exit (i=255) at ../cleanup.c:31 #2 0x77f9fa99 in ssh_packet_read_seqnr (ssh=0x786f4520, typep=0x7fffde0f , seqnr_p=0x7fffde10) at ../packet.c:1330 #3 0x77fa69f5 in ssh_dispatch_run (ssh=0x786f4520, mode=0, done=0x78207178, ctxt=0x786f4520) at ../dispatch.c:101 #4 0x77f85aef in keygrab_ssh2 (c=0x78207160) at ../ssh-keyscan.c:292 #5 0x77f86e99 in congreet (s=149) at ../ssh-keyscan.c:501 #6 0x77f86f34 in conread (s=149) at ../ssh-keyscan.c:516 #7 0x77f873b5 in conloop () at ../ssh-keyscan.c:587 #8 0x77f874cf in do_host ( host=0x7fffe27b foobaz.internal.example.com,X.Y.Z.W) at ../ssh-keyscan.c:613 #9 0x77f87d44 in main (argc=6, argv=0x7fffe778) at ../ssh-keyscan.c:779 This is the 20150127 snapshot, still. There seem to be a number of places in ssh_packet_read_seqnr() where connection errors lead straight to an exit... -- You are receiving this mail because: You are watching someone on the CC list of the bug. You are watching the assignee of the bug. ___ openssh-bugs mailing list openssh-bugs@mindrot.org https://lists.mindrot.org/mailman/listinfo/openssh-bugs
