Remotely manage Linux servers, start with SSH
Linux servers often require remote management during operation and maintenance. SSH is one of the most commonly used remote management tools. It allows administrators to log in to Linux servers remotely, execute commands and manipulate files. In this article, we will discuss how to use SSH to connect to a Linux server and share some practical tips for SSH.
As a system administrator, you plan to use OpenSSH on Linux to automate daily tasks, such as file transfers, backup database dump files to another server, etc. To achieve this, you need to be able to automatically log in to Host B from Host A. Automatic login means using ssh in a shell script without entering any password.

This article will tell you how to set up SSH password-free login on CentOS/RHEL. Once auto-login is configured, you can use it to move files using SSH (Secure Shell) and Secure Copy (SCP).
SSH is open source and the most reliable network protocol for remote login. System administrators use it to execute commands and transfer files to another computer over the network via the SCP protocol.
By configuring SSH password-free login, you can enjoy the following conveniences:
◆Use scripts to automate daily work.
◆Enhance the security of Linux servers. This is a recommended way to protect your Virtual Private Server (VPS) from brute force attacks, as SSH keys are nearly unbreakable by brute force alone.
What is Ssh-Keygen
ssh-keygen is a tool used to generate, create and manage public and private keys for SSH authentication. Through the ssh-keygen command, users can create keys that support both SSH1 and SSH2 protocols. ssh-keygen creates RSA keys for the SSH1 protocol, which can be RSA or DSA for SSH2.
What is Ssh-Copy-Id
ssh-copy-id is a script command used to copy the local public key to the remote authorized_keys file. It will also append the identity file to the ~/.ssh/authorized_keys file of the remote machine and send it to the remote host. appropriate permissions for the user's home directory.
SSH Key
SSH keys provide a better and secure mechanism for logging into Linux servers. After running ssh-keygen, a public and private key pair will be generated. You can place the public key on any server and use it to unlock when connecting to the server from a client holding the private key. When the two match, the system can be unlocked without a password.
Set up password-free login SSH on CentOS and RHEL
The following steps have been tested on CentOS 5/6/7, RHEL 5/6/7 and Oracle Linux 6/7.
Node 1: 192.168.0.9 Node 2: 192.168.0.10
Directory structure of this chapter
- step one :
- Step 2:
- Step 3:
- Step 4:
step one :
Test the connection and access from node 1 to node 2:
[root@node1 ~]# ssh root@192.168.0.10 The authenticity of host '192.168.0.10 (192.168.0.10)' can't be established. RSA key fingerprint is 6d:8f:63:9b:3b:63:e1:72:b3:06:a4:e4:f4:37:21:42. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.0.10' (RSA) to the list of known hosts. root@192.168.0.10's password: Last login: Thu Dec 10 22:04:55 2015 from 192.168.0.1 [root@node2 ~]#
Step 2:
Use the ssh-key-gen command to generate the public key and private key. It should be noted here that the private key can be encrypted to enhance security.
[root@node1 ~]# ssh-keygen Generating public/private rsa key pair. Enter file in which to save the key (/root/.ssh/id_rsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /root/.ssh/id_rsa. Your public key has been saved in /root/.ssh/id_rsa.pub. The key fingerprint is: b4:51:7e:1e:52:61:cd:fb:b2:98:4b:ad:a1:8b:31:6d root@node1.ehowstuff.local The key's randomart image is: +--[ RSA 2048]----+ | . ++ | | o o o | | o o o . | | . o + .. | | S . . | | . .. .| | o E oo.o | | = ooo. | | . o.o. | +-----------------+
Step 3:
Use the ssh-copy-id command to copy or upload the public key to the remote host, and append the identity file to ~/.ssh/authorized_keys on node 2:
[root@node1 ~]# ssh-copy-id -i ~/.ssh/id_rsa.pub 192.168.0.10 root@192.168.0.10's password: Now try logging into the machine, with "ssh '192.168.0.10'", and check in: .ssh/authorized_keys to make sure we haven't added extra keys that you weren't expecting.
Step 4:
Verify password-free SSH login to node 2:
[root@node1 ~]# ssh root@192.168.0.10 Last login: Sun Dec 13 14:03:20 2015 from www.ehowstuff.local
To summarize, SSH is a very important remote management tool in Linux systems. It can provide a safe and efficient remote access method. When using SSH, pay attention to strengthening security measures, such as using public key authentication, and setting reasonable configuration parameters. At the same time, we also shared some practical SSH tips, such as using proxies, forwarding ports, etc., which can help us better manage Linux servers. I believe these contents will be helpful to Linux operation and maintenance personnel.
The above is the detailed content of Remotely manage Linux servers, start with SSH. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



The key differences between CentOS and Ubuntu are: origin (CentOS originates from Red Hat, for enterprises; Ubuntu originates from Debian, for individuals), package management (CentOS uses yum, focusing on stability; Ubuntu uses apt, for high update frequency), support cycle (CentOS provides 10 years of support, Ubuntu provides 5 years of LTS support), community support (CentOS focuses on stability, Ubuntu provides a wide range of tutorials and documents), uses (CentOS is biased towards servers, Ubuntu is suitable for servers and desktops), other differences include installation simplicity (CentOS is thin)

CentOS has been discontinued, alternatives include: 1. Rocky Linux (best compatibility); 2. AlmaLinux (compatible with CentOS); 3. Ubuntu Server (configuration required); 4. Red Hat Enterprise Linux (commercial version, paid license); 5. Oracle Linux (compatible with CentOS and RHEL). When migrating, considerations are: compatibility, availability, support, cost, and community support.

CentOS installation steps: Download the ISO image and burn bootable media; boot and select the installation source; select the language and keyboard layout; configure the network; partition the hard disk; set the system clock; create the root user; select the software package; start the installation; restart and boot from the hard disk after the installation is completed.

How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

Docker uses Linux kernel features to provide an efficient and isolated application running environment. Its working principle is as follows: 1. The mirror is used as a read-only template, which contains everything you need to run the application; 2. The Union File System (UnionFS) stacks multiple file systems, only storing the differences, saving space and speeding up; 3. The daemon manages the mirrors and containers, and the client uses them for interaction; 4. Namespaces and cgroups implement container isolation and resource limitations; 5. Multiple network modes support container interconnection. Only by understanding these core concepts can you better utilize Docker.

Docker process viewing method: 1. Docker CLI command: docker ps; 2. Systemd CLI command: systemctl status docker; 3. Docker Compose CLI command: docker-compose ps; 4. Process Explorer (Windows); 5. /proc directory (Linux).

VS Code system requirements: Operating system: Windows 10 and above, macOS 10.12 and above, Linux distribution processor: minimum 1.6 GHz, recommended 2.0 GHz and above memory: minimum 512 MB, recommended 4 GB and above storage space: minimum 250 MB, recommended 1 GB and above other requirements: stable network connection, Xorg/Wayland (Linux)

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.
