First you need to obtain a copy of the installation package (e.g., putty--installer.msi). If you have a 64-bit computer, it is recommended that you install the 64-bit version putty-64bit--installer.msi. Almost any computer bought after 2015 has a 64-bit processor, except for the very cheapest ones. Many high-end computers sold several years before that. If you don't know or don't care, it is always safe to use the 32-bit version (putty--installer.msi).
Hi - is there anyway of changing the default window size when opening a session in SolarPutty? I have played around with the putty.exe settings (columns/rows) and the window size is affected for Putty directly but then when opening SolarPutty the window is always extending past the taskbar at the bottom and at the top of the screen, seemingly ignoring any settings from the Putty session. To resize the screen I have to pull in the sides of the display and then I can resize it. Prob a simple setting somewhere in SolarPutty to retain the settings on open or exit? Thanks
We have identified that Solar-PuTTY default windows size is set up incorrectly (exceeding screen size) for some Windows configuration and scale >100% in display settings. We will check if this can be improved in future.
Every once in a while I hear of windows users trying to find a good SSH client for Windows to connect to their Linux boxes. For the longest time, a couple of the more popular choices have been Cygwin and Putty.
Ok, maybe not...but its very likely that if you are reading this and find yourself needing to SSH here and there, you also use GIT. Well many are unaware that git for windows bundles several Linux familiar tools. Many might use these in the git bash shell.
Then I tried to copy those files in my ubuntu machine (21.04), and logged in loading the private key (open putty, write the user@hostname and then load the private key at SSH>Auth), but there is unable to connect being rejected by the server as this error says:
I see putty now allows you to configure pageant to let openSSH access keys via named pipes, and it can coexist with the built in Open SSH agent in Windows. It basically works like how you configure 1password on Linux and Mac, so taking over the named pipe shouldn't be neccessary. Any plans to change how it works on windows in the future? I fear that Windows or defender will suddently realize that this is not the correct process, and block it at some point.
Also, any plans to include native support for putty/pageant? Alot of windows tools like WinSCP and Devolutions RDM uses Putty as it's backend, so it would be useful to have support built in. I got it working with Nathan Beals' WinSSH-Pageant, but would be super nice to have it built in?
Go to the putty install directory on Windows (typically c:\Program Files\Putty) and run puttygen.exe. Go to the "conversions" tab and import the public key that you copied from Linux. Save it (it'll save as a .ppk file, which is Putty's key format).
When you connect, in the putty left-hand side, go to "SSH", then to "Auth" - under "Auth", load the .ppk format private key you just saved. Then connect. If you're asked for a user/pass, just hit enter on both. You should be connected / see a welcome message.
I don't know what else it could be. How is it possible that any server is reachable (so routing, connection all is ok) using a putty client, but ssh doesn't work using cmd, powershell, or wls linux? Interesting is also that Hyper terminal worked few days, after the issue occurred in wls, but not any more.
hi Marc-7910
i also had same issue with ssh command not working correctly but was able to connect to remote using putty, i checked with mulitple solution and many of them didnt work, finally i came across a thread that talks about saving login info in C:\.ssh\config file , i found that contents of this files were not correct , so you have to configure the names like below to easily ssh to the server
Your local Windows desktop system is now installed with an SSH program (PuTTY), an X-windows server program(Xming) and public/private key icon (e.g. jdoe.ppk). You also have configured a remote host connection in a saved session (e.g. compute) with host name and login details (e.g. compute.example.edu and jdoe). To complete the process, you need to exchange keys to allow a trusted connection from your Windows desktop system to this saved session.
follow the prompts and type your responses as shown below. Otherwise, proceed to step 4. Prompt Action [jdoe@compute ]$ Type ssh-keygen -C "key comment"
e.g. key comment=jdoe compute Aug26 Enter file in which to save the key (/home/jdoe/.ssh/id_rsa): Press return to accept the default key file name shown in parentheses Enter passphrase: Press return Enter same passphrase again: Press return [jdoe@compute ]$ Type ssh-add -L >> .ssh/authorized_keys
When you no longer need Xming, right-click the Xming icon in the taskbar and click Exit. Then click Exit again in the Xming - Exit? window. This will close all X-windowsand running applications.
I doubt that it is the client. For testing I downloaded putty 0.62 to a
Win7 Prof. and can without problem log into my PC and my laptop (both
openSUSE 12.2).
Other than that feedback I am afraid to be of no help.