![]() To start using it you need a config like this: # LocalPort TargetHost TargetPort SshHost SshUsername SshKeyPathġ8080 80 User D:\secure\path\to\private_key. That's why I come up with custom Powershell script, easy configurable, changeable, small, but works. Right-clicking on a tab or using the Tools menu will allow you to get to the PuTTY menu In the configuration dialog you can specify a bunch of options including an automatic login macro or passing command line parameters to putty. All PuTTY sessions are managed and stored under folders. The connection manager can be docked to the side by using the little pushpin button. However, for shared hosting users, you will need to enter a predefined username like u721233450. A login as: message will pop-up and asks you to enter your SSH username. I tried many solutions like SSH tunnel managers, but all were inconvinient for me: too many configuration screens, sometimes buggy (one time SSH tunnel manager purged all! settings I had! So I had to restore settings for all 30 tunnels). Multi PuTTY Manager (MPManager) helps to open and manage multiple PuTTY sessions in tabs. Launch the PuTTY SSH client, then enter your server’s SSH IP and SSH Port. I did find this question: How to reliably keep an SSH tunnel open?, but that's using Linux as the SSH client, and I'm using Windows. I'm planning on making a dedicated user with no privileges and not allowed to interactively log in, and use that.) Chocolatey is trusted by businesses to manage software deployments. Chocolatey integrates w/SCCM, Puppet, Chef, etc. (Yes, I am aware of the hazards of automatically logging in to SSH. Chocolatey is software management automation for Windows that wraps installers, executables, zips, and scripts into compiled packages. The two tunnels are one local tunnel, and one remote tunnel. The data I'm sending across the two tunnels is VNC connections, so I often won't be at the machine to clear errors and enter passwords. What I'd like to do is have an application that can set up the two SSH tunnels, and can automatically reconnect, without needing to manually do anything, including enter a password. This works well, except when the SSH connection drops: PuTTY displays an error message, and I need to manually close the error and reconnect to the server. ![]() I'm trying to set up a Windows computer to always have two SSH tunnels to my Linux server.Ĭurrently, I'm using PuTTY to open the two SSH tunnels: I log in to the server in PuTTY, leave it minimized, and never touch it. ![]()
0 Comments
Leave a Reply. |