Project

General

Profile

Bug #34894

Be more explicit about SSH connection handling

Added by Adam Ruzicka about 2 months ago. Updated 17 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Smart Proxy - SSH
Difficulty:
Triaged:
No
Bugzilla link:

Description

Currently we use the same set of ssh options no matter if the connection is already established or not. This can lead to ambiguities where we cannot reliably tell what's going on.

Associated revisions

Revision 2d2549c7 (diff)
Added by Adam Růžička 17 days ago

Be more explicit about dealing with connections (#82)

  • Fixes #34894 - Be more explicit about SSH connection handling

This allows us to:
- try using both password and key passphrase
- have clearer idea what's going on
- have better logging
- decouple connection handling logic from what we want to run on the
remote end

  • Refs #34894 - Fix effective user preflight check
  • Refs #34894 - Be more strict about password prompts
  • Refs #34894 - Fix polling runner
  • Refs #34894 - Fix async ssh mode name
  • Refs #34894 - Prefer last successful auth method when reestablishing connection

Logger gets set between runner's #initialize and #start.

History

#1 Updated by The Foreman Bot about 2 months ago

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

#2 Updated by The Foreman Bot 17 days ago

  • Fixed in Releases smart_proxy_remote_execution_ssh-0.7.1 added

#3 Updated by Anonymous 17 days ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF