(user deleted)
create SSH tunnel after session is established
Checking in to see if there's an update, or anything I can help with (further explanation, etc).
utilizing $HOST$ variable in a port forward entry appends a ":" to the end of the host string
I will test and get back to you. Additionally I believe the issue may stem from my error (but could be a bug as well).
Under the SSH Settings (second tab when creating a SSH Port Forward Entry), I was using $HOST$:$PORT$ since the end goal was to have a template. The reason for this is that our access port for the ssh service can vary from system to system and I did not see a way to define just the port as a variable for the entries.
I have since removed the port variable and simply used $HOST$, which seems to be more consistent and is giving me the expected results.
utilizing $HOST$ variable in a port forward entry appends a ":" to the end of the host string
It does work as a stand alone entry.
I am attempting to utilize this as a sub connection, or even a template.
utilizing $HOST$ variable in a port forward entry appends a ":" to the end of the host string
I am attempting to create a port forward entry using the $HOST$ variable, however it appends a ":" to the end of the host entry, this effectively attempts to use this string (xxx.xxx.xxx.xxx::80) to open a port forward which fails.
Output from tunnel session:
[8/2/2017 10:03:46 AM] Looking up host "10.240.1.19"
[8/2/2017 10:03:46 AM] Connecting to 10.240.1.19 port 22
[8/2/2017 10:03:46 AM] We claim version: SSH-2.0-PuTTY_Release_0.67
[8/2/2017 10:03:46 AM] Server version: SSH-2.0-OpenSSH_4.3
[8/2/2017 10:03:46 AM] We believe remote version has SSH-2 channel request bug
[8/2/2017 10:03:46 AM] Using SSH protocol version 2
[8/2/2017 10:03:46 AM] Doing Diffie-Hellman group exchange
[8/2/2017 10:03:46 AM] Doing Diffie-Hellman key exchange with hash SHA-1
<APPENDED ENTRY>
[8/2/2017 10:03:46 AM] Access granted
[8/2/2017 10:03:46 AM] Opening session as main channel
[8/2/2017 10:03:46 AM] Opened main channel
[8/2/2017 10:03:46 AM] Service lookup failed for destination port ":80"
[8/2/2017 10:03:46 AM] Allocated pty (ospeed 38400bps, ispeed 38400bps)
[8/2/2017 10:03:46 AM] Started a shell/command
to reproduce, create a port forward entry as a sub connection:
source = 127.0.0.1
Source Port = 80
Destination = $HOST$
Destination Port = 80
Mode = Local
I have attempted similar with Dynamic Mode, however that fails as well, but I believe that is a seperate issue.
Manually inputting the host works without issue.
create SSH tunnel after session is established
Just checking in to see if this has been reviewed/roadmapped etc, or if there's anything else I can provide to help out.
create SSH tunnel after session is established
Correct, in the Change settings menu after a connection has been made. I will have to check with regards to the account existing or not, but I do not think so.
Example Scenario:
We connect to a linux server on a remote site with a public IP via ssh on port 22, there is an additional web server on the same lan that does not have a public interface, I need to see the web page being presented by that internal server. I can create a tunnel from my existing ssh session to port 80 on that internal server's ip and view the web page using 127.0.0.1 in my browser remotely, no real login required on the 'internal/tunneled to' server to view the page.
(forgive me that's the simplest way I could explain it)
create SSH tunnel after session is established
I'm able to create a seperate tunnel entry without issue.
What i'm requesting, is to be able to add a tunnel while the session is already established without creating a separate entry. The tunnel can exit with the existing session, it doesn't have to be retained after.
create SSH tunnel after session is established
Is there currently a method of creating a tunnel in the rebex session after a connection has been made? Similar to how Putty allows this? I realize I can create templates, however the ports and ip's we're tunneling to from an existing session may change at any time, additionally our standard users who will need to do the tunneling will not have administrative access to modify sessions or create templates, so the idea of a template not ideal.
Screenshot of the specific settings are attached. I have searched and tested multiple methods, and cannot find a way around us having this functionality.
Preferably in a context menu, that we can change post connecting to the session.
Native SFTP client as a tool instead of individual entry
Great, thank you
Native SFTP client as a tool instead of individual entry
Additional Update:
It seems to be working after the following:
I had to set the priority of the Macro Templates higher than the original ssh entry.
Once I set the priority of the 'tools' higher than the original entry AND have multiple connections hard set to true (was default) then i'm able to use the tools as we intended.
Native SFTP client as a tool instead of individual entry
Modified existing session + all templates used by macro-tools.
Here are my results.
In the main entry (ssh) and all templates I have 'Allow open multiple connections' set to 'True'
If I open the session using a macro template then open the mail ssh session it works correctly.
If I do the reverse, opening the main ssh session, then attempt to open an additional session with the macro templates it simply jumps back to the original session without opening an additional tab or external window.
I will monitor the other thread.
Thank you for the input.
Native SFTP client as a tool instead of individual entry
I wanted to revisit this. As it only partially fills the need we have.
Example Scenario: we have an entry defined as an ssh session, we have that session open already. If I want to open the native sftp client as a template for this session, I have to exit the existing session first. What I would like for the tool to do is open an additional session using the template while the original ssh session is still open.
Essentially I could open up the same session using multiple templates at the same time. I believe it was working that way up-until the latest build. 11.5.0.0.
I've gone back through configurations on each of the templates as well as the macro's and I do not see any flags/switches I can add to open an additional session.
Native SFTP client as a tool instead of individual entry
That is exactly what I was looking for.
Thank you.
Native SFTP client as a tool instead of individual entry
I would like to see the native SFTP client be usable as a Macro/Tool instead of a pre-defined entry.
For example: Currently, in order to utilize the SFTP connection I would have to define an entry for each of my 700+ servers.
Instead I would like to right click on an existing ssh entry, select 'tools' and have an option to open winscp using the saved address and credentials (or ssh key) in the ssh entry.
Is this currently possible? I have only found a way to pre-define the entry in the same group so far.
Linux Port of Remote Desktop Manager
This seems to be an old thread, but its exactly the question i'd like to ask. Are there any updated plans for a linux client release?
Padding is Invalid Error
Latest Beta 11.1.2.0 seems to resolve.
Padding is Invalid Error
After updating our server to DVLS 3.1; when using the 11.1 client I am receiving the following error:
CryptographicException - Padding is invalid and cannot be removed.
at System.Security.Cryptography.RijndaelManagedTransform.DecryptData(Byte[] inputBuffer, Int32 inputOffset, Int32 inputCount, Byte[]& outputBuffer, Int32 outputOffset, PaddingMode paddingMode, Boolean fLast)
at System.Security.Cryptography.RijndaelManagedTransform.TransformFinalBlock(Byte[] inputBuffer, Int32 inputOffset, Int32 inputCount)
at System.Security.Cryptography.CryptoStream.FlushFinalBlock()
at System.Security.Cryptography.CryptoStream.Dispose(Boolean disposing)
at System.IO.Stream.Close()
at System.IO.Stream.Dispose()
at A.caffdb7cd64b8f25021522cf428831983.cbe3acd6492484a5bc671e384b09ae0f8(String c976455d4fb74ab6075c2618c33425db6, String c30234935d04135eee043de8bc49f7858, String cc775c49dcea664820c922a35fdf0bfb6)
at Devolutions.RemoteDesktopManager.Business.DataSources.PersonalXmlConnectionDataSource.LoadData()
at Devolutions.RemoteDesktopManager.Business.DataSources.PersonalXmlConnectionDataSource.GetConnections()
at A.c7e2cef3f825a7ec6ad4bada24eb65d62.caf5606902cd4b8fa72d75fe22722f906()
at A.c7e2cef3f825a7ec6ad4bada24eb65d62.get_c96fb366f86ad2bded84356bc5f76bce6()
at A.c7e2cef3f825a7ec6ad4bada24eb65d62.get_cd51ecb38581233121f4ec2311e63e3a9()
at Devolutions.RemoteDesktopManager.Forms.FrmConnectionGroup.LoadConnectionInControls(Connection connectionToLoad)
at Devolutions.RemoteDesktopManager.Forms.FrmConnectionGroup.cd010602130da8ffa095e72f712cf3d19(Object c19f185fd70cefc696ba148af1c4faf54, EventArgs cf1018bb83ec7debd818319fd3cb4844e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at Devolutions.RemoteDesktopManager.Forms.FrmBase.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Currently I am installing beta 11.1.2.0 to test and verify.
I see another user reported the same/similar issue, so I created this one for visibility. Please feel free to combine or move them if necessary.
I will update again post installation of 11.1.2.0 client.
SSH Port Forward entry not referencing Key stored in repository
Updated to V 11.1.0.0; issue with regards to key is no longer present.
SSH Port Forward entry not referencing Key stored in repository
I've tried both 32 bit and 64bit.
========================================
In putty, once the session is established, I right click on the title bar go to 'change settings', then Connection --> SSH --> Tunnels. At that point I can create or remove any tunnel, or port forwarding on demand.
I've attached a screen shot.
I would prefer to utilize the built in client instead of putty outside of RDM.
SSH Port Forward entry not referencing Key stored in repository
Same results either way. Even created an entirely new key, and pasted the data into the specific entry itself (after adding public to server).
Let me ask this. Is there currently any way to port forward 'on the fly' using the built in rebex shell?
For example, using PuTTY after an ssh session is established I can change settings and port forward at anytime during the session.
That functionality would actually eliminate my specific need for the separate port forward session. I can re-post, or move this question to the feature request section if need be.
Otherwise, let me know if you need anything else in regards to the keys.
SSH Port Forward entry not referencing Key stored in repository
Actually, it was generated using the tool embedded in RDM. I'll see if I can convert it to ppk.
SSH Port Forward entry not referencing Key stored in repository
After pasting the contents it still failed. Looks like it timed out. Attached screen shot of error. Is there additional logging I can turn on, and or gather for you?
SSH Port Forward entry not referencing Key stored in repository
That is interesting, it seems to be referencing a path that doesn't exist on my system.
The "I:" drive its looking for doesn't exist.
Here is the output if it will help.
========================================
[1/19/2016 1:50:14 PM] Looking up host "<removed>"
[1/19/2016 1:50:14 PM] Connecting to <removed> port 22
[1/19/2016 1:50:14 PM] We claim version: SSH-2.0-PuTTY_Release_0.64
[1/19/2016 1:50:14 PM] Server version: SSH-2.0-OpenSSH_4.3
[1/19/2016 1:50:14 PM] We believe remote version has SSH-2 channel request bug
[1/19/2016 1:50:14 PM] Using SSH protocol version 2
[1/19/2016 1:50:14 PM] Doing Diffie-Hellman group exchange
[1/19/2016 1:50:14 PM] Doing Diffie-Hellman key exchange with hash SHA-1
[1/19/2016 1:50:14 PM] Host key fingerprint is:
[1/19/2016 1:50:14 PM] ssh-rsa 2048 <removed>
[1/19/2016 1:50:14 PM] Initialised AES-256 SDCTR client->server encryption
[1/19/2016 1:50:14 PM] Initialised HMAC-SHA1 client->server MAC algorithm
[1/19/2016 1:50:14 PM] Initialised AES-256 SDCTR server->client encryption
[1/19/2016 1:50:14 PM] Initialised HMAC-SHA1 server->client MAC algorithm
[1/19/2016 1:50:14 PM] Reading private key file "I:\RDM-Genereated-Private-key.pub.pri"
[1/19/2016 1:50:14 PM] Unable to use this key file (unable to open file)
========================================
SSH Port Forward entry not referencing Key stored in repository
Perhaps i'm making a mistake here, however other ssh entries work without issue using the key stored in the repository.
When I create an SSH Port Forward session and select the Private Key tab, the Private key type of Repository, and then the key, RDM attempts to find a key file that stored locally on my workstation instead of the repository.
I've created other sessions (ssh, rebex) using the same method and they work without issue.
Is this a known bug?
My overall goal is to create tunnels for remote console access (idrac specifically), however I have to first jump to an ssh host that's remote, then tunnel to the idrac interface. I'd like to accomplish that with a single entry.
Currently using 11.0.18.0.