CSEC_PUBLIC/How-To-Secure-A-Linux-Server
1
0
Fork 0
mirror of https://github.com/imthenachoman/How-To-Secure-A-Linux-Server.git synced 2025-12-06 09:12:47 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #75 from YesterKo/master

Browse Source 
Fixed typo in README.md
This commit is contained in:
IMTheNachoMan
2021-11-20 14:06:11 -05:00
committed by GitHub
parent 777a61d3a1 63bb8e4719
commit c58d6e04dc
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -24,7 +24,7 @@ An evolving how-to guide for securing a Linux server that, hopefully, also teach
- [Pre/Post Installation Requirements](#prepost-installation-requirements) - [Pre/Post Installation Requirements](#prepost-installation-requirements)
- [Other Important Notes](#other-important-notes) - [Other Important Notes](#other-important-notes)
- [The SSH Server](#the-ssh-server) - [The SSH Server](#the-ssh-server)
- [Important Not Before You Make SSH Changes](#important-not-before-you-make-ssh-changes) - [Important Note Before You Make SSH Changes](#important-note-before-you-make-ssh-changes)
- [SSH Public/Private Keys](#ssh-publicprivate-keys) - [SSH Public/Private Keys](#ssh-publicprivate-keys)
- [Create SSH Group For AllowGroups](#create-ssh-group-for-allowgroups) - [Create SSH Group For AllowGroups](#create-ssh-group-for-allowgroups)
- [Secure `/etc/ssh/sshd_config`](#secure-etcsshsshd_config) - [Secure `/etc/ssh/sshd_config`](#secure-etcsshsshd_config)
@@ -271,7 +271,7 @@ Where applicable, use the expert install option so you have tighter control of w
## The SSH Server ## The SSH Server
### Important Not Before You Make SSH Changes ### Important Note Before You Make SSH Changes
It is highly advised you keep a 2nd terminal open to your server **before you make and apply SSH configuration changes**. This way if you lock yourself out of your 1st terminal session, you still have one sesssion connected so you can fix it. It is highly advised you keep a 2nd terminal open to your server **before you make and apply SSH configuration changes**. This way if you lock yourself out of your 1st terminal session, you still have one sesssion connected so you can fix it.