Why SSH connection basics in Linux CLI? - Purpose & Use Cases

The Big Idea

What if you could control any computer from anywhere, safely and instantly?

The Scenario

Imagine you need to access your work computer from home to fix a problem or check files. Without SSH, you might have to physically be at the computer or use complicated, unsafe methods to connect remotely.

The Problem

Manually accessing a remote computer can be slow and risky. You might share passwords insecurely, make typing mistakes, or expose your data to hackers. It's like leaving your front door unlocked or giving out your house keys to strangers.

The Solution

SSH lets you connect safely and easily to another computer over the internet. It creates a secure tunnel, like a secret passage, so you can control the remote computer as if you were sitting right there, without risking your data or passwords.

Before vs After

✗ Before

telnet remote-computer
login: user
password: 1234

✓ After

ssh user@remote-computer

What It Enables

SSH makes secure remote control of computers simple, fast, and safe, opening doors to managing servers, fixing issues, and working from anywhere.

Real Life Example

A system administrator uses SSH to update software on a server located in another city without leaving their desk, saving hours of travel and ensuring the server stays secure.

Key Takeaways

Manual remote access is slow and unsafe.

SSH creates a secure, encrypted connection.

It enables easy and safe remote computer control.

Practice

1. What does the command ssh user@hostname do?

easy

A. Lists files on the remote computer.

B. Copies files from the remote computer to local.

C. Starts a secure connection to the remote computer as 'user'.

D. Deletes the user account on the remote computer.

Solution

1. Step 1: Understand the ssh command purpose

   The ssh command is used to securely connect to another computer over a network.

2. Step 2: Analyze the syntax ssh user@hostname

   This syntax means connect as 'user' to the computer identified by 'hostname'.

3. Final Answer:

   Starts a secure connection to the remote computer as 'user'. -> Option C

4. Quick Check:

   ssh user@hostname = Secure connection [OK]

Hint: ssh user@host means connect securely as user [OK]

Common Mistakes:

• Thinking ssh copies files instead of connecting
• Confusing ssh with file listing commands
• Assuming ssh deletes accounts

2. Which of these is the correct syntax to connect to a remote server with ssh?

easy

A. ssh user@hostname

B. ssh -connect user hostname

C. ssh connect user@hostname

D. ssh user hostname

Solution

1. Step 1: Recall ssh command syntax

   The correct syntax is ssh user@hostname without extra words or flags for basic connection.

2. Step 2: Check each option

   Options A, B, and D have incorrect syntax or missing '@' sign.

3. Final Answer:

   ssh user@hostname -> Option A

4. Quick Check:

   Correct ssh syntax = ssh user@hostname [OK]

Hint: ssh always uses user@hostname format [OK]

Common Mistakes:

• Adding extra words like 'connect' in command
• Omitting '@' between user and hostname
• Using flags incorrectly for basic ssh

3. What will happen if you run ssh alice@192.168.1.10 and the password is correct?

medium

A. You will see a list of files on your local computer.

B. The remote computer will shut down.

C. Your local files will be deleted.

D. You will be logged into the remote computer as user alice.

Solution

1. Step 1: Understand ssh login process

   Running ssh with user and IP tries to connect and log in to that remote machine.

2. Step 2: Check what happens on correct password

   If password is correct, you get a command prompt on the remote machine as that user.

3. Final Answer:

   You will be logged into the remote computer as user alice. -> Option D

4. Quick Check:

   ssh + correct password = remote login [OK]

Hint: Correct password means remote login success [OK]

Common Mistakes:

• Thinking ssh shuts down remote machine
• Confusing ssh with file deletion
• Assuming ssh lists local files

4. You try to connect with ssh [e-mail] but get the error: Permission denied (publickey). What is the likely problem?

medium

A. You typed the wrong hostname.

B. Your SSH key is missing or not accepted by the server.

C. The server is turned off.

D. You forgot to install ssh on your computer.

Solution

1. Step 1: Understand the error message

   "Permission denied (publickey)" means the server expects an SSH key for authentication but did not accept yours.

2. Step 2: Identify cause of error

   This usually means your SSH key is missing, not loaded, or not authorized on the server.

3. Final Answer:

   Your SSH key is missing or not accepted by the server. -> Option B

4. Quick Check:

   Permission denied (publickey) = SSH key issue [OK]

Hint: Permission denied (publickey) means SSH key problem [OK]

Common Mistakes:

• Assuming hostname typo causes this error
• Thinking server power state causes this error
• Believing ssh must be installed locally to connect

5. You want to connect to a remote server at example.com as user admin but the server uses a non-standard port 2222. Which command will connect correctly?

hard

A. ssh -p 2222 [e-mail]

B. ssh [e-mail]:2222

C. ssh [e-mail] -port 2222

D. ssh [e-mail]

Solution

1. Step 1: Recall how to specify a port in ssh

   The correct flag to specify a port is -p followed by the port number.

2. Step 2: Analyze each option

   ssh -p 2222 [e-mail] uses -p 2222 correctly. Options A, C, and D use incorrect syntax or wrong placement.

3. Final Answer:

   ssh -p 2222 [e-mail] -> Option A

4. Quick Check:

   Use -p to specify port in ssh [OK]

Hint: Use ssh -p port user@host for custom ports [OK]

Common Mistakes:

• Putting port after hostname with colon
• Using -port instead of -p
• Changing hostname to include port number