[Bug 2758] Connection to xx.xx.xx.xx port 22: Broken pipe

2021-04-22 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=2758

Damien Miller  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

--- Comment #6 from Damien Miller  ---
closing resolved bugs as of 8.6p1 release

-- 
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 2758] Connection to xx.xx.xx.xx port 22: Broken pipe

2018-04-05 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=2758

Damien Miller  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #5 from Damien Miller  ---
Sorry, like I said - the message indicates the exact error case that
caused the connection to be dropped. It's useful information and worth
keeping.

-- 
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 2758] Connection to xx.xx.xx.xx port 22: Broken pipe

2018-01-07 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=2758

--- Comment #4 from j...@jguk.org ---
Why not put something user-friendly first then?

eg add "lost"

Connection lost to xx.xx.xx.xx port 22: Broken pipe

-- 
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 2758] Connection to xx.xx.xx.xx port 22: Broken pipe

2018-01-04 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=2758

Damien Miller  changed:

   What|Removed |Added

 CC||d...@mindrot.org

--- Comment #3 from Damien Miller  ---
The error indicates the exact condition that caused the connection to
drop using one of the system error messages (see "man errno"). To
change it to something different would be to lose information.

-- 
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 2758] Connection to xx.xx.xx.xx port 22: Broken pipe

2017-08-12 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=2758

--- Comment #2 from j...@jguk.org ---
Hello
Sorry I don't know the reason the connection had a pipe error.

Even "Connection lost" would sound good.


Although in English, "closed" doesn't mean deliberately closed.

-- 
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 2758] Connection to xx.xx.xx.xx port 22: Broken pipe

2017-08-12 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=2758

Darren Tucker  changed:

   What|Removed |Added

 CC||dtuc...@zip.com.au

--- Comment #1 from Darren Tucker  ---
(In reply to jg from comment #0)
[...]
> packet_write_wait: Connection to xx.xx.xx.xx port 22: Broken pipe
> $
> 
> Could that just say "Connection closed" please ? eg.

Is that being triggered by a TCP reset?  If so the message seems
appropriate.

"Connection closed" means it was deliberately closed be either client
or server (ie TCP FIN).  Using it when something else breaks the
connection seems like a lie.

-- 
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