One of the first practical things I needed to do when taking on this project, was to install Kali Linux. I have done this before, but this time I wanted to be able to work on Kali as a full version on my laptop – instead of using a virtual machine. I therefore ended up choosing the Kali Linux live feature, by booting it via a USB stick partitioned with Kali on it.
This might seem like a straightforward thing to do, but there were some issues along the way. Making sure the partition and formatting are correct is one thing, it is another making sure your computer can run it. When attempting to do a test run of this with the lab computers at Noroff, it got refused and stuck on the loading stage. On my laptop there were also some issues in regards to some BIOS-settings, but I overcame these quickly.
Since this was my first go with Kali Linux live, I did not stop to consider how a live system actually works! As you might assume, a live system does not store or retain any information or settings permanently, it just runs – and when it stops it is all back to how it was when you started out. I learned this the hard way after spending hours tweaking my Kali Linux settings to perfection and my own personal choices. Once I booted it again, all the changes and files I had there – were gone.
So by doing some more research I ended up having a go at Kali Linux Persistence. It allowed me to boot from the same image, but I had to create a second partition and do a whole complicated song and dance in the Kali settings. It took me some time to find the right recipe and perform it correctly, but in the end I were able to store changes and files/folders.
However, life in Linux land can be treacherous. I were going to do the standard update, upgrade and so on, but this time I decided to do it via the GUI panel in the Settings menu. Bad choice! Doing this with a clean install meant way too much data transfer and prompts, taking forever and in the end freezing and crashing. And by this happening whilst installing system critical modules – meant the whole system got corrupted.
After cleaning out the drive and doing the whole process again with partitioning, installing kali and doing the persistence- song and -dance, I were able to get Kali running with everything the way I want it. The research process so far has at least given me way more insight to what goes on behind the curtains on Kali Linux.