PuTTY is a great Windows frontend, not to mention the need for an SSH client in the first place. On Linux, OS X, and most other UNIX-y based environments, SSH is generally purely command line, but still amazingly powerful. The SSH client allows you to store an amazing amount of properties based on a given hostname, even global defaults, in the 'sshconfig' client file. This file doesn't exist by default (per the comments on the question), but should be written at /.ssh/config. That path equates to: , your home directory, it expands on my system to /Users/jason.ssh, the leading dot makes it hidden.
![Something like putty for mac Something like putty for mac](/uploads/1/2/5/3/125385246/827355638.png)
If you're in Terminal and in your home directory, you can simply run cd.ssh and enter it. Config is the file name, it is a plain text file with configuration parameters. I use this file to control tunnels I always use, the private key needed for the connection, the username (if it differs from my local username), etc. See the manpage, either via man sshconfig on your own machine which will contain the most appropriate version, or you can view it online from. Some example contents from my ssh config file are: ControlMaster auto ControlPath /.ssh/sockets/master-%r-%h-%p VisualHostKey yes Host serve Hostname 8.8.8.8 User jason IdentityFile /.ssh/idrsa LocalForward 5901 localhost:5901 Whitespace is purely personal preference, it is not required except to separate Keys from Values. The first three lines are global properties, they affect every SSH connection.
The second section is a host-specific configuration. The Host line specifies the host tag you will use when invoking ssh. When running that, it loads all the properties listed until the next Host line. Since serve is not necessarily a DNS name, I specify the Hostname that it should actually connect to (no, not actually mine).
User is self explanatory and there just to be explicit, and the IdentityFile is the path to the Private Key file it uses to connect. Lastly, LocalForward sets up a port forwarding rule that I send through the SSH tunnel. The various syntaxes are all documented on the man page. There is no mechanism for defining a plain text password. Password entry is ALWAYS interactive when setting up the SSH connection.
If you want to log in automatically, set up. Storing plain text passwords is stupid, always. I use this to great effect. And the best part? All your SSH configurations are incredibly portable, it's just one file that you have to backup/retain, and move between system to system! Not so portable to Windows, but who really likes dealing with the registry anyway?
Did try adding it like this: sudo port install putty -d. How can I install PuTTY on Mac OS 10.7.5? Whenever i need some help in a topic or i need something.
I have no experiences with this App: - I only did a quick Google on 'OS X telnet GUI' and got a link to this product as the first hit - but it seems to do the same as PuTTY. There is a 30 days trial available. ZOC is a professional SSH/telnet client and terminal emulator. With its impressive list of emulations it lets you easily connect to hosts and mainframes, using communication methods like secure shell, telnet, serial cable or modem/isdn. Its sleek user interface has many ways of making your life easier. In its own way, ZOC is the Swiss Army Knife of terminal emulators: versatile, robust, proven.
Key Benefits:. Tabbed sessions with thumbnails. Customizable to meet your preferences and needs.
Scripting language with over 200 commands. Compatible with Windows 7 and OS X Mountain Lion. Administrator friendly (deployment, configuration).
Now $79.99 with attractive bulk discounts Key Features:. Emulations: VT220, xterm, Wyse, QNX, TN3270, TN5250. Communication: SSH, Telnet, Modem, Serial Cable. File Transfer: SCP, Zmodem, Xmodem, Ymodem, Kermit. Jason's is definitely the way to go, but I'd like to point out a feature of Terminal that may be useful. Within Terminal, you can make a direct connection to a remote machine similar to the way PuTTY does, without first opening a terminal window on the local machine. Simply select Shell-New Remote Connection.
In the window that pops up, you can add any SSH server to the right-hand column, including aliases defined in the /.ssh/config file. Using Jason's example, you would select 'Secure Shell' as the service on the left, and then add 'serve' to the list of servers on the right. In the future, you can open the dialog box (much like the main PuTTY window) and double-click the entry for the server you want to connect to. The only difference between this and PuTTY is that you put custom configuration settings in the /.ssh/config file, which I see as a huge advantage. Any terminal program could work with this answer, but I recommend iTerm2.
To store connection info and login with a single short command (no password typing required), you could use a key-login combined with an ' alias'. Once you have an ssh-key on your server and your Mac, you could login with a command such as: ssh [email protected] Using an alias within /.bashprofile you could shorten the command with an alias such as: alias s10='ssh [email protected]' Then in iTerm2 you only need to execute a command: s10 to log into the server at 10.0.0.1 using ssh key login. To store your session log (commands you've run) iTerm2 does this automatically, but you can adjust the amount of session logs you'd like to keep within Preferences - Default profile - Terminal - Scrollback buffer.
Tick the box for Unlimited scrollback if you prefer. You can also store your logs indefinitely, between sessions by saving them to files. Preferences - Default profile - Miscellaneous - Automatically log session input to files in your chosen file on drive.
The power of the command line I believe that you should only use the mouse when you don’t know what are doing. That is why graphical interfaces exist.
If you have a repetitive task, then clicking the same thing over and over shows that you are poor engineer. You need to take control of your tools to work in the smartest way. PuTTY is a fine example of having both options. You can clicky-clicky all you want and waste hours of of your life pushing your mouse around the screen. Or you can run a lot of the repetitive PuTTY actions from the command line. But first thing is to introduce to using the keyboard to get around Windows and open the DOS box.
It always surprising how so few people know that Windows can actually be driven using the keyboard and very rarely need to use the mouse. Installation You need to note the directory that you installed PuTTY to, something like this would be the default. Ahh, the speed and the comfort!! Can you feel that? But you’re right, I want even less clicking. BUT, I still have to click on grunter and then open with my mouse hand.
Is strikes me that PuTTY was built by people who are really CLI centric so there would have to be options for doing more. In Section 3.8 of the Help file, cleverly titled “The PuTTY command line” we get the following details. To start a connection to a server called host: putty.exe -ssh -telnet -rlogin -raw host If this syntax is used, settings are taken from the Default Settings (see section 4.1.2); user overrides these settings if supplied. Also, you can specify a protocol, which will override the default protocol (see section 3.8.3.2). For telnet sessions, the following alternative syntax is supported (this makes PuTTY suitable for use as a URL handler for telnet URLs in web browsers): putty.exe telnet://host:port/ In order to start an existing saved session called sessionname, use the -load option (described in section 3.8.3.1).
Putty.exe -load “session name” ALRIGHT!!!! Even better is this bit 3.8.3.1 -load: load a saved session The -load option causes PuTTY to load configuration details out of a saved session.
If these details include a host name, then this option is all you need to make PuTTY start a session. You need double quotes around the session name if it contains spaces.
So now I can open a DOS box (Ctrl-Escape, R, cmd, Enter – just to remind you again), then type. Freedom from the mouse! A little review then If you spend all day connecting to equpment, you need to get the connection done as fast as possible.
Spending all your life clicky-clicky on the cute little mousey is just distracting you from the task at the hand. It just not geek enough, and you need to be hardcore.
This technique shows a really fast way to get connected to your devices. It works best for SSH devices although it does, kind of support telnet, just not very well. You can now use the Windows Command Line to connect directly to a SSH host by using this syntax: putty.exe -ssh or you can use telnet putty.exe telnet://192.168.1.48/ You will need to spend some time learning the keyboard shortcuts that I talked about. Pretty quickly they will become second nature and you will have even more speed and confidence as you move around your network.
More options This really is only just the start of what can do with PuTTY, and there are lots more things. If you have a favorite then please using the contact form or put something in the comments and I would be pleased to add it or write it up. Other Posts in A Series On The Same Topic. (9th January 2011). (5th October 2009).
(21st September 2009). (20th September 2009). I’m a die hard putty user but my network has hundreds of systems that I have log into.
Putty connection manager is the way to go on this one. I created a database with that is laid out with folders that I can navigate through to find the box I need to connect to.
This is the antithesis of of what this article is all about. For my quick and dirty connection I use cygwin ssh. Works just like the linux version. And as for my Windoze laptop, good ol’ kermit to the rescue. It also does zterm transfers for copying up IOS images, that is if you don’t have the thumb-drive available. I will agree here. I have to connect to a possible couple of hundred devices across the fleet.
Putty will not do and neither will the command line. PuttyCM is the best thing since sliced bread. Also a comment to Greg, that OS in your screenshots is almost 12 years old. I know you’re not a Windows guy but Windows 7 is a whole lot more productive than XP. You could’ve just pressed the start menu key on your keyboard once (or clicked it), typed in the word ‘putty’ and pressed enter and it would’ve launched.
Even if it wasn’t even installed and the exe was lying around somewhere on the HDD, and without any environment variables. Man, I wish I would have realized earlier, this is kind of just a silly way of running putty. I expected to be able to Run putty.inside. console2 or cmd prompt. Not all is lost however, as I did go get puTTy finally, and I happened to read the part about plink. Plink no one wants to use puTTy’s ugly interface do they? So I don’t look like so much of a dick, to the people seeing this in the future.
Oh yeah “Hi” ?. @ Joe Smith: Or you could use Visor with Terminal.app, set terminal to launch at startup, assign ^ + ` to bring down the terminal, and alias all of your ssh sessions. Then you press ^ + `, type the name of your server, press enter, and you’re done. Or you could use Quicksilver to assign scripts to ssh into your servers, and launch those scripts through Quicksilver. Both remove the mouse entirely, as this article was attempting.
When on Windows you could simply use Cygwin, which allows you to use OpenSSH client and daemon, and gives you a bash environment to boot. You could also use AutoHotKey to minimize typing even further, using either this article’s method or Cygwin. When on Linux there are too many options to name. (Though I wish I liked any of the Visor alternatives on Linux.) You could switch to another virtual terminal and set up aliases.
You could use your DE’s launch mechanism. You could use AwesomeWM and barely have to use the mouse to do anything. Brian Long says. First: you don’t want clicking Start/Programs/Accesories/Notepad?
Use the new Start menu, it will show the last used programs. Set it to show 20, small icons and that will cover most of your work. Second: want even less clicking? Using the keyboard, perhaps? Windows has built in a useful feature: you can create a shortcut on the Start Menu or the Desktop and set a hotkey combination to it.
You could go to Notepad on the Start Menu, open it’s properties, and set a hotkey like Ctrl+Alt+N, easy to use and remember. Third: Ctrl+Esc? Too much typing, buy a new keyboard and use the Winkey. You open the start menu to open the Run Dialog? You can make it a whole lot quicker just pressing Win+R. Or try with F, E, D too and use the damn internet to seek more useful keys, dude.
Fiddling with paths? That’s archaic. If you like typing put all your used shorcuts on the Command starting path (usually C:Documents and settingsUser) type the first letters and press tab until it appears. Yes, DOS has autocomplete.
If you reinstal Windows you just need to copy all the.lnk to the new computer, no typing of paths needed. All this ranting and the “technique” is full of flaws xD Ps: can that be called technique?. ktulu789 says. I was looking for a way to run Putty with a single command besides /m commands.bat.
I have an AutoIt Script to shut down the entire server network. On some I use Windows Shutdown command, on other domains I use PSshutdown, on a couple of devices like NAS and the like: Putty SSH and Linux PowerOff command. And on the virtual machines and appliances on ESXi also PowerOff command. I want to set a different shutdown delay for guests and hosts like guestA now guestB 60 sec guestC 120 sec HostX 200 sec guest1 now guest2 60 Host# 130 -m for running a batch is great, but it is just one line,/command. I just find that having lots of Commands.txt, Commandsb.txt, looks dirty.
Is there any way to just go: PuTTY -ssh guestA -u -pw -mno poweroff now PuTTY -ssh guestB -u -pw -mno poweroff 60? I just tought of setting parameters for the batch file like -m Commands.txt%1 But it ain’t a real batch file.
This may need quotes, how could PuTTY tell which are it’s commands and which are for the batch?. Gama Xul says.