|
Re: SSH transport [message #7633 is a reply to message #7612] |
Tue, 17 April 2007 13:28 |
Martin Oberhuber Messages: 1007 Registered: July 2009 |
Senior Member |
|
|
Hello,
the problem with ssh(ls)/scp is that it needs to be aware of the various
kinds of shells that a user can have installed on the remote side,
various output and date formats of ls and the like. I know that there
are tools like WinSCP around which do provide this, but if you look at
their configuration options you get a feeling of how many alternatives
need to be considered for a really stable solution.
sftp, on the other hand, is a standardized protocol following an RFC and
thus most easy to implement in a stable manner. That's why we chose sftp
at first.
But if somebody in the community (you?) wanted to contribute an RSE
ssh(ls)/scp provider under EPL, we'd happily accept it. The RSE
IFileService API is really simple to implement. You could take the
current ssh/sftp plugin as a blueprint and would not even have to do a
connectorservice.
You could start by making a bugzilla enhancement request, declare that
you wanted to work on it and then attach your code as a ZIP or patch on
bugzilla. The TM and RSE FAQ has some hints on how to get started with
programming in Eclipse. The people subscribed to the dsdp-tm-dev mailing
list will also be available to help if you have any questions.
The only word of caution I need to give, is that we cannot accept code
of unclear copyright or provenience. So you could not just take some
GPL'd scp client and contribute it. Your work would need to be original
work by yourself, contributed under the EPL or a compatible license.
Thanks,
--
Martin Oberhuber
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
Eclipse.org wrote:
> Hi all,
> current ssh transport (particulary for browsing/transferring stuff) is using
> sftp subsystem. Are there any opportunity to implement another approach
> using scp protocol for trunsferring data and "ls" command through ssh
> connection for browsing ? Not all ssh-enabled devices support sftp subsystem
> for security purposes, so probably ssh(ls)/scp pair looks more universal.
>
>
|
|
|
Re: SSH transport [message #566807 is a reply to message #7612] |
Tue, 17 April 2007 13:28 |
Martin Oberhuber Messages: 1007 Registered: July 2009 |
Senior Member |
|
|
Hello,
the problem with ssh(ls)/scp is that it needs to be aware of the various
kinds of shells that a user can have installed on the remote side,
various output and date formats of ls and the like. I know that there
are tools like WinSCP around which do provide this, but if you look at
their configuration options you get a feeling of how many alternatives
need to be considered for a really stable solution.
sftp, on the other hand, is a standardized protocol following an RFC and
thus most easy to implement in a stable manner. That's why we chose sftp
at first.
But if somebody in the community (you?) wanted to contribute an RSE
ssh(ls)/scp provider under EPL, we'd happily accept it. The RSE
IFileService API is really simple to implement. You could take the
current ssh/sftp plugin as a blueprint and would not even have to do a
connectorservice.
You could start by making a bugzilla enhancement request, declare that
you wanted to work on it and then attach your code as a ZIP or patch on
bugzilla. The TM and RSE FAQ has some hints on how to get started with
programming in Eclipse. The people subscribed to the dsdp-tm-dev mailing
list will also be available to help if you have any questions.
The only word of caution I need to give, is that we cannot accept code
of unclear copyright or provenience. So you could not just take some
GPL'd scp client and contribute it. Your work would need to be original
work by yourself, contributed under the EPL or a compatible license.
Thanks,
--
Martin Oberhuber
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
Eclipse.org wrote:
> Hi all,
> current ssh transport (particulary for browsing/transferring stuff) is using
> sftp subsystem. Are there any opportunity to implement another approach
> using scp protocol for trunsferring data and "ls" command through ssh
> connection for browsing ? Not all ssh-enabled devices support sftp subsystem
> for security purposes, so probably ssh(ls)/scp pair looks more universal.
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03040 seconds