Articles tagged ‘ssh’

For me as a Linux^w user I always had to type long lines to start my SSH^w sessions. It’s no rocket science, you know, but for he who types thousands of characters each day, each character save is golden.

We usally start our SSH sessions by typing the following command string:

ssh user@domain.tld

I’ve tried to shorten this by adding the domain and its TLD^w to my hosts file with a shorter alias like

hname hostname.tld

But obviously that crashed against Apache^w Vhost^w capability, the request never make it to the other end.

I personally have SSH keys on some of my servers to avoid typing passwords, that is good to prevent against MITM^w attacks and keyloggers, but I still have to type the string mentioned lines above.

Then, with 3 lines in a SSH’s configuration file on my home directory (yes, you don’t need to alter the server’s SSH configuration file and yes, you can do that on your shared hosting’s shell account).
Read the full article

For every *nix/BSD user, there was no life before SSH and even the crappy Windows plataform got a client (thank god).

But I’ve personally ran into many bad experiences that Google helped me solve.

So, here are my advices for logging into SSH to a linux machine:

1. Change your Terminal Emulation to “linux”: Connection-> Data -> Terminal-Type String = linux
2. Change your escape sequence to “Linux”: Terminal -> Keyboad -> “The Function Keys and Keypad” -> Linux
3. Set the terminal to UTF-8: Window -> Translation -> “Character set translation on received data” -> UTF-8

That’s it, if someone has other tips envolving PuTTY SSH Client, please share at the comments!