On Fri, Mar 29, 2019 at 10:31 PM Damien Miller <djm@xxxxxxxxxxx> wrote: > Thanks for testing - are you able to see if there's anything in > the server logs? I looked in /var/log/secure or /var/log/messages and just saw the 2 lines below: Mar 29 20:57:17 ip-10-12-0-116 sshd[14315]: Accepted publickey for ec2-user from xxx ssh2: RSA-CERT ID xxx (for xxx) (serial xxx) CA RSA SHA256:QtxnpSvhjow+Z68+z5VMnNGitHHc+nkoDMiJM0C+JtM Mar 29 20:57:17 ip-10-12-0-116 sshd[14315]: pam_unix(sshd:session): session opened for user ec2-user by (uid=0) > I've just committed some extra verbosity in the client's log messages that > might clarify where it is exiting (patch attached). For some reason I couldn't get the patch to apply cleanly over the snapshot, so manually applied the lines and ended up with the following output: (skipped all the pre-authentication logging) debug1: Authentication succeeded (publickey). Authenticated to xxx debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug3: send packet: type 90 debug1: Requesting no-more-sessions@xxxxxxxxxxx debug3: send packet: type 80 debug1: Entering interactive session. debug1: pledge: network debug3: receive packet: type 80 debug1: client_input_global_request: rtype hostkeys-00@xxxxxxxxxxx want_reply 0 debug3: receive packet: type 91 debug2: channel_input_open_confirmation: channel 0: callback start debug2: fd 3 setting TCP_NODELAY debug3: ssh_packet_set_tos: set IP_TOS 0x48 debug2: client_session2_setup: id 0 debug2: channel 0: request pty-req confirm 1 debug3: send packet: type 98 debug2: channel 0: request shell confirm 1 debug3: send packet: type 98 debug2: channel_input_open_confirmation: channel 0: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug3: send packet: type 1 client_loop: send disconnect: Broken pipe _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
