Sunday, November 22, 2026
TR
Linux

How to Use SSH to Connect to a Remote Server

How to Use SSH to Connect to a Remote Server
Contents
  1. How Does SSH Work?
  2. How to Configure SSH
  3. How to Log In to SSH with Keys
  4. How Does Key-Based Authentication Work?
  5. How to Create SSH Keys
  6. How to Transfer Your Public Key to the Server
  7. Client-Side Options
  8. Disabling Password Authentication

To connect to a remote system using SSH, we will use the sshcommand.

If you are using Windows, to be able to use sshfrom a terminal you need to install a version of OpenSSH. If you prefer to work in PowerShell, you can follow Microsoft's documentation to add OpenSSH to PowerShell. If you prefer to have a full Linux environment, you can install WSL, the Windows Subsystem for Linux, which will include it by default. Finally, as a lightweight third option, you can install Git for Windows, which provides a native Windows bash terminal environment that includes the ssh command. Each of these is well supported, and whichever you decide to use will come down to your preference.

If you are using a Mac or Linux, the ssh command will already be available in your terminal.

The simplest form of the command is:

ssh remote_host

In this remote_host example, it is the IP address or domain name that you are trying to connect to.

This command assumes that your username on the remote system is the same as your username on your local system.

If your username is different on the remote system, you can specify it using this syntax:

ssh remote_username@remote_host

Once you connect to the server, you may be asked to verify your identity by providing a password. Later, we will cover how to generate keys to use instead of passwords.

To exit the ssh session and return to your local shell session, type:

exit

How Does SSH Work?

SSH works by connecting a client program to an ssh server called sshd.

In the previous section, the ssh client program was used. The ssh server was already running on the remote_host server we specified .

On almost all Linux environments, the sshd server should start automatically. If it is not running for any reason, you may need to temporarily access your server through a web-based console or a local serial console.

The process required to start an ssh server depends on the Linux distribution you are using.

On Ubuntu, you can start the ssh server by typing:

sudo systemctl start ssh

This should start the sshd server, and you can then log in remotely.

How to Configure SSH

When you change the SSH configuration, you are changing the settings of the sshd server.

On Ubuntu, the main sshd configuration file is /etc/ssh/sshd_config.

Back up the current version of this file before editing it:

sudo cp /etc/ssh/sshd_config{,.bak}

Open it using nano or your favorite text editor :

sudo nano /etc/ssh/sshd_config

You will want to leave most of the options in this file alone. However, there are a few you may want to look at: /etc/ssh/sshd_config

Port 22

The port declaration specifies which port the sshd server will listen on for connections. By default, this is 22. You should probably leave this setting alone unless you have specific reasons to do otherwise. If you do change your port, we will show you later how to connect to the new port. /etc/ssh/sshd_config

HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key

The host key declarations specify where to look for global host keys. We will discuss what a host key is later. /etc/ssh/sshd_config

SyslogFacility AUTH
LogLevel INFO

These two items indicate the level of logging that should occur.

If you are having trouble with SSH, increasing the amount of logging can be a good way to discover what the problem is. /etc/ssh/sshd_config

LoginGraceTime 120
PermitRootLogin yes
StrictModes yes

These parameters specify some login information.

LoginGraceTime specifies how many seconds to keep the connection alive without a successful login.

It can be a good idea to set this to a slightly higher value than the time it normally takes you to log in.

PermitRootLogin selects whether the root user is allowed to log in .

In most cases, this should be changed to no once you have created a user account that has access to elevated privileges (through suor sudo) and can log in through ssh, in order to minimize the risk of anyone gaining root access to your server.

strictModes is a safety guard that will refuse a login attempt if the authentication files are readable by everyone.

This prevents login attempts when the configuration files are not secure. /etc/ssh/sshd_config

X11Forwarding yes
X11DisplayOffset 10

These parameters configure an ability called X11 Forwarding . This allows you to view the graphical user interface (GUI) of a remote system on your local system.

This option must be enabled on the server and given with the SSH client during connection with the -X option.

After you have made your changes, save and close the file. If you are using nano, press Ctrl+X, then Y when prompted, and then Enter.

