Kali linux windows server

//
//

Note: This post has been updated on 10/01/2014 (dd/mm/yyyy) to reflect the changes of Kali Linux 1.0.6 and the fix for the bug 575 I’ve submitted (ext4 file system issues with Hyper-V).

Greetings everyone,

Backtrack was a wonderful Pentest distro, you already should be aware that Backtrack R3 was the last release and it became deprecated. Kali Linux is the new Pentest distro from the same team, more details about the changes between BackTrack and Kali Linux go here:

http://www.kali.org/news/kali-linux-whats-new/

Following the blog post How to Install BackTrack 5 R3 on Hyper-V 3.0 – Windows Server 2012 and Window 8 it is about time to come up with Kali Linux installation process on Hyper-V, as said on my previous post and as the same as Backtrack, installing Kali on VMware or Vbox is a no brainer and you can either download a pre-installed VMware VM, doing the installation on Hyper-V has some special considerations which I will cover in detail here.

You may ask, why do I care with Hyper-V. The world is changing and Hyper-V became the most reliable Hypervisor in the market since Windows 8 and Windows Server 2012, comparing feature by feature with VMWare some features are almost equal, some others are better and there’s a few that are a way too much better (almost double the specs). Windows 8.1 and Windows Server 2012 R2 are already RTM and I am running them on my environments, I can tell you that if Hyper-V was already a top technology, on the new OS versions it became even better, if you are running Windows it’s a free ride so worth’s the try.

[Before you start]

– I will show you how to install Kali Linux on Hyper-V with LVM encryption partition to protect your data. There was a bug (see below bug 443) with LVM Encryption on Kali Linux that was fixed on the release 1.05, so make sure that you download the latest release or else you will be unable to boot your Machine without fixing GRUB.

http://bugs.kali.org/view.php?id=443

– Kali Linux installation process will configure by default the ext4 file system. If you are still using Kali 1.0.5 and below on ext4 file system the installation process of Kali Linux will hang while copying the OS installation files to the HDD, this was caused by a regression on the Storvsc driver that uses the method “WRITE_SAME” which is not supported on Hyper-V, the behavior is described on the following bug entry.
//
//
http://bugs.kali.org/view.php?id=223

There was a patch for the Storvsc driver that fixes this issue to Disable and blacklist the “WRITE_SAME” method: https://patchwork.kernel.org/patch/2172871/

During the Kali Linux 1.0.5 I’ve submitted the bug 575 which is now fixed on Kali Linux 1.0.6, you can see the details here:

http://bugs.kali.org/view.php?id=575

Hopefully this bug was brought to the attention of Kali’s team and now the ext4 file system is fully supported on Hyper-V.

For the purpose and success of this installation you need to download and install Kali Linux 1.0.6 and beyond, the installation is now reflecting the full compatibility of ext4 file system.

[Installation process]

1. Install the Hyper-V role on your machine, follow these links if you are not familiar yet with the process:

Windows Server 2008 R2 Hyper-V Getting Started Guide
http://technet.microsoft.com/en-us/library/cc732470(v=WS.10).aspx

Windows Server 2012 Install the Hyper-V Role and Configure a Virtual Machine
http://technet.microsoft.com/en-us/library/hh846766.aspx

2. Go to the Kali website Download section and download the Kali Linux ISO file 1.05 or higher. I prefer Kali Linux 64 bit  so this Wizard is focused on this distribution installation.

Kali Linux Download section:
http://www.kali.org/downloads/

3. On the Hyper-V Manager create a new Virtual Machine and Virtual Hard Disk:

On the right pane Click “New” –>Virtual Machine

On the New Virtual Machine Wizard –> Next

Define the Machine Machine Name and the location of the Virtual Machine configuration files

If your are running a Windows 8.1 or Windows Server 2012 R2 host Select the Virtual Machine “Generation 1”

Set the Memory size “2048” MB (depending on your needs, this is my setup memory)

Select your Internal or External Virtual Switch Network created on Step 3.

Create a Virtual Hard Disk (default: differential) with 30GB (depending on your needs)

Select “Install Operating System from a Boot CD/DVD” and Select the “image file (ISO)” downloaded on Step 2.

