Displaying 4 results from an estimated 4 matches for "ssh2_disconnect_by_application".
2013 Jan 04
16
[Bug 2057] New: ssh should treat "Received disconnect" messages as errors
https://bugzilla.mindrot.org/show_bug.cgi?id=2057
Bug ID: 2057
Summary: ssh should treat "Received disconnect" messages as
errors
Classification: Unclassified
Product: Portable OpenSSH
Version: -current
Hardware: All
OS: All
Status: NEW
Severity: minor
Priority:
2024 May 27
1
OpenSSH server doesn't log client disconnect without SSH_MSG_DISCONNECT
...-1269,6 +1269,10 @@
> * and indeed OpenSSH feels this is more polite than sending a
> * DISCONNECT. So now we don't.
> */
> +
> + /* We do again. */
> + ssh2_bpp_queue_disconnect(s->ppl.bpp, "disconnected by user",
> SSH2_DISCONNECT_BY_APPLICATION);
> +
> ssh_user_close(s->ppl.ssh, "All channels closed");
> return;
> }
Yeah, you're adding a new thing that will be logged. IMO you should
try to figure out why the "Connection closed" message that is present
in the debug log you sent...
2010 Mar 12
1
Is this a bug in 5.4p1?
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
2024 May 22
2
OpenSSH server doesn't log client disconnect without SSH_MSG_DISCONNECT
On Tue, 21 May 2024, Opty wrote:
> Hello,
>
> can anyone confirm that OpenSSH server doesn't log client disconnect
> without SSH_MSG_DISCONNECT?
OpenSSH logs the disconnection regardless of whether the client sends
SSH_MSG_DISCONNECT or just drops the connection.
A little more information may be logged from the disconnect packet
if it was sent, but there should always be a