Import connections from asbru-cm

Hello,
Could you provide us sample file to import?

Regards

Hello! I made test data with different types of connections. I hope that everything is as it should be. Thanks.

Hello,
Do you know if they support a csv format? This is yaml and we never implemented this in RDM?

Regards

Do you know if they support a csv format? This is yaml and we never implemented this in RDM?

Hi! Unfortunately, export is only in yaml format (

Thank you for the information. I will create a ticket for that.

Regards

Any news?

Hi beliy,

There is no news regarding this feature for the moment. I increased the ticket priority.

Regards,

Thanks, we will continue to wait

Hi beliy,

Just letting you know that I'm currently working on a way to import connections from asbru-cm.

Hi beliy,

Just letting you know that I'm currently working on a way to import connections from asbru-cm.

Hi! Good news. We look forward to it.

Hi Beliy,

This feature is ready and planned to be for 2023.2.1.0.

From this version you'll be able to import your connections from asbru-cm into RDM Linux.

Supported connection types are:

• RDP
• VNC
• SSH
• Telnet
• SFTP
• FTP
• Generic Command

I've been waiting for this opportunity for a long time, but unfortunately I couldn't import it.
https://i.imgur.com/GHM1lib.png

Hi Beliy,

Could you send me the contents of your file by private message?

Hi Beliy,

Could you send me the contents of your file by private message?

Hello, I sent a PM

Hi beliy,

The issue was due to a "mosh" connection in your file which is not supported.

I was able to import your file as follows:

1. Open the file and search for "MOSH".
2. Scroll up to the connection ID (e.g: c7773d50-0f6f-2f7f-5902-1cafa3507a41)
3. Select and delete everything down, including the ID, until you reach another connection ID
4. Save and import it to RDM

I also made a fix to avoid this in the future.

Hi beliy,

The issue was due to a "mosh" connection in your file which is not supported.

I was able to import your file as follows:

1. Open the file and search for "MOSH".
2. Scroll up to the connection ID (e.g: c7773d50-0f6f-2f7f-5902-1cafa3507a41)
3. Select and delete everything down, including the ID, until you reach another connection ID
4. Save and import it to RDM

Thanks, after removing "MOSH" it was able to import.
But for SSH I noticed the following nuances:
1) "Username" is not imported
2) "After login command" is not imported
3) asbru-cm ignored extra spaces in values, and RDM is very sensitive to them. Is it possible to also remove extra spaces at the beginning and end of the variable during import?

Hi beliy,

I've corrected points 1 and 2 and now the spaces at the beginning and end of most values are removed. A hotfix will be deployed soon.

Note that RDM linux has no special case for post-connection commands like asbru-cm does ("On MATCH", "On FAIL", "Expect", etc.) and these parameters will be ignored by RDM.

if you find other options available in asbru-cm that are also in RDM, but are not imported, don't hesitate to mention them to us and we'll add them.

Hi beliy,

I've corrected points 1 and 2 and now the spaces at the beginning and end of most values are removed. A hotfix will be deployed soon.

Note that RDM linux has no special case for post-connection commands like asbru-cm does ("On MATCH", "On FAIL", "Expect", etc.) and these parameters will be ignored by RDM.

if you find other options available in asbru-cm that are also in RDM, but are not imported, don't hesitate to mention them to us and we'll add them.

Thank you. Most use "Expect" in the same sense as "After login command". Personally, I use to enter the command "sudo -i" to become root. I do the same in RDM, but through "After login command". Perhaps it is possible to add an option that will also allow importing commands from "Expect" to "After login command" for those who need it?

Sorry for the misunderstanding, the commands you enter in the "Expect" tab will be added to your "After login command" in RDM.

Note that RDM linux has no special case for post-connection commands like asbru-cm does ("On MATCH", "On FAIL", "Expect", etc.) and these parameters will be ignored by RDM.

What I meant by this is that other parameters such as "On MATCH" and the "Expect" text box will be ignored by RDM, but the command you wrote in the "Send" text box will be added to RDM if it is enabled in asbru-cm.

This should work as expected in your case, since you don't seem to be using any of the other parameters proposed by asbru-cm for your command.

Thanks, really looking forward to this update

Hi beliy,

A new version is out and should contain everything we've been talking about.

Let me know if anything is missing.

Thank you, everything that was discussed - worked. There is a problem with SFTP (hanging), but it seems that it is not related to import, because all parameters are ok. I plan to make a bug report on the problems after several weeks of testing.