Project

General

Profile

Actions

Bug #26958

closed

ssh/session: webrick tries to use closed socket after hijacking

Added by Marius Vollmer over 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Found in Releases:

Description

Webrick does not fully support socket hijacking, so we pry the socket from its hands with some trickery. However, once the session is done, webrick will try to use the hijacked socket, which is now closed. This results in errors, which are logged and then ignored.

We should prevent these errors from happening, if just to keep them out of the log. They don't seem to cause any harm, but the log should be kept clean from noise.

Actions #1

Updated by The Foreman Bot over 5 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/41 added
Actions #2

Updated by Anonymous over 5 years ago

  • Status changed from Ready For Testing to Closed
Actions #3

Updated by Adam Ruzicka almost 5 years ago

  • Fixed in Releases smart_proxy_remote_execution_ssh-0.3.0 added
Actions

Also available in: Atom PDF