Last active
August 13, 2021 17:30
-
-
Save da667/9610bf9f39aa5906f2d5c13e136911b7 to your computer and use it in GitHub Desktop.
SSH config file for Building Virtual Machine Labs Chapter 15: Routing and Remote Access for Hosted Hypervisors
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Host siem | |
Hostname 172.16.1.3 | |
User ayy | |
Host ips | |
HostName 172.16.1.4 | |
User ayy | |
Host kali | |
HostName 172.16.2.2 | |
User ayy |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a sample
~/.ssh/config
file for students reading Building Virtual Machine Labs, specifically, chapter 15 -- Routing and Remote Access for Hosted Hypervisors. This SSH config file assumes that you are using the default subnet assignments (e.g. 172.16.1.0/24 and 172.16.2.0/24), and that the user created during OS install for all three VMs isayy
.If you need to adjust the IP address for the IPS, SIEM, or Kali virtual machines, modify the
HostName
field as necessary. Likewise modify theUser
field to reflect the name of the user you wish to log in as over SSH as necessary.To install this file on Linux or OSX, run the following commands:
ls -al ~/.ssh
if the output of this command indicates that the .ssh directory doesn't exist:
mkdir ~/.ssh
chmod 700 ~/.ssh
Finally, copy this file to the .ssh directory
cp config ~/.ssh/config
chmod 600 ~/.ssh/config
Test to ensure the config file is set up properly by running the following commands:
ssh siem
ssh ips
ssh kali
After running each of these commands, students will be prompted for the password of the specified user on each VM. Once you enter the password, confirm you are logged on to the correct virtual machine.
"I already have a
~/.ssh/config
file. Wat do?"cp ~/.ssh/config ~/.ssh/config.old
cat config >> ~/.ssh/config
These commands will back up the existing ssh config file, and append the content from the sample config file to the existing config file. if problems occur, the command
cp ~/.ssh/config.old ~/.ssh/config
can be used to restore the backed up ssh config