Review the VM configuration ao click “Finish” to complete the VM setup.

4. Start the Kali Linux Virtual Machine and from the Boot Menu select the “Graphical Install” option as shown in the pic

Картинка с сайта: luisrato.wordpress.com

5. On the Language screen select your preferred language, e.g. “English – English” and your Location, e.g. “Other –> Europe –> Portugal”

6. Select your Locals, e.g. “United States – en_US.UTF-8” and your Keyboard type, e.g. “Portuguese”

7. On the Network Configuration Screen select “ Configure Network Manually” (if you have a DHCP Server available on the same network you may use the automatic configuration, on my lab I’ll do a manual network config)

8. Define your IP address and network mask, e.g. “10.0.0.100/24” and your gateway, e.g. “10.0.0.254”

9. Configure your name server, e.g. “192.168.0.1” and your hosname, e.g. “kalim3r0”

10. Define the domain name, e.g. “lab.local”

11. Define the root user password

12. Configure the clock, e.g. “Lisbon”

13. On the Partition Disks setup window select “Guided – Use entire disk and set up encrypted LVM”

Select the appropriate partition disk and click continue, e.g. “SCSI 3 (0,0,0) (sda) – 32,2 GB Msft Virtual Disk”

14. On the Partition Disks partitioning window select “All files in one partition (recommended for new users)”, for the purpose of this demo this is the simplest option, you can define separate partitions for /home, /usr, /var, etc, etc

15. Confirm the Logical Volume Manager configuration, on “Write the changes to disks and configure LVM”  Select “Yes”

16. Define a Passphrase for the Encryption, don’t forget this passphrase because you will need to type it every time you boot up Kali Linux

17. On the Partition disks window with the Logical Volume Manager, partitions and mount point details, keep the default file system configuration (Kali 1.0.6 and above you can use ext4 file system) and click on the “Continue” button.

18. Confirm the changes and configuration of the Partition Disk on “Write the changes to disks” and select “Yes”

19. On the Configure the package manager window on “Use a network mirror” select “Yes”.

The intent of this process is to update the Kali Linux packages during the OS install, so make sure that you have Internet connectivity to accomplish this task

20. When you go ahead with the packages updates with the last step you may configure a proxy server ip address. For the purpose of this lab I have NAT and access to the internet, so I don’t need a proxy server and I will leave it blank

21. On the Install the Grub boot loader on a hard disk on “Install the GRUB boot loader to the master boot record?” select “Yes”

After GRUB boot loader installation the Kali Linux installation is complete and you should see the Finish Installation window, click on “Continue” to boot up Kali Linux

22. When you boot Kali Linux you will be prompted with the GRUB boot loader option and it will automatically boot in normal mode

23. After the boot you will be prompted for the Encryption Passphrase you defined on step 21

24. After
boot you will be prompted for credentials to Log in:

Username: root
Password: The password you defined on step 15

25. Finally you will have access to the so waited Kali Linux desktop

Картинка с сайта: luisrato.wordpress.com

[EXTRAS]
No matter if you are a Linux newbie or you had forgotten the appropriate syntax for some of the common Linux commands, here are some helpful terminal commands:

1. Define a new password

passwd

2. Configure network settings:

Temporary configuration (will disappear after reboot):

ifconfig
(to verify which network interface is available, possibly “eth0”)

Ifconfig eth0 10.0.0.100 netmask 255.255.255.0 up
route add default gw 10.0.0.254 eth0

Static configuration:

ifconfig
(to verify which network interface is available, possibly “eth0”)

sudo nano /etc/network/interfaces

On the appropriate interface line (e.g. confirmed in ifconfig “eth0″) edit and append as follow:

auto eth0
iface eth0 inet static
address 10.0.0.100
gateway 10.0.0.254
netmask 255.255.255.0
network 10.0.0.0
broadcast 10.0.0.255

Картинка с сайта: luisrato.wordpress.com

3 . Configure the DNS resolver

sudo nano /etc/resolv.conf

On the resolv.conf file insert the following entry:

nameserver 192.168.0.1
(IP of your nameserver)

