fix formatting
This commit is contained in:
parent
7ab7d6e84d
commit
2b6e6a23e8
183
README.md
183
README.md
@ -141,111 +141,112 @@ Coming Soons
|
|||||||
<!-- HARDENING -->
|
<!-- HARDENING -->
|
||||||
## Hardening
|
## Hardening
|
||||||
|
|
||||||
## Creating a SSH Key
|
## Creating a SSH Key
|
||||||
**Windows:**
|
**Windows:**
|
||||||
|
|
||||||
1. Open the Settings panel, then click Apps.
|
1. Open the Settings panel, then click Apps.
|
||||||
2. Under the Apps and Features heading, click Optional Features.<br>
|
2. Under the Apps and Features heading, click Optional Features.<br>
|
||||||
|
|
||||||
|
|
||||||
3. Scroll down the list to see if OpenSSH Client is listed.<br>
|
3. Scroll down the list to see if OpenSSH Client is listed.<br>
|
||||||
|
|
||||||
* If it’s not, click the plus-sign next to Add a feature. <br>
|
* If it’s not, click the plus-sign next to Add a feature. <br>
|
||||||
* Scroll through the list to find and select OpenSSH Client.<br>
|
* Scroll through the list to find and select OpenSSH Client.<br>
|
||||||
* Finally, click Install.
|
* Finally, click Install.
|
||||||
|
|
||||||
4. Open Command Prompt.<br>
|
4. Open Command Prompt.
|
||||||
|
1) Press the Windows key.
|
||||||
1) Press the Windows key.
|
2) Type `cmd`.
|
||||||
2) Type `cmd`.
|
3) Under *Best Match*, right-click Command Prompt.
|
||||||
3) Under *Best Match*, right-click Command Prompt.
|
4) Click Run as Administrator
|
||||||
4) Click Run as Administrator
|
|
||||||
|
|
||||||
5. If prompted, click **Yes** in the *Do you want to allow this app to make changes to your device?* pop-up.
|
|
||||||
|
|
||||||
6. Use OpenSSH to Generate an SSH Key Pair
|
5. If prompted, click **Yes** in the *Do you want to allow this app to make changes to your device?* pop-up.
|
||||||
1) In the command prompt, type the following:
|
|
||||||
```sh
|
|
||||||
ssh-keygen
|
|
||||||
```
|
|
||||||
|
|
||||||
2) By default, the system will save the keys to C:\Users\your_username/.ssh/id_rsa. You can use the default name, or you can choose more descriptive names. This can help distinguish between keys, if you are using multiple key pairs. To stick to the default option, press Enter.
|
|
||||||
3) You’ll be asked to enter a passphrase. Hit Enter to skip this step.
|
|
||||||
4) The system will generate the key pair, and display the key fingerprint and a randomart image.
|
|
||||||
5) Open your file browser.
|
|
||||||
6) Navigate to C:\Users\your_username/.ssh.
|
|
||||||
7) You should see two files. The identification is saved in the id_rsa file and the public key is labeled id_rsa.pub. This is your SSH key pair.
|
|
||||||
|
|
||||||
**Linux:**
|
6. Use OpenSSH to Generate an SSH Key Pair
|
||||||
|
1) In the command prompt, type the following:
|
||||||
|
```sh
|
||||||
|
ssh-keygen
|
||||||
|
```
|
||||||
|
|
||||||
|
2) By default, the system will save the keys to C:\Users\your_username/.ssh/id_rsa. You can use the default name, or you can choose more descriptive names. This can help distinguish between keys, if you are using multiple key pairs. To stick to the default option, press Enter.
|
||||||
|
3) You’ll be asked to enter a passphrase. Hit Enter to skip this step.
|
||||||
|
4) The system will generate the key pair, and display the key fingerprint and a randomart image.
|
||||||
|
5) Open your file browser.
|
||||||
|
6) Navigate to C:\Users\your_username/.ssh.
|
||||||
|
7) You should see two files. The identification is saved in the id_rsa file and the public key is labeled id_rsa.pub. This is your SSH key pair.
|
||||||
|
|
||||||
**MacOS:**
|
**Linux:**
|
||||||
|
|
||||||
### Adding SSH Public Key
|
**MacOS:**
|
||||||
Replace $SSH with the content of the public key.
|
|
||||||
```sh
|
|
||||||
echo "$SSH" >> ~/.ssh/authorized_keys
|
|
||||||
```
|
|
||||||
### SSH Permissions
|
|
||||||
```sh
|
|
||||||
mkdir -p ~/.ssh
|
|
||||||
touch ~/.ssh/authorized_keys
|
|
||||||
chmod 700 ~/.ssh
|
|
||||||
chmod 600 ~/.ssh/authorized_keys
|
|
||||||
```
|
|
||||||
### Disabling password based SSH
|
|
||||||
```sh
|
|
||||||
cd /etc/ssh
|
|
||||||
sed -i 's/#PasswordAuthentication yes/PasswordAuthentication no/g' sshd_config
|
|
||||||
systemctl restart sshd
|
|
||||||
```
|
|
||||||
### Allow user to SUDO without password
|
|
||||||
|
|
||||||
```sh
|
### Adding SSH Public Key
|
||||||
sudo su -
|
Replace $SSH with the content of the public key.
|
||||||
visudo
|
```sh
|
||||||
```
|
echo "$SSH" >> ~/.ssh/authorized_keys
|
||||||
Press `Insert` on keyboard, substitute `$USER` with the user you created during installation.
|
```
|
||||||
```sh
|
### SSH Permissions
|
||||||
$USER ALL=(ALL) NOPASSWD: ALL
|
```sh
|
||||||
```
|
mkdir -p ~/.ssh
|
||||||
### Working with fapolicyd
|
touch ~/.ssh/authorized_keys
|
||||||
fapolicyd starts in protection mode. We need to set fapolicyd to permissive mode to allow us to build the necessary rule sets for our individual systems.
|
chmod 700 ~/.ssh
|
||||||
```sh
|
chmod 600 ~/.ssh/authorized_keys
|
||||||
cd /etc/fapolicyd/
|
```
|
||||||
sed -i 's/permissive = 0/permissive = 1/g' fapolicyd.conf
|
### Disabling password based SSH
|
||||||
systemctl restart fapolicyd
|
```sh
|
||||||
```
|
cd /etc/ssh
|
||||||
See <a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/assembly_blocking-and-allowing-applications-using-fapolicyd_security-hardening">RHEL: Blocking and Allowing applications with fapolicyd</a> for more information on building rules.
|
sed -i 's/#PasswordAuthentication yes/PasswordAuthentication no/g' sshd_config
|
||||||
|
systemctl restart sshd
|
||||||
|
```
|
||||||
|
### Allow user to SUDO without password
|
||||||
|
|
||||||
### Fixing wget
|
```sh
|
||||||
As of current GnuTLS is not properly working with FIPS. To correct this we tell GnuTLS to disable health checks.
|
sudo su -
|
||||||
|
visudo
|
||||||
|
```
|
||||||
|
Press `Insert` on keyboard, substitute `$USER` with the user you created during installation.
|
||||||
|
```sh
|
||||||
|
$USER ALL=(ALL) NOPASSWD: ALL
|
||||||
|
```
|
||||||
|
### Working with fapolicyd
|
||||||
|
fapolicyd starts in protection mode. We need to set fapolicyd to permissive mode to allow us to build the necessary rule sets for our individual systems.
|
||||||
|
```sh
|
||||||
|
cd /etc/fapolicyd/
|
||||||
|
sed -i 's/permissive = 0/permissive = 1/g' fapolicyd.conf
|
||||||
|
systemctl restart fapolicyd
|
||||||
|
```
|
||||||
|
See <a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/assembly_blocking-and-allowing-applications-using-fapolicyd_security-hardening">RHEL: Blocking and Allowing applications with fapolicyd</a> for more information on building rules.
|
||||||
|
|
||||||
```sh
|
### Fixing wget
|
||||||
export GNUTLS_SKIP_FIPS_INTEGRITY_CHECKS=1
|
As of current GnuTLS is not properly working with FIPS. To correct this we tell GnuTLS to disable health checks.
|
||||||
|
|
||||||
# Lets make is persistant
|
```sh
|
||||||
cd /etc/profile.d/
|
export GNUTLS_SKIP_FIPS_INTEGRITY_CHECKS=1
|
||||||
touch gnutls.sh
|
|
||||||
echo "export GNUTLS_SKIP_FIPS_INTEGRITY_CHECKS=1" > gnutls.sh
|
|
||||||
```
|
|
||||||
`wget` will now function as intended.
|
|
||||||
<p align="right">(<a href="#top">back to top</a>)</p>
|
|
||||||
|
|
||||||
<!-- CLOUD -->
|
# Lets make is persistant
|
||||||
## Optional Cloud Configurations:
|
cd /etc/profile.d/
|
||||||
`cloud-init`: Cloud images are operating system templates and every instance starts out as an identical clone of every other instance. It is the user data that gives every cloud instance its personality and cloud-init is the tool that applies user data to your instances automatically.
|
touch gnutls.sh
|
||||||
```sh
|
echo "export GNUTLS_SKIP_FIPS_INTEGRITY_CHECKS=1" > gnutls.sh
|
||||||
dnf install -y cloud-init
|
```
|
||||||
```
|
`wget` will now function as intended.
|
||||||
|
<p align="right">(<a href="#top">back to top</a>)</p>
|
||||||
|
|
||||||
`cloud-utils-growpart`: Provides the growpart script for growing a partition. It is primarily used in cloud images in conjunction with the dracut-modules-growroot package to grow the root partition on first boot.
|
<!-- CLOUD -->
|
||||||
```sh
|
## Optional Cloud Configurations:
|
||||||
dnf install -y cloud-utils-growpart
|
`cloud-init`: Cloud images are operating system templates and every instance starts out as an identical clone of every other instance. It is the user data that gives every cloud instance its personality and cloud-init is the tool that applies user data to your instances automatically.
|
||||||
```
|
```sh
|
||||||
`gdisk`: GDISK command is used to partition the drives of your system. Works with cloud-init for partition resizing.
|
dnf install -y cloud-init
|
||||||
```sh
|
```
|
||||||
dnf install -y gdisk
|
|
||||||
```
|
`cloud-utils-growpart`: Provides the growpart script for growing a partition. It is primarily used in cloud images in conjunction with the dracut-modules-growroot package to grow the root partition on first boot.
|
||||||
|
```sh
|
||||||
|
dnf install -y cloud-utils-growpart
|
||||||
|
```
|
||||||
|
`gdisk`: GDISK command is used to partition the drives of your system. Works with cloud-init for partition resizing.
|
||||||
|
```sh
|
||||||
|
dnf install -y gdisk
|
||||||
|
```
|
||||||
|
|
||||||
<!-- LICENSE -->
|
<!-- LICENSE -->
|
||||||
## License:
|
## License:
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user