Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » DSDP - Target Management » SSHing from a remote connection
SSHing from a remote connection [message #32029] Tue, 17 February 2009 11:05 Go to next message
Tim Hassall is currently offline Tim Hassall
Messages: 2
Registered: July 2009
Junior Member
Hi,

In my work we log into a unix box for authentication, from which we can
then ssh into our production boxes - they are not accessible with our
standard credentials. Is there a way currently that RSE can be used so
that we establish a connection to the authentication box, then ssh to a
production box and still get the benefits of RSE (Tree file structure,
file editing etc.) for the subsequent boxes? If not, a nudge in the right
direction code wise would not go unwelcomed :-)

Thanks,
Tim
Re: SSHing from a remote connection [message #32064 is a reply to message #32029] Tue, 17 February 2009 11:52 Go to previous messageGo to next message
Steve Blass is currently offline Steve Blass
Messages: 276
Registered: July 2009
Senior Member
Tim Hassall wrote:
> Hi,
>
> In my work we log into a unix box for authentication, from which we can
> then ssh into our production boxes - they are not accessible with our
> standard credentials. Is there a way currently that RSE can be used so
> that we establish a connection to the authentication box, then ssh to a
> production box and still get the benefits of RSE (Tree file structure,
> file editing etc.) for the subsequent boxes? If not, a nudge in the
> right direction code wise would not go unwelcomed :-)
>
> Thanks,
> Tim
>

You could build a tunnel to the production box on a non-standard local
port and aim RSE at that. A command line ssh example tunneling from
port 8701 on the localhost through the authentication box to the
production box would look like

$ ssh -l authbox_username -L8701:productionbox:22 authenticationbox

Now set up an RSE SSH connection for localhost and adjust the port by
right-clicking the localhost SFTP files item in the tree, selecting
properties and entering 8701 in the port number. Now you can connect
all the way through. When RSE asks you to login use the productionbox
credentials.

HTH,

Steve
Re: SSHing from a remote connection [message #32240 is a reply to message #32064] Mon, 23 February 2009 09:06 Go to previous message
Martin Oberhuber is currently offline Martin Oberhuber
Messages: 983
Registered: July 2009
Senior Member
Thanks Steve,

the tunneling trick should indeed fix the issue. I'd also like to add
that since RSE 3.1M5, there is better support for the files cache in
case multiple tunnels are used on localhost with different ports:

http://download.eclipse.org/dsdp/tm/downloads/drops/S-3.1M5- 200902081925/buildNotes.php
https://bugs.eclipse.org/bugs/show_bug.cgi?id=245260

Some similar command for setting up an SSH tunnel are also near the end
of the dstore userdocs for setting up a server:

http://dsdp.eclipse.org/help/latest/topic/org.eclipse.rse.do c.user/tasks/tbeginlinux.html

Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm




Steve Blass wrote:
> Tim Hassall wrote:
>> Hi,
>>
>> In my work we log into a unix box for authentication, from which we
>> can then ssh into our production boxes - they are not accessible with
>> our standard credentials. Is there a way currently that RSE can be
>> used so that we establish a connection to the authentication box, then
>> ssh to a production box and still get the benefits of RSE (Tree file
>> structure, file editing etc.) for the subsequent boxes? If not, a
>> nudge in the right direction code wise would not go unwelcomed :-)
>>
>> Thanks,
>> Tim
>>
>
> You could build a tunnel to the production box on a non-standard local
> port and aim RSE at that. A command line ssh example tunneling from
> port 8701 on the localhost through the authentication box to the
> production box would look like
>
> $ ssh -l authbox_username -L8701:productionbox:22 authenticationbox
>
> Now set up an RSE SSH connection for localhost and adjust the port by
> right-clicking the localhost SFTP files item in the tree, selecting
> properties and entering 8701 in the port number. Now you can connect
> all the way through. When RSE asks you to login use the productionbox
> credentials.
>
> HTH,
>
> Steve
>
>
>
Re: SSHing from a remote connection [message #579134 is a reply to message #32029] Tue, 17 February 2009 11:52 Go to previous message
Steve Blass is currently offline Steve Blass
Messages: 276
Registered: July 2009
Senior Member
Tim Hassall wrote:
> Hi,
>
> In my work we log into a unix box for authentication, from which we can
> then ssh into our production boxes - they are not accessible with our
> standard credentials. Is there a way currently that RSE can be used so
> that we establish a connection to the authentication box, then ssh to a
> production box and still get the benefits of RSE (Tree file structure,
> file editing etc.) for the subsequent boxes? If not, a nudge in the
> right direction code wise would not go unwelcomed :-)
>
> Thanks,
> Tim
>

You could build a tunnel to the production box on a non-standard local
port and aim RSE at that. A command line ssh example tunneling from
port 8701 on the localhost through the authentication box to the
production box would look like

$ ssh -l authbox_username -L8701:productionbox:22 authenticationbox

Now set up an RSE SSH connection for localhost and adjust the port by
right-clicking the localhost SFTP files item in the tree, selecting
properties and entering 8701 in the port number. Now you can connect
all the way through. When RSE asks you to login use the productionbox
credentials.

HTH,

Steve
Re: SSHing from a remote connection [message #579207 is a reply to message #32064] Mon, 23 February 2009 09:06 Go to previous message
Martin Oberhuber is currently offline Martin Oberhuber
Messages: 983
Registered: July 2009
Senior Member
Thanks Steve,

the tunneling trick should indeed fix the issue. I'd also like to add
that since RSE 3.1M5, there is better support for the files cache in
case multiple tunnels are used on localhost with different ports:

http://download.eclipse.org/dsdp/tm/downloads/drops/S-3.1M5- 200902081925/buildNotes.php
https://bugs.eclipse.org/bugs/show_bug.cgi?id=245260

Some similar command for setting up an SSH tunnel are also near the end
of the dstore userdocs for setting up a server:

http://dsdp.eclipse.org/help/latest/topic/org.eclipse.rse.do c.user/tasks/tbeginlinux.html

Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm




Steve Blass wrote:
> Tim Hassall wrote:
>> Hi,
>>
>> In my work we log into a unix box for authentication, from which we
>> can then ssh into our production boxes - they are not accessible with
>> our standard credentials. Is there a way currently that RSE can be
>> used so that we establish a connection to the authentication box, then
>> ssh to a production box and still get the benefits of RSE (Tree file
>> structure, file editing etc.) for the subsequent boxes? If not, a
>> nudge in the right direction code wise would not go unwelcomed :-)
>>
>> Thanks,
>> Tim
>>
>
> You could build a tunnel to the production box on a non-standard local
> port and aim RSE at that. A command line ssh example tunneling from
> port 8701 on the localhost through the authentication box to the
> production box would look like
>
> $ ssh -l authbox_username -L8701:productionbox:22 authenticationbox
>
> Now set up an RSE SSH connection for localhost and adjust the port by
> right-clicking the localhost SFTP files item in the tree, selecting
> properties and entering 8701 in the port number. Now you can connect
> all the way through. When RSE asks you to login use the productionbox
> credentials.
>
> HTH,
>
> Steve
>
>
>
Previous Topic:how to correctly init RSE
Next Topic:Working with Synchronize as part of Export
Goto Forum:
  


Current Time: Fri Aug 29 04:11:10 EDT 2014

Powered by FUDForum. Page generated in 0.02010 seconds