4. Reload the new network configuration by restarting the network daemon

sudo /etc/init.d/networking restart

5. Download the list of the updated packages

apt-get update

6. Compare and update installed packages

apt-get upgrade

7. Install a new package

apt-get install <packagename>

R-Tape Loading error,
Luís Rato
//
//

Publicado em Hyper-V, Linux, Security
Etiquetas: Hyper-V, Linux, Pentesting, Security

When I first began familiar with WSL 1.0 , the network interfacing was simpler. But since WSL2 uses dynamic virtual IP address for each VM, now the things has got little trickier. Here, we will learn to install Postgres and MariaDB server and client in both Windows and WSL2 Linux and access them across the virtual Ethernet connection. By the term using interchangeably we mean accessing database in Windows from WSL2 Linux and vice versa.

PROBLEM STATEMENT: WSL2 IPv4 has access to PostgreSQL from localhost in Linux but not in Windows requires virtual ethernet adaptor’s assigned IP to communicate between each other and also other issue found was them requiring the firewall.

REQUIREMENTS: Database clients should be able to access database servers both in same OS and in other. WSL Client should access server in Windows and Windows clients should access database in WSL2.

To begin, one must need a good installation of Windows and WSL2 based distro in their machine.

Working with databases interchangeably

Картинка с сайта: dev.to

Source: https://dev.to/hymanzhan/setting-up-wsl-2-for-web-development-3202

Please be aware that you need to identify the IP address of the virtual machine (WSL) and the host machine you are working with, which might be different from the IP address of your local physical machine. You can find the IP address using Task Manager, and also using this command in WSL:

ip route # or

ip addr | grep eth0

You might also need to enable firewall on port 3306 for MariaDB and 5432 for Postgres for interconnectivity.

If you require port forwarding in WSL for reason, this article has it covered well. For Postgres vs MySQL comparison, you can check this blog from EDB, so you can choose the database system based on your need.

Database Servers

Database Servers in Windows

For Windows, you can get PostgreSQL from EDB and pgAdmin 4 from their download page. Simply install them and all add their bin directories to path folder if necessary.

For MariaDB, I recommend using XAMPP since it is robust and simple for beginners. But, if you like to install standalone version, you can download and install from official MariaDB site. You can use both MySQL Workbench and phpmyadmin to access such them as a client.

You must be able to access normally in Windows by psql and mysql commands.

Enabling/Disabling database servers in Windows is done through ‘Windows Services’. It can be accessed by entering service.msc in Windows Run (Win+R).

Database Servers in Linux

PostgreSQL Server in WSL

Most of the Linux distribution already have source for installing Postgres packages.

sudo apt update
sudo apt install postgresql postgresql-client postgresql-client-common postgresql-common postgresql-contrib -y
psql --version # to confirm installation
sudo service postgresql start # replace ending by stop to stop server, restart to restart server

sudo -u postgres psql # to access Postges via command line (both in Linux)

TIP: can check the status of your services in Linux using sudo service --status-all in the shell.

Картинка с сайта: dev.to

This is the expected output after proper installation.

To fix connection refused issue, here’s the workaround for it:

sudo -u postgres psql -c 'SHOW config_file' # to locate config file

Once you find the file, change the listen_addresses to * in postgresql.conf, the restart Postgres by sudo service postgresql restart command.

Also, update this in pg_hba.conf to allow remote auth from Windows host.

...
host  all       all       0.0.0.0/0            scram-sha-256
host  all       all       ::/0              scram-sha-256

This is a less recommended method (for security) you can try in case above methods still don’t let you connect in Windows:

#newline
host    all             all             all                     trust

Here’s the detail article if you like to dig deeper into this. Also, check this for better insights.

MariaDB Server in WSL

Here’s the command enough to setup MariaDB server in WSL:

sudo apt install mariadb-server
sudo service mariadb start
sudo mysql # to access the database CLI

To change port, edit the configuration file /etc/mysql/my.cnf that suits your needs.

