Tag Info

New answers tagged


You can use the -m parameter this loads a file that will be executed on the server. The content of the file should contain the "ssh my_user@other_server" Alternative you can use a session and set it up so that under connection -> SSH you have "ssh my_user@other_server" this will load the session connect you to first then executes the ssh connection. An ...


Create and save a session to connect (specified as Host Name), with the following proxy settings in the config GUI: Proxy type: Local Proxy hostname: Port: 22 Username: Maihabunash Password: secret123 local proxy command: plink -P %proxyport %user@%proxyhost -nc %host:%port Then run putty with the saved session name: putty.exe ...


Another reason somehow related to pam that may affect hosts with powerbroker/pbis/likewise authentication. grep /etc/pam.d for the "lsass" occurance: grep -r lsass /etc/pam.d if you see in the output something like: /etc/pam.d/common-session:session sufficient pam_lsass.so then it's probably the root cause of the problem. The quick fix is ...


You need to convert the provided PEM file to PPK file using Puttygen tool in Windows. Open puttygen and click on import key option in the menu. Once it is imported you will see the button which says "Save Private Key". Save it as a xyz.ppk file name and they load that ppk file in putty and login. Hope this helps.


To convert .pem key to .ppk key using *nix command-line version of puttygen use: puttygen mykey.pem -o mykey.ppk See puttygen man page. There's PuTTY rpm and "putty-tools" package available for many *nix distributions. The .ppk format is proprietary to PuTTY, so tools outside of PuTTY toolset (like ssh-keygen) do not support it. Note that you can ...


Change your username to "root" and it can work or AWS will tell you what username you should use.

Top 50 recent answers are included