If you changed any settings in /etc/ssh/sshd_config, make sure you reload your sshd server to apply your changes:

sudo systemctl reload ssh

You should test your changes thoroughly to make sure they work the way you expect.

It can be a good idea to have a few terminal sessions open while you make changes. This allows you to roll back the configuration if necessary without locking yourself out.

How to Log In to SSH with Keys

While being able to log in to a remote system using passwords is useful, it is faster and more secure to set up key-based authentication .

How Does Key-Based Authentication Work?

Key-based authentication works by creating a pair of keys: a private key and a public key .

The private key is located on the client machine and is secured and kept secret.

The public key can be given to anyone or placed on any server you want to access.

When you try to connect using a key pair, the server uses the public key to create a message for the client computer that can only be read with the private key.

The client computer then sends the appropriate response back to the server, and the server will know that the client is legitimate.

This process is performed automatically once you have configured your keys.

How to Create SSH Keys

SSH keys should be generated on the computer you wish to log in from. This is usually your local machine.

Enter the following at the command line:

ssh-keygen -t rsa

You may be asked to set a passphrase on the key files, but this is a fairly uncommon practice, and you should press enter at the prompts to accept the defaults. Your keys will be created at ~/.ssh/id_rsa.pub and ~/.ssh/id_rsa .

Change into the .ssh directory by typing :

cd ~/.ssh

Look at the permissions of the files:

ls -l
Output-rw-r--r-- 1 demo demo  807 Sep  9 22:15 authorized_keys
-rw------- 1 demo demo 1679 Sep  9 23:13 id_rsa
-rw-r--r-- 1 demo demo  396 Sep  9 23:13 id_rsa.pub

As you can see, the id_rsafile is readable and writable only by the owner. This helps it remain secret.

However, the id_rsa.pub file can be shared and has the appropriate permissions for this activity.

How to Transfer Your Public Key to the Server

If you currently have password-based access to a server, you can copy your public key to the server by issuing this command:

ssh-copy-id remote_host

This will start an SSH session. After you enter your password, it will copy your public key to the server's authorized keys file, which will allow you to log in without a password next time.

Client-Side Options

There are a number of optional flags that you can provide when connecting over SSH.

Some of these may be necessary to match the settings in the remote host's sshdconfiguration.

For example, if you changed the port number in your sshdconfiguration, you need to match that port on the client side by typing:

ssh -p port_number remote_host

Note: changing your ssh port is a reasonable way of providing security through obscurity . If you allow ssh connections to a widely known server deployment on port 22 as normal, and you have password authentication enabled, you will likely be attacked by many automated login attempts. Using only key-based authentication and running ssh on a non-standard port is not the most sophisticated security solution you can implement, but it should minimize these.

If you want to execute just a single command on a remote system, you can specify it after the host like this:

ssh remote_host command_to_run

You will connect to the remote machine, authenticate, and the command will be executed.

As we said before, if X11 forwarding is enabled on both computers, you can access this functionality by typing:

ssh -X remote_host

Provided you have the appropriate tools on your computer, GUI programs that you use on the remote system will now open their windows on your local system.

Disabling Password Authentication

If you have created SSH keys, you can increase your server's security by disabling password-only authentication. Apart from the console, the only way to log in to your server will be with the private key that matches the public key you installed on the server.

Warning: Before proceeding with this step, make sure you have installed a public key on your server. Otherwise, you will lock yourself out!

As root or a user with sudo privileges, open the sshd configuration file:

sudo nano /etc/ssh/sshd_config

Find the line that reads Password Authenticationand uncomment it by removing the # at the beginning of the line. You can then change its value to no: /etc/ssh/sshd_config

PasswordAuthentication no

Two more settings that should not need to be changed (unless you have modified this file before) are PubkeyAuthenticationand ChallengeResponseAuthentication. They are set by default and should read as follows: /etc/ssh/sshd_config

PubkeyAuthentication yes
ChallengeResponseAuthentication no

After you have made your changes, save and close the file.

You can now reload the SSH daemon:

sudo systemctl reload ssh

Password authentication should now be disabled, and your server should be accessible only through SSH key authentication.

Kerim Koç

Systems and infrastructure engineer. I write about Linux, open source, high availability and security.