This StackOverflow thread suggests to edit the file /etc/mysql/mariadb.conf.d/50-server.cnf, replace bind-address = 127.0.0.1 (localhost) by bind-address = 0.0.0.0 or * (all). After you restart the server by $ sudo service mariadb restart, you may be able to login your Linux database server in Windows client too with proper credentials (username, password) configuration.

Database Clients

Database Clients in Windows accessing database in both Windows & WSL

We need to enable firewall for both in and out bound in Windows (for working across). To access, we need to find IP of VM in which the database server is active, the we can get along by mentioning host, port, user and password from any database client. This process if enough for the well-configured server.

Here’s the sample psql command to log in for dev user, to avoid conflict:

psql -U dev -d postgres -h 192.168.176.181 -p 5432 # server host IP

In pgAdmin mention host IP address from ip route and add other credentials to access WSL based Postgres server.

Картинка с сайта: dev.to

To access MariaDB in Windows using XAMPP phpmyadmin, create a user in WSL MariaDB server (say wsl_user with no password) and grant ALL PRIVELEDGES. Now, you can go to login portal for phpmyadmin and find Debian in server version.

Here, mysql accesses the server in Windows in the first one, and in the second one, the server is natively installed within WSL. Therefore, both side accessed.

In phpMyAdmin, you also need to change its config.inc.php on $cfg['Servers'][$i]['auth_type'] = 'config'; to cookie to get login page.

Картинка с сайта: dev.to

Here’s a sample showing access in Command Line (Database server is in Windows):

Картинка с сайта: dev.to

Database Clients in WSL accessing database in both Windows and WSL

For psql in WSL to access Windows database, you need to find host IP (using ip route for example) and then hit the command below:

psql -h [HOST ADDRESS] -U [USER NAME]

Картинка с сайта: dev.to

For MariaDB client access, it is simple as mysql like mysql -u wsl_root -p -h 172.24.xxx.xxx:

Картинка с сайта: dev.to

To make things simpler, simply create new user and access through it:

CREATE USER 'wsl_root'@'localhost' IDENTIFIED BY 'password';
GRANT ALL PRIVILEGES ON *.* TO 'wsl_root'@'localhost' WITH GRANT OPTION;
CREATE USER 'wsl_root'@'%' IDENTIFIED BY 'password';
GRANT ALL PRIVILEGES ON *.* TO 'wsl_root'@'%' WITH GRANT OPTION;
FLUSH PRIVILEGES;

You can get more details in these blogs: https://dev.to/hymanzhan/setting-up-wsl-2-for-web-development-3202 and https://dev.to/qviper/connecting-mysql-server-in-windows-machine-from-wsl-4pf1

Tips

Complete Postgres removal

Here’s the solution in detail for the process:

• Remove Postgres from apt (or from other installation if any):

  sudo apt-get --purge remove postgresql postgresql-*

• Verify if packages are uninstalled:

  dpkg -l | grep postgres

Here’s the solution in detail for the process:

• Remove Postgres from apt (or from other installation if any):

  sudo apt-get --purge remove postgresql postgresql-*

• Verify if packages are uninstalled:

  dpkg -l | grep postgres

Here, you must find this to be empty. If not, remove them manually.

• Remove the configuration folders below:

  sudo rm -rf /var/lib/postgresql/
  sudo rm -rf /var/log/postgresql/
  sudo rm -rf /etc/postgresql/

• Finally, remove postgres user:

  sudo deluser postgres

Work-around for error in phpmyadmin

Grant all permissions to root and pma and remove password too:

CREATE USER 'pma'@'localhost' IDENTIFIED BY '';

SET PASSWORD FOR root@localhost='';

References

• https://docs.microsoft.com/en-us/windows/wsl/networking
• https://www.enterprisedb.com/postgres-tutorials/how-use-postgresql-django
• https://www.enterprisedb.com/blog/how-to-secure-postgresql-security-hardening-best-practices-checklist-tips-encryption-authentication-vulnerabilities
• https://www.enterprisedb.com/postgresql-tutorial-resources-training
• https://dev.to/hymanzhan/setting-up-wsl-2-for-web-development-3202#install-database-in-wsl
• https://stackoverflow.com/questions/56824788/how-to-connect-to-windows-postgres-database-from-wsl