Using Plink instead of PuTTY and passing arguments through stdin: Plink supports stdin / stdout communication, however the terminal functionality is very limited and not usable in practice after the login was successful.Instead of passing password argument, using SendKeys to type password into the promt: Unreliable, as there is no way to read the PuTTY output and know when the application is ready for the input to be typed in.These are the things I researched so far: So far I haven't found any practical solution to circumvent this. The problem with the current approach is, that in the Windows Task Manager its possible for an administrator to see all started PuTTY instances and the corresponding credentials as command line arguments. So the purpose of the application is to automate password retrieval and login to different servers. The arguments are passed to PuTTY through the command line interface. The password for each server is retrieved from a password manager service. For this the application currently starts the PuTTY process and passes arguments, like the hostname, username and password. I am maintaining an application in our company (written in C#), which runs on a jumphost and provides the functionality to search across different servers and initiate a PuTTY connection to that server.
0 Comments
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |