cyconical

[cyconical]

Thanks reza,

sure, the firewall can do the job! Wasn’t thinking about that.

I already changed the SSH port, but noticed, that a connection via nx protocol was still possible, and thus my ssh connection with private key would have been kind of obsolete.

 

[cyconical]

Hey Tor,

thanks for your reply. Unfortunately my clients are using Linux, Mac and Windows, so an option within the nxs file would have been the best solution. I also want my clients to download the nxs file as I want to change the SSH keys every week or so. What do you mean by ‘client startup script’ which shall be triggered?

My goal is it, for the clients, to download the nxs file, open it, and after they log out it shall just close itself. Is there an option for executing a script on the local client’s computer after logout?

c.

[cyconical]

It should be “ ”

[cyconical]

Ok, I found a solution.

I put the key into the .nxs file (<option key=”Public Key” value=”…..”>) and replaced the spaces in it with “$ # x a ;” (without the spaces between the chars, I noted that when I write it without spaces, it is not shown properly). A separate key file is not needed anymore.

• This reply was modified 9 years ago by cyconical.
• This reply was modified 9 years ago by cyconical.

[Author]

Posts