Bug 331217 - [scp] When creating an "SSH Only" connection, scp should not be selected by default
Summary: [scp] When creating an "SSH Only" connection, scp should not be selected by d...
Status: RESOLVED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.3 M4   Edit
Assignee: Anna Dushistova CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords: helpwanted
Depends on: 213438
Blocks:
  Show dependency tree
 
Reported: 2010-11-26 10:32 EST by Martin Oberhuber CLA
Modified: 2010-12-14 07:23 EST (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2010-11-26 10:32:26 EST 
With the new SCP plugin installed, when I create an "SSH Only" connection the scp file subsystem is selected by default.

This might be a problem when scp gets mature and integrated into RSE-runtime. Since many existing users of RSE will be used to creating "SSH Only" connections, but for a fact (and because of the conceptual transfer method), the SFTP connection is more reliable than SCP.

We need to find a way of integrating scp with the standard RSE-runtime while making sure that we don't break existing adopters. Following ideas might work:

(a) just change order of subsystems in the wizard, giving scp lower priority
(b) invent a fallback where sftp is tried first, with a fallback to scp when it
    fails
(c) Don't register scp into the "SSH Only" system type by default, but provide
    a separate and different system type
Comment 1 Anna Dushistova CLA 2010-11-30 11:29:43 EST 
Martin, I changed the priority to 120, and it's now not selected by default.
Let me know if you want it to be fixed differently.