RDM upgrade broke SSH key login
So, through unrelenting trial-and-error, I have (hopefully) found the changes required to restore previous functionality.
Apparently, I need to manually edit each and every one of our server connections/profiles, changing two things:
1) Credentials : "My personal credentials" to Credentials : "My privileged account"
2) Tick the checkbox "Use credentials from template".
To be honest, I've been messing with settings all morning, so it's possible there were some other config changes which contributed to the fix, but the above was definitely the piece finally got it working.
Hopefully this may be of use to others who encounter the same issues following an upgrade.
Kind regards,
RDM upgrade broke SSH key login
I have just started up my laptop with an old RDM installed (2023.3.39) and connecting to the same server I was testing throughout this exercise via this old client successfully connects, so it does look like something has broke in the newer version of RDM :(
RDM upgrade broke SSH key login
So I thought I was onto something by changing the connection profile's connection "Credentials" setting from "My personal credentials" to "My privileged account". As upon drilling into this option it appears to ultimately point to "My personal SSH key".
However, despite thoroughly checking the config of this SSH key screen, RDM still just appears to try to login to our target using standard username. "My personal SSH key" is pre-configured with my login name, so I am expecting RDM to simply send the username with the SSH key and successfully login, but it still appears to not even send the username :|
RDM upgrade broke SSH key login
Good morning,
Typically, we use RDM for connecting to all our Linux servers using pre-made/shared SSH keys. This is the way my team has used it for years.
We hadn't upgraded our RDM client (2023.3.39.0) for a good while, but recently found time to upgrade it to the latest, and further upgraded again today as there was another release. We're now on 2024-2.21.0 64-bit. For this upgrade we had to install .NET 8.
So, onto the problem....
Since the upgrade, RDM no longer appears to attempt to send the SSH keys to our RDM connection target. It just seems to try to log in via password (which the server would expectedly reject) and fail.
If I check the RDM host profile (based on a template) I see
Credentials : "My personal credentials"
I seem to remember, or have a feeling, that this should be set to "My personal SSK key" (or words to that effect), but if I click the drop-down to change it back, there exists no option to change it.
Am I looking at the right thing here? Surely SSH key login hasn't removed from RDM!? If I go to File... My account settings... My personal SSH key... I can see my configuration, with the SSH key either copy/pasted or I can point to the path of the SSH key file. So it looks like RDM still supports SSH keys in principle, but where am I missing the piece where I restore the use of this login type in all our connections.
As a sanity check, I fired up standard PuTTY client, pointed it to my SSH key, and boom, it worked first time, straight onto one of our servers. So I know this is a problem in RDM.
Please tell me SSH key login hasn't been removed from RDM!? This would be a deal breaker for my team.
Kind regards,
Elliot
MariaDB Support (and farewell to RDM)
I can't express how disappointed we are by the withdrawal of MariaDB support for storing the RDM connections database.
RDM was the perfect fit for my infrastructure team mainly due to this feature and now we're left frustrated as we'll have to waste time and money looking for an alternative product to replace RDM (your alternative options are inadequate or financially unequivalent).
After years of using this product, I guess it's time to say goodbye :(
New right-click menu is infuriating
Awesome. Updated this morning and all seems well! Thank you :)
New right-click menu is infuriating
Hello,
It seems that since upgrading to the latest RDM (v2022.3.15.0 64-bit), now when we right-click to paste in the terminal/PuTTY window, it correctly pastes, but now also provides a menu (with options for Copy, Copy All to Clipboard, etc), which must be clicked off to dismiss it. Every. Time.
My team has been using RDM (enterprise) for years now, and not once has anyone mentioned that such a menu would be a good idea. No doubt different customers use RDM in different ways, but for how we use it, this "feature" is disruptive, distractive, hindersome, annoying and infuriating.
Please can you advise how we can turn this unwanted feature off?
Regards,
EJ
PuTTY Timeout
Hello,
To be honest I'm unsure what the difference is - I was under the impression that PuTTY (the executable) is invoked when you open an "SSH Shell session" within RDM?
All of my connections use PuTTY (as far as I know), so I am guessing that the time-out is there? How can I 100% confirm this?
Something else I have also checked: my installed PuTTY exe has Connection keepalives set to every 5 seconds.
PuTTY Timeout
I predominantly use RDM for SSH connections.
Originally, I had my RDM set-up so that my PuTTY connections never timed-out. But recently, my PC died, so I had to move all my backed-up configs, etc, to a new computer.
Despite importing my RDM config, I am finding that my PuTTY/SSH sessions keep timing-out. It's really, really frustrating, as sometimes I have many windows open, all deep into file-systems, watching files, monitoring etc, only to get back to my workstation and find all the sessions timed-out. This definitely never used to happen before the crash/reinstall.
I have checked what RDM settings seem relevant:
File...Options...Types...PuTTY is set to 'PuTTY'.
My installation Path for PuTTY is also configured correctly and 'Application is ready'.
My Default Settings... SSH Shell... General... Advanced settings have the 'Enable TCP keepalives' set, with a ping interval of 15 seconds.
My session profiles DO NOT have the 'Automatically close session after X minutes' option set.
Can someone knowledgable in this area enlighten me on a way to fix the timeout please? :)
Thanks
SSH/terminal windows crashing in latest RDM
Hi all,
Thanks for addressing this bug. I can report that v2019.1.25.0 64-bit is no longer dropping my SSH/terminal sessions :)
SSH/terminal windows crashing in latest RDM
Yes, this is with RDM Enterprise Edition v2019.1.20.0 64-bit
SSH/terminal windows crashing in latest RDM
I have found that this isn't caused by a buffer issue as previously suspected.
I had a SSH terminal window open, where I was editing a file on a linux server (using VIM). I left my desk, and when I returned, and switched to the RDM application window, my terminal session had gone.
This is now a major issue, as it means I am losing work (the file was half-way through being edited).
The problem is also definitely nothing to do with session time-out, as my other two terminal sessions were still running (one of which was against the same server).
SSH/terminal windows crashing in latest RDM
I have checked the [Advanced] settings for the session, by the way, and it isn't set to close after any amount of time.
SSH/terminal windows crashing in latest RDM
Hello,
Since upgrading to the latest 64bit Windows client yesterday, I am finding that some SSH/terminal windows close/quit/crash/exit of their own accord.
For instance, I have an SSH/terminal window open where I am watching server logs. After an undetermined amount of time, the SSH/terminal window just dies and closes.
I watch server logs every single day as part of my job, so this definitely wasn't happening before the upgrade.
I am wondering whether some text buffer is getting full and crashing the terminal client/window?
Any help or advice would be appreciated.
Kind regards
Is it safe to upgrade?
Hi David,
Thank you for your reply.
My Windows users are on 14.1.3.0 64-bit (released 2019-01-23)
My Mac user is on 6.2.1.0 (released 2019-02-21)
As it's been 3 months now since the last Windows official release, do you know if there is a new one on the immediate horizon?
Is it safe to upgrade?
Hi all,
I have 4 [enterprise license] users of RDM. We all use the same shared central database (self-hosted MariaDB).
I really want to use the latest RDM Windows beta client to enjoy the improved SSH/PuTTY/terminal emulator/client, and bug fixes.
Question 1) If I upgrade my existing RDM Windows installation to the latest Beta version, does it upgrade/change the central database in any way?
Question 2) If the answer to Q1 is 'yes', then will all my other RDM Windows users need to upgrade?
Question 3) If the answer to Q1 is 'yes', what about my Mac user? I don't see a beta version available for Mac, so will they be unable to use the central DB?
Thank you!
Cisco ASA ASDM addon oddity
Hi,
I could have sworn, upon initial testing, this add-on was working, but we have started using it in our daily routine now and it's behaving oddly.
We double-click our "Cisco ASDM" connection, which correctly launches the ASDM IDM, but then it automatically overwrites the "Device IP Address / Name" entry in our ASDM IDM with a single "+" character, clears the username/password and then tries to launch the connection to the ASDM device with hostname "+".
Does anyone have any idea what's happening? Why is RDM replacing our ASDM hostnames with a "+" before launching?!
Thank you
Tag management
It appears that host tags can't be deleted once created?
And, also, because the tags are fixed in order of creation, it's laborious to locate tags when you start to amass them.
Any chance tag management can get some love? :)
Store/remember SNMP community
Hi,
The community string is the string which defaults to 'public'. It behaves a little like a password for accessing the SNMP device.
Most organisations will change the community string on their SNMP devices to something other than 'public' as a layer of security to stop people randomly connecting.
Can I run macro/script against a folder?
Sure, here's the macro I am currently experimenting with:
<?xml version="1.0"?>
<ArrayOfConnection>
<Connection>
<Cmd>
<Arguments>-s -f:range $SITE_CUSTOM_FIELD1$</Arguments>
<UseShellExecute>false</UseShellExecute>
</Cmd>
<Tools>
<Visibility>Hidden</Visibility>
</Tools>
<CommandLine>"C:\Program Files (x86)\Angry IP Scanner\ipscan-win32.exe"</CommandLine>
<ConnectionType>SessionTool</ConnectionType>
<Group>Sites\COMPANYNAME\CITYNAME</Group>
<ID>390bc370-e523-4096-83ce-a964100e6089</ID>
<Image>iVBORw0KGgoAAAANSUhEUgAAACgAAAAoCAYAAACM/rhtAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAAEnQAABJ0Ad5mH3gAAAu6SURBVFhHzZgLPNTpGsf/gzAokpZKM2NcJkKSS2d1s7kWotxvlZK2tj050nbSbZ3QqtVWq3vtaXWRrXarTVEb0V1KJSQGgxIq3YvM7zx/zZxjHe1uu8757PP5fD8G83mf7/s87/vO+x/mj4aZH5TtFrV+47v6eWNAyrNmlkAiqBPhnZhKTJPhkfSi2XRuW5VgjpQvG67nw3R+6+iVRxqLbzWVS+teVOAu0UA0Ek3EA+IR8Zh4SjwjXhCN9P6Ug813xix5HWw0r1xFNlwPx1gojVre+reMG9XPxc8rUEOJa4l64h4hF20mHhIthFx01+n7D8aveBVrGSNVl43Ww6HJE6rquy0ISbpUnV9bIa2gpGKimpAQbDXlovcJeTVZ0R8KJW2j4l5niGKbestG66nQ5zJq/GmMhuAqoyZ4qaLv1LY4vVJaStUrp8R3iEqiipBXs2vbc0uq2u1iW0tFEdKelNNVJyFXjqbgrNJg4zcarlbSDz4fh+Fb9iC9pAbFlLiEKCNYUbaaXUVraRI5t6sx8tPrjzUsPhvDMCN6yQb/Q8FhuPq2DJe/pZfA5IXOzA8hSJsI4wJfCC9Nh8+OGhQ8rcR1ErhJ3CK6irJtZ0WPk5zLjnxoeU8CR1N4lya8gNHQ6y/L87tCgVHjhTEqgqtqw83bhV+7wzTfD6Kr/jC67guTtH3YUFCLK5T8KlFE3CDkoqXEbYJt++X7YvjsvwyjnIUQZHlDd/k4qdIggyckuZEKMEiW7z2DWkqCt3V87aTmh31hcT4QpgUBML7mB+G1IFh9UYX8J5W4RAIFRCHRWVTedlZ0RkYFDLMSwS+myt+cAiPqAG+7G5RNhryk7iQzjOg916MaX4/I13K2lloc84PVuSCYXwqECckZ3qAkh9YjNqsOZyn5eeIicZmQi14j5G1ferwOwj0ZGFjuA/0yHwhuTe4Yw+SKHwZ+7ghFXUEbw+XNpayKb5P/eijQLk1Rt7WA6T4fWJ0PwpBCf/BLJmNQ+SQMKKNqrr+OYw/EOEMC+cQ54gIhF2Xbfomqm5QngeGOU9Cp8oJupRdJemMwSRoUUxVpmYgu+qF/lINUoR+/lVHhO8ry/0qo8d0UdYxeGCS6Si0uBnbMdkDlJPSt94BW/UQM+CkRc0/dQfazCpwmkVwij+gsmv+4EvG5EhgdSodmjQ/61nlAp8YTumIvmqQ3eKWTO1rNdmRIri/6uFiD4Q4uY1SFPJnFO0KTr8Wo8ouptTDP8e+Q06XZqze5Q7nFFRp3J8Fk73F8IxEji0ROEj8ROYRcNI/Eky9KYPLjXmjU+EOjYQL63J2AvrUkWe0JPZosK8l2xJCqyHbHeJ8XlAYYSRk1g3Uyk3eEKj+QUdN/bbzFA6ZXAjD49tvZqz50A7fZDf0LoxGcVYQDjypxjGROEJ1F2YqmS6owdOdFaBQsBFccCrUaP2jUe6EPVZ+V7E8THlAxqaPV8ioOvRQA3VkOVEVBKaNuoCuz6SbU+Ad68YRtVmdp3dFxwgr2p1lrk2Q/iSf4R1ORcL0aP5DIUeJH4jjBimYTp4iDdKQEpdfCc1c1nLZVY1RqNWxTJLBKlsByVQ0sVlXDPIkmkSjG0KRymO48BNMLUyE66A1Gmd/UcXp0G1wjfTpWJHozR2H4uWBY0K41phawreDRbHlFYRh3OBubaqtwiERYySMEK8lWkxXtWk152+W7nV2f8mPp0tMKxJ0Sw/TgRogKgumUCADXYkgrbdAlZMN5K0URGRk5YNasWTzhELsgro5ps+XX3rDPDunA7mQIhucEwjIvAOaZCxGZVYV9zyrxHSU4SHQVzSQ6i7IV7bw+WVF2I7G7fX2hGLa7M2CaOw3m+f6wojy86WOhPdAizds7wCQqKoo9wDlMTEzM96mpqTmrVq25GRMb17p0RyKWpX2B5bvfsmzPF1i6dxUmbc5BYlkN9tLg6cR+Qi76PXGY6CzadX2youyxxIruLpcgcO0dLNq1CYvTkxC3b1VHjkVr4xG3YuW9jRs35icnJ2fPnz/fiYmOjt6dnp7+8vjx49Ls7Gxkn/xvMk+cgteGB9hJn7tpbAJCLppBHCA6i7Lrk227XFS+Ptm2H6ivhufqx8g4eq7bXKwD65KVldUeFxd3mgkJCRGRbUNOTg7exYZ9RRiV+Ayf5jYgkWa/g845VnQPsY+QV5MV/aX1eZR2/6SvHmPX9wXd5ulKfHz87Q7BpKSkpszMTNa8W45lnsC2/XmI334VH68rx5SkOngk3MWUlLuI2HsPGyTVPxOVV7Oz6KGHYkTtacDqbwuQmdl9ns6wPosXLz7LODg48ObOnVuydetW7Ny5873YtC0NM9dcxcqbkn+3vTvR76jiCzMliPkqF1u37+p2rK6sXbv2NW2UTxhbW1t/evEoISEBVMn3YkVCCiI2FSKFKriLRN61PhOvSBCacIbe/2W343QH7Y2nnp6eIxmRSORnbW2db2dnd87C0uau+bARUnu/sbAPGEd8hJFBTvhLsDNGhThjXJgznMKc4BY+HhMJt4hghO4txWaq0E4S+YaQi8rX5+Y6ukUvuoaPpoViQoQPPGZMgVekH7wjAzAlKgj+UcEInB2G4MgwBAQGt4eHhz+ZPn16i6+vb6Ojo6OIPQoVzczMlFkUewvdOeqDXwsTXGCVFwLL8xGwKJyNYTdnw+5OFBxrIuBRFwr/Bn+ENvrAt2wepmVLsIVEthE7CFaUlfyW/Z3WndXqBihXTIXyfReo1DuDW+MMtUpnaJS5QLvIDXoXJ0D/zET08xkBdW2DSgtr69FUrJE2Nja2fn5+Xa9gY5Xo4y6PbtBSiyw6oC/PgHnRbFiUzIFV5cewq50Fh4YZGNM0FWMehsM+fzuii2qwkWQ2E51Fv26qhMM/K8C9HgOFp85QfOIMpRYX9HrkCuWHrlB54Ire9yZAW+KBvnvHg6Nl0M6oChbKRH4hNHhmCprCev3Yj2CZHw7zwkiYFUdhSHkUTKvpZ30kRCRp2ByBEWlFSGqswgZWiJCLfkmfx+5HStGncBk4T13+I/iYBElSmSRZQY37E6B5wRVKI83A9BacYpj+GjKLXwl1wV9VjYxfG6V6YOjFcIiKpsOwNAKCygjo10yHXv1U6NRG4sMddfiSnta+Iql1BCu6ji6qIafF0LmwBpzH7uA8cyJJZyjIBDtXkVtCr8OswPTh19ItxkKW/TdE74H9GA1+GtfM7I3ogHfH1Ut4g71+BUBP7A/t2inomxcP/5N1WM1WjEghWNFYegwddDQdCg89wTwnuXcJ3qPXS2ykjI5BMy0rd8qq8Db5bw1qNVXyiqqZabvhd150RfcDj242ehXe6Ee3Y326ysdW1WAVSSUTrGjSIzEMU4uhVB/QIfczQaKzoGKqPRht4XO6XkUyjJmyLOt7hhrPmshV6C18/kH8OOhfoGcSei7REfvAiO51/yCpBCKRWNZYiWFbKqBaMrdDhhVjWLnOFWx0gtJ1RyjMHAZGRb+B1l0so2v5B7+b6aOvzajzYziaBiVc92FSrdWj0f9wDMZn1GAFiX1OLKirgv3+W+h97bOOzcDKsFIdcoRCM5E1Cgoxw8EZavKKbs6nCK+OU6OHQpHhGtjRg80ahUGG9z+I2I05ZdVYTnKfNYnheLASWoVLoMS2jtqo0EKStXR0/DQanGQbcKYMlTJDhK2MlvAkbYZQRoUnlI3bo0G3XDMNhiuy4c+pKo97RM+8dP3yOVINLYdYcGzM2zluQ9s5jmbtzDATKWNiDIZvCKZfxzo7yGgY+NFyGdCTVes2dMJemYzd3HJjactt6bxy8Rv90Pyzijr2Gyh5OnGGUeedoIevrYwqbxk9pXkwjFBT9kXRe+7S3xmC6DdRYefrW+bX3mm3THyZO3jeS0PZv/4E4QdF0d9fbZtxtf6l/fpnN42ipSNl//lzRL8I6UCrlc+zrNc8FRvHtI6R/fnPE0YL2lwE0W3F/Hltbsxy/H/W1PsE/5M290EfSycbzZP+j76V7xoM8y/DE2MPIxvNEgAAAABJRU5ErkJggg==</Image>
<ImageMD5>7fed033494cc8972b40d2078bab52237</ImageMD5>
<Name>Subnet Scan</Name>
<Stamp>06129c41-59c1-4aee-a5d7-2f1365dbb478</Stamp>
<TemplateSourceID>87f1b07d-2ff8-4797-8a08-831fc8e4aadb</TemplateSourceID>
</Connection>
</ArrayOfConnection>
Can I run macro/script against a folder?
We have created folders for each of our branches/sites.
What I want to be able to do is to right-click on a folder (site) and run a macro/script to scan the site's subnet (i.e.: show me all the live hosts).
So, for instance if my site (folder) is called 'City1' and we add 10.11.1.0/24 in the 'custom field 1' for that folder, I want to right-click on 'City1' and initiate a subnet scan on 10.11.1.0/24.
I have tried to create a command prompt macro, which invokes a Windows network scanner tool, but when I then right-click on the site (folder) it asks me which sessions I want to run the macro against? I don't want to run it against sessions, I want to run it against the folder.
Does this make sense? And is this possible? :)
Thanks
Moving password lists corrupts them!
Thank you for the update :)
Custom Column populated by SNMP request
Any chance we can configure custom columns to be auto-populated by a pre-defined SNMP GET request?
Or even if you had to right-click the host to run the SNMP query, but have the result dumped into a custom column; that would still work.
Thank you.
Store/remember SNMP community
It seems that there's nowhere to store a preferred SNMP community string - or RDM doesn't remember that last one used.
Can we request this as a feature?
Configuring terminal emulation
Hi David,
I have just tried the latest portable Beta version and can confirm the screens appear to build properly in this newer version.
We are now in anticipation of the final release :D :D :)