Differences between revisions 12 and 38 (spanning 26 versions)
⇤ ← Revision 12 as of 2017-01-25 03:45:33 →
Size: 3378
Editor: scot
Comment:
← Revision 38 as of 2021-02-02 23:36:23 → ⇥
Size: 4472
Editor: scot
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= More Firewall rules and VNC access to your Kali Linux = = Lab 03 - More Firewall rules and Remote access to your VMs =
Line 5: Line 5:
 1. First we are going to setup your Kali linux to allow SSH and VNC - your final goal is to show a VNC login from your Windows 10 Box.  1. Setup rdp backdoors to your windows machines on pfsense using NAT
 1. Setup ssh keys on github and use them to access your ubuntu, and kali machines. Again, setup backdoors using NAT
 1. Setup xrdp for kali (that way you can access it without having to use the SCVMM tool.
Line 7: Line 9:
 1. Explore the metasploitable box and see what ports are open on it. This will involve a bit of work relating to nmap. Goal is to list all open ports and the common programs that run on those ports.
Line 16: Line 16:
 1. Install the openssh-server on kali (you know how, I shouldn't have to tell you)
 1. Make sure the service always starts on a reboot (ditto here, hint update-rc.d)		  1. Install the openssh-server on kali (you know how, I shouldn't have to tell you), it should already be installed on your ubuntu server.
 1. Create a public key private key pair and post your public key on git hub (see: https://help.github.com/articles/connecting-to-github-with-ssh/. Once you have your public key posted on github others can access it via: "github.com/username.keys" You can use that to your advantage when installing the keys. I use wget to get the keys from github when I need them.
 1. Make sure the open ssh service always starts on a reboot of kali (ditto here, hint systemctl enable ssh)
Line 20: Line 21:
    1. Now you should be able to login from your Windows 10 machine (using putty, did you install that yet?) and sudo su|bash or whatever you want to use to become root! And you don't ever need that crazy IE for this either.
 1. Now that you are root, why not take this opportunity to update|upgrade your system.
    1. This is not as easy as it may sound. You should know to do a apt-get update, apt-get upgrade, apt-get dist-upgrade, and now full-upgrade. BUT THIS MAY NOT WORK HERE! Why? Because you are installing software that will set off all sorts of alarms in most security suites. 		    1. Now you should be able to login from your Ubuntu Windows and sudo su|bash or whatever you want to use to become root! And you don't ever need that crazy GUI for this either.
 1. Now that you are root, take this opportunity to update|upgrade your systems.
    1. This is not as easy as it may sound for kali. You should know to do a apt-get update, apt-get upgrade, apt-get dist-upgrade, and now full-upgrade. BUT THIS MAY NOT WORK HERE! Why? Because you are installing software that will set off all sorts of alarms in most security suites. So you may have trouble with your kali update.
Line 24: Line 25:
 1. Make sure you have updated your Windows 10, and Windows 2016 machines too.  1. Make sure you have updated your Windows machine(s) too.
Line 26: Line 27:
    1. Update all machines except metasploitable 3.     1. Update all machines except metasploitable 3.
       * Hint if you your having trouble with pfSense, try the following:
         1. Check the networking
         2. Login to pfSense and do an upgrade from the commandline. # sudo pfSense-upgrade -d
Line 28: Line 32:
 1. Finally, I want to have a remote desktop ability to Kali 2. (e.g. VNC). However there seems to be problems with VNC and Gnome 3.
    1. It is not necessary to remove Gnome 3, we'll just install mate side-by-side {{{# apt-get install mate}}} ([[https://forums.kali.org/showthread.php?26704-Kali-2-0-vncserver-grey-window-sad-computer|kali forums]])
    1. Change the default to boot to the terminal instead of into Gnome 3:
       * To switch from GUI to CLI: {{{# systemctl set-default multi-user.target}}} I did this from the CLI.
       * To switch from CLI to GUI: {{{# systemctl set-default graphical.target}}} (This is just in case, we will leave it in CLI mode)
    1. Change which GUI you are using with: {{{# update-alternatives --config x-session-manager}}} to change to mate.
    1. From the command line {{{# vncserver -localhost no -geometry 1024x768}}}
    1. Download a VNC client to your windows 10 machine and login to: 192.168.1.4::5901
    1. Todo: have the vncserver survive a reboot.
  1. Install xrdp on kali (I'm assuming your ubuntu we already has this).
 1. Install NAT rules to allow you to ssh into your linux machines and rdp into your windows machines (if you haven't already done this). You can use any port you like to forward to your internal machines (which should all have static IPs of course)
Line 41: Line 37:
 1. Show me that no updates are needed on any of your computers!
 1. Show me that you can login to kali via ssh and VNC.		  1. Show me that you can login to each of the following machines from the lab network and that you have installed all updates except on Metasploitable 3!
    1. Window Server
    1. Kali
    1. Ubuntu 18.04
 1. Show me that you can login to kali via ssh and rdp.
 1. Show me that you can rdp into your Ubuntu VM directly from outside your firewall (yes this is a back door)
 1. Show me that you can ssh into your linux machines using your public key from outside your firewall (yes these are back doors)

= 2019 Example screen shots =

== Showing Ubuntu ==

Here is an example of what I did for my ubuntu. First I setup a reserved IP for the ubuntu system.

{{attachment:screen3.png}}

Then I setup a NAT rule and firewall rule to allow port 2222 to be forwarded to my ubuntu machine on port 22.

{{attachment:screen2.png}}

Then I can login from an ubuntu prompt on my system at home:

{{attachment:screen1.png}}

== Showing for Windows ==

I installed Windows 2019 server (not the desktop experience version).

From powershell, I had to do several things - see WindowsAdministration/PowerShellScripts#Setting_up_a_Windows_2019_Server_for_the_first_time

When you are done, it should show the following:

{{attachment:screen4.png}}

You could do this for both windows systems if you like.

Lab 03 - More Firewall rules and Remote access to your VMs

Goal

  1. Setup rdp backdoors to your windows machines on pfsense using NAT
  2. Setup ssh keys on github and use them to access your ubuntu, and kali machines. Again, setup backdoors using NAT
  3. Setup xrdp for kali (that way you can access it without having to use the SCVMM tool.

  4. Understand Firewall rules and how they are processed on pfSense

Lab Guide

There will be a lecture and demo of firewall rules.

First we are going to setup

  1. Install the openssh-server on kali (you know how, I shouldn't have to tell you), it should already be installed on your ubuntu server.

  2. Create a public key private key pair and post your public key on git hub (see: https://help.github.com/articles/connecting-to-github-with-ssh/. Once you have your public key posted on github others can access it via: "github.com/username.keys" You can use that to your advantage when installing the keys. I use wget to get the keys from github when I need them.

  3. Make sure the open ssh service always starts on a reboot of kali (ditto here, hint systemctl enable ssh)
    1. Can you login over ssh with root? Ok, then add yourself
    2. Don't forget to add yourself to the right group (hint: usermod will do that for you).
    3. Now you should be able to login from your Ubuntu Windows and sudo su|bash or whatever you want to use to become root! And you don't ever need that crazy GUI for this either.
  4. Now that you are root, take this opportunity to update|upgrade your systems.
    1. This is not as easy as it may sound for kali. You should know to do a apt-get update, apt-get upgrade, apt-get dist-upgrade, and now full-upgrade. BUT THIS MAY NOT WORK HERE! Why? Because you are installing software that will set off all sorts of alarms in most security suites. So you may have trouble with your kali update.
    2. Solution? I had to use a SOCKS proxy to end around this. You all should collaborate to see if you can find a solution. I've given you a hint, here is another. There are only a couple of .deb files that will fail so you could just download them through another means (again, the means I used was a SOCKS proxy).
  5. Make sure you have updated your Windows machine(s) too.
  6. Since the most important step in security is to make sure your machines are up-to-date...
    1. Update all machines except metasploitable 3.
      • Hint if you your having trouble with pfSense, try the following:
        1. Check the networking
        2. Login to pfSense and do an upgrade from the commandline. # sudo pfSense-upgrade -d
    2. Make sure that all machines will continue to update on a regular bases.
  7. Install xrdp on kali (I'm assuming your ubuntu we already has this).
  8. Install NAT rules to allow you to ssh into your linux machines and rdp into your windows machines (if you haven't already done this). You can use any port you like to forward to your internal machines (which should all have static IPs of course)

Show me

  1. Show me that you can login to each of the following machines from the lab network and that you have installed all updates except on Metasploitable 3!
    1. Window Server
    2. Kali
    3. Ubuntu 18.04
  2. Show me that you can login to kali via ssh and rdp.
  3. Show me that you can rdp into your Ubuntu VM directly from outside your firewall (yes this is a back door)
  4. Show me that you can ssh into your linux machines using your public key from outside your firewall (yes these are back doors)

2019 Example screen shots

Showing Ubuntu

Here is an example of what I did for my ubuntu. First I setup a reserved IP for the ubuntu system.

screen3.png

Then I setup a NAT rule and firewall rule to allow port 2222 to be forwarded to my ubuntu machine on port 22.

screen2.png

Then I can login from an ubuntu prompt on my system at home:

screen1.png

Showing for Windows

I installed Windows 2019 server (not the desktop experience version).

From powershell, I had to do several things - see WindowsAdministration/PowerShellScripts#Setting_up_a_Windows_2019_Server_for_the_first_time

When you are done, it should show the following:

screen4.png

You could do this for both windows systems if you like.

NetworkSecurity/Lab/Lab03 (last edited 2021-02-04 19:53:15 by scot)