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 01:02:49 +01:00
Code Issues Packages Projects Releases Wiki Activity

Compare commits

base: CSEC_PUBLIC:73b8d04e7d60a6549be79782c43be2fa47af1670
Branches Tags
CSEC_PUBLIC:master
...
compare: CSEC_PUBLIC:80d50c0851ea5dcd236fcba439cd250681432191
Branches Tags
CSEC_PUBLIC:master

2 Commits
73b8d04e7d ... 80d50c0851

Author SHA1 Message Date
jxdv
80d50c0851 Merge c2f8f2e42d into f34170e867 2024-02-24 10:21:41 -08:00
IMTheNachoMan
f34170e867 Update README.md 
https://github.com/imthenachoman/How-To-Secure-A-Linux-Server/issues/115
 2024-02-24 09:03:02 -05:00
1 changed files with 3 additions and 0 deletions
Expand all files Collapse all files

3
README.md
View File

@@ -580,6 +580,9 @@ SSH is a door into your server. This is especially true if you are opening ports
# don't allow .rhosts or /etc/hosts.equiv # don't allow .rhosts or /etc/hosts.equiv
HostbasedAuthentication no HostbasedAuthentication no
# https://github.com/imthenachoman/How-To-Secure-A-Linux-Server/issues/115
HashKnownHosts yes
``` ```
1. Then **find and edit or add** these settings, and set values as per your requirements: 1. Then **find and edit or add** these settings, and set values as per your requirements: