Tag Archives: PuTTY

How to Set the Window Title in PuTTY Tips, Tricks and Tutorials 07 JUL 2015

The free Telnet/SSH client PuTTY is an essential daily tool for me at work, what with all the Linux servers I routinely have to jump into and work on.

The default behaviour for PuTTY after logging into a server is for the terminal window’s title to be set by the server being communicated with – usually a combination of the currently logged in username and the server’s hostname or IP address.

A nice little trick however, if you want more human friendly window titles to work with (i.e., so you don’t get confused by the 10 open clients you have at any one time), is to force the Window Title to something you define – you know, like the actual project name that the server hosts.

To do this is pretty simple.

First, load the session whose window title you want to set. Click on the Terminal->Features menu item on the left and tick (enable) “Disable remote-controlled window title changing”. Next, go to the Window->Behaviour menu item and then enter your desired window title in the “Window title” field.

Go back to the session window and save your changes.

As easy as that! :)

writing on glass

Related Link: http://www.chiark.greenend.org.uk/~sgtatham/putty/

How to Export PuTTY Saved Sessions CodeUnit 11 FEB 2013

If you are a developer and you make use of the Windows operating system, then you will undoubtedly be more than just a little familiar with the fantastic PuTTY telnet/ssh client written and maintained by Simon Tatham.

I manage a fair number of servers over SSH and it is always a problem when I change my primary work machine as there isn’t a simple way to transfer all of your Saved Sessions over to the new machine.

Or rather, there isn’t any obvious way of doing it.

Turns out that exporting your Saved Sessions is a matter of registry manipulation, as the software saves everything over there. This makes it a simple task of exporting all the relevant keys using Window’s standard regedit utility and then importing them on the new PC.

To achieve, fire up a command prompt and enter:

regedit /e "%userprofile%\Desktop\putty-registry-export.reg" HKEY_CURRENT_USER\Software\Simontatham

This will generate a .reg file on your desktop which you can then move across to your new machine. Once there, you can either restore using regedit and the /s switch, or simply right-click on the file and select the top “Merge” option.


How to Enable SSH Remote Access on a New Ubuntu Server 10.10 Install CodeUnit 08 APR 2011

Being able to administer your Ubuntu servers remotely is one of the most important aspects when running your own server environment, which makes the extremely useful OpenSSH server package an almost critical part of your system after install.

Because it is not installed by default (though the option does form part of the installer process), it is pretty simple to enable afterwards.

Once you have finished your install and logged in, update your apt-get sources by entering:

sudo apt-get update

(If you don’t do this and try installing openssh-server directly, you’ll most likely encounter a “openssh-server has no install candidate” error. Try it for yourself if you don’t believe me)

Once this has completed updating your packages, install the OpenSSH server onto your system with:

sudo apt-get install openssh-server


You may want to further configure SSH access on your system (like change the default port for added security for example), which can be done by editing the config file at /etc/ssh/sshd_config and make the required changes (disabling root logins is also always a good idea).

Note, you can check if SSH has been installed and is running by running the following PS check:

ps -aef | grep sshd


Linux ls Colour-coding in PuTTY CodeUnit 05 NOV 2009

PuTTY is a damn useful app for when it comes to gaining remote access into a machine via SSH or Telnet, and has more than proven its worth to serious geeks over the years since it was first released.

But here’s a question that you’ll be asking if you are new to the whole command line SSH into Linux access thing:

“Just what does all the colour-coding (when it comes to folder listings) displayed in PuTTY mean?”

Well, basically the colour-coding is to expediate file type recognition. For example, the default colour set is as follows (thanks Google!):

  • * Normal file: White (or the default colour used by the command line window)
  • * Directory: Blue
  • * Symbolic link: Cyan
  • * Pipe: Yellow
  • * Socket: Magenta
  • * Block device driver: Bold yellow foreground, with black background
  • * Character device driver: Bold yellow foreground, with black background
  • * Orphaned syminks: Blinking Bold white, with red background
  • * Missing links: Blinking Bold white, with red background
  • * Archives or compressed files: Red (e.g. .tar, .gz, .zip, .rpm)
  • * Image files: Magenta (.jpg, gif, bmp, png, tif)

To manipulate or view just what colours your system is spitting out you, simply pay a visit to /etc/profile.d/colors.sh and /etc/profile.d/colors.csh

There, hope that helps! :)

(Tip: If you wish to disable the list colouring, simply remove the alias that attaches ls –color=tty to ls – run `alias` to see what I’m referring to.)