search for: ssh_msg_disconnect

...ns to the client why the socket was closed? >From draft-ietf-secsh-transport-24.txt, chapter 11: ---------------------------------------------------------- 11. Additional Messages Either party may send any of the following messages at any time. 11.1 Disconnection Message byte SSH_MSG_DISCONNECT uint32 reason code string description [RFC3629] string language tag [RFC3066] This message causes immediate termination of the connection. All implementations MUST be able to process this message; they SHOULD be able to send this message. The sender MUST NO...

...server and the server respond with SSH_CMSG_EXITSTATUS and finally close the connection when the client sends SSH_CMSG_EXIT_CONFIRMATION. This will effectively end the server_loop in the server. This would close the connection in a cleaner way. Although the RFC has stated that either side may send SSH_MSG_DISCONNECT, for immediate disconnect, I am surprised that this is the normal exit method used in putty implementation. I fear that any addition of code after server_loop, to be done once the connection is closed by the server might not get called, as it now is redirected to fatal_cleanup(). Is t...

I am testing with a 5.4p1 client and have noticed, on the server side, that sometimes an SSH_MSG_DISCONNECT message is received with the following 28-byte long payload: 0x00 0x00 0x00 0x0b Reason: SSH_DISCONNECT_BY_APPLICATION 0x00 0x00 0x00 0x14 Description string length: 20 bytes 0x64 0x69 0x73 0x63 0x6f 0x6e 0x6e 0x65 Descrip...

http://bugzilla.mindrot.org/show_bug.cgi?id=1307 Summary: client disconnects if ServerAlive enabled but not implemented Product: Portable OpenSSH Version: 4.3p2 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: bitbucket at

.... What do I do? - SSH2_MSG_CHANNEL_CLOSE results in a long polling loop where sshd keeps trying to garbage collect the channel, but can't because the process is still alive. Furthermore, this appears to be stalling the other commands as well. (More experimentation is needed on this point.) - SSH_MSG_DISCONNECT tears down the whole session, killing *all* the commands. I could do this, but now I have to restart all the other commands that get trashed. - I could try a SSH_MSG_CHANNEL_REQUEST "signal" and send SIGINT, SIGTERM, SIGABRT, etc, but I don't see a handler for "signal" in t...

...tch if key is _used_ warn about keysize-mismatch with log() not error() channels.c readconf.c readconf.h ssh.c ssh.h sshconnect.c ports are u_short - [hostfile.c] indent, shorter warning - [nchan.c] use error() for internal errors - [packet.c] set loglevel for SSH_MSG_DISCONNECT to log(), not fatal() serverloop.c indent - [ssh-add.1 ssh-add.c ssh.h] document $SSH_ASKPASS, reasonable default - [ssh.1] CheckHostIP is not available for connects via proxy command - [sshconnect.c] typo easier to read client code for passwd and skey auth...

...at mindrot.org Reporter: imorgan at nas.nasa.gov Created attachment 2204 --> https://bugzilla.mindrot.org/attachment.cgi?id=2204&action=edit Use error() to report "Received disconnect" messages to the user In packet.c, logit() is used to report SSH2_MSG_DISCONNECT and SSH_MSG_DISCONNECT messages to the user. This means that if the user has LogLevel set to "error," such messages will be suppressed. Since the circumstances which trigger packet_disconnect() to be called are really error conditions, it seems more appropriate to use error(). One scenario where this occurs is...

Dear all, For my thesis, I've been working on automatic inference of state machines for SSH servers. I ran into a couple of particularities regarding OpenSSH's inferred state machine, and was hoping some of you might be interested. Maybe you can even shed some light on it. Setup: I'm using LearnLib's (Java) version of the L* learning algorithm [1] to come up with sequences of