Migration tool SecureCRT to Asbru

[daxm]

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Not really. Just would be nice to have a migration path.

Describe the solution you'd like A clear and concise description of what you want to happen. Simple enough. I'd like a migration tool to take a SecureCRT backup file and import the data into Asbru.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Manually recreating? Ugh.

Additional context Add any other context or screenshots about the feature request here.

[gfrenoy]

Thanks for the suggestion, it would of course be a great feature.

Would you have some additional information to help anyone who would like to contribute ?

I'm thinking first about:

• a documentation about the SecureCRT backup file structure ?
• an analysis on how connections parameters should be migrated ?
• an example of a SecureCRT backup file ?

[daxm]

I'm not sure how to provide a sample backup file that would be "anonymized". Do you have a sample file of the structure that Asbru uses? I'd be happy to share with you directly (aka not publicly publishing) my SecureCRT backup file. Also, I'd be happy to work on the conversion "tool" however I'm no professional programmer. If I knew the structure of Asbru I could at least give it a try.

[gfrenoy]

Thanks for offering your help; here are some instructions.

• To have a sample Ásbrú configuration file, you can create a new temporary configuration with asbru-cm --config-dir=/tmp/asbru and create some new connections ;
• That's what I did, here is the corresponding asbru.yml that you will find in the configuration directory: asbru.zip ;
• I used 192.168.1.1 for all host IP ; user as username and pass as password ;
• The structure of the file is somehow "verbose" but simple.
  • There's a first defaults section ; you can just keep it as it is
  • All connections are kept in the environments section
  • Each connection is identified by a GUID (note: consider using cat /proc/sys/kernel/random/uuid)
  • You can keep a kind of connection template per connection type (ssh, xfreerdp, etc.) and only replace some of the parameters
  • At least, the following parameters will need to be changed for each conncection : name, description, ip, parent, pass, title
  • You will need to have some "already present" entries like __PAC__ROOT__ (the root) and __PAC_SHELL__ (the local shell)
• You'll find also example of migration scripts in the utils directory (see https://github.com/asbru-cm/asbru-cm/tree/master/utils)
• When testing, be aware that there is asbru.nfreeze that is loaded (if it exists) before loading asbru.yml so you need to delete the nfreeze file to make sure the yml is properly loaded
• You can contact me on IRC or Matrix for a more interactive discussion (see https://www.asbru-cm.net/support.html)

[daxm]

Well... I tried.  I tried and tried but I cannot get out of the SecureCRT's funky XML into anything I can use for importation to Asbru.  :-(

I'm 100% sure it is possible but not at my programming skill level.

On 6/26/20 12:40 AM, Gaëtan Frenoy wrote:

Thanks for offering your help; here are some instructions.

• To have a sample Ásbrú configuration file, you can create a new temporary configuration with |asbru-cm --config-dir=/tmp/asbru| and create ;
• That's what I did, here is the corresponding |asbru.yml| that you will find in the configuration directory: asbru.zip https://github.com/asbru-cm/asbru-cm/files/4835389/asbru.zip ;
• I used 192.168.1.1 for all host IP ; user as username and pass as password ;
• The structure of the file is somehow "verbose" but simple. o There's a first |defaults| section ; you can just keep it as it is o All connections are kept in the |environments| section o Each connection is identified by a GUID (note: consider using |cat /proc/sys/kernel/random/uuid|)
• You can keep a kind of connection template per connection type (ssh, xfreerdp, etc.) and only replace some of the parameters
• At least, the following parameters will need to be changed for each conncection : name, description, ip, parent, pass, title
• You will need to have some "already present" entries like |PACROOT| (the root) and |PAC_SHELL__| (the local shell)
• You'll find also example of migration scripts in the |utils| directory (see https://github.com/asbru-cm/asbru-cm/tree/master/utils)
• When testing, be aware that there is |asbru.nfreeze| that is loaded (if it exists) before loading |asbru.yml| so you need to delete the nfreeze file to make sure the |yml| is properly loaded
• You can contact me on IRC or Matrix for a more interactive discussion (see https://www.asbru-cm.net/support.html)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/asbru-cm/asbru-cm/issues/653#issuecomment-650004139, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZOMZ7FBZVAH4HACIHCWKTRYQ7FHANCNFSM4OF44GJQ.

[gfrenoy]

I'm 100% sure it is possible but not at my programming skill level

Thanks for trying, be sure it's a very necessary step to succeed :)

And feel free to share what you tried, where you are and what does not work for you and we'll try to help and fill the skill gap...

[daxm]

DM me and I can share with you my XML file. I'll also share with you my "bad" coding skills. :-) You can find my contact info at daxm.net, FYI.

[gfrenoy]

Sent you a mail, hopefully it will not reach your spambox :) That being said, we should discuss this publicly (without disclosing any sensitive information) since I believe it can help others to contribute.

[hanspr]

@daxm

Assuming the evaluation version of SecureCRT has all options available. You could create a virtual machine, install an evaluation version of SecureCRT

Then

• create some connections, as many as you think would represent the possible configurations that should be imported
• or, import your real connections, replace all hosts, and sensitive data from the connections

Then export the connection information from that evaluation version

Upload the generated file here, so we all can take a look of the file and see the path to solve this.

[daxm]

See attached.  I hope it helps!  :-)

On 10/7/20 8:02 PM, Hans Peyrot wrote:

@daxm https://github.com/daxm

Assuming the evaluation version of SecureCRT has all options available. You could create a virtual machine, install an evaluation version of SecureCRT

Then

• create some connections, as many as you think would represent the possible configurations that should be imported
• or, import your real connections, replace all hosts, and sensitive data from the connections

Then export the connection information from that evaluation version

Upload the generated file here, so we all can take a look of the file and see the path to solve this.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/asbru-cm/asbru-cm/issues/653#issuecomment-705285864, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZOMZ45VBZQPPB23BWUTITSJUMT3ANCNFSM4OF44GJQ.

[hanspr]

@daxm

Can not see any attachments in the email or here on github.

[daxm]

I don't see a way to upload a file to the GitHub ticket so I uploaded the file to here:  http://daxm.net/scrt-sample-config.xml

On 10/8/20 12:25 PM, Hans Peyrot wrote:

@daxm https://github.com/daxm

Can not see any attachments in the email or here on github.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/asbru-cm/asbru-cm/issues/653#issuecomment-705744913, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZOMZZJOBR6EAZDN4BXV7LSJX72VANCNFSM4OF44GJQ.

[hanspr]

Just drop any file on top of the editing box, or click on the message, the instructions are located at the bottom

In any case, I downloaded the file from your link.

Thanks

[4mig4]

That is indeed a very useful suggestion and very nice feature to have if it was available.