Just a quick update to the 2020.1 release we put out last month. We made some major changes to the installers, and some people had a few issues with some of the images we released. So, we made some slight alternations to smooth things out and make the install process easier for everyone.
Before, we used to release multiple separate installers for different Desktop Environments (DE). With 2020.1 we changed how we distributed our base images, without having multiple different ISOs for each DE, by introducing a “installer” image as well as a “live” image.
Both accomplish the same thing, but how they do it is different. The “installer” image is the new one, as this uses “debian-cd” on the back-end. We noticed a bug in a dependency chain, which caused an issue with x11. As a result, you may not have got a graphical interface after installing Kali. As a result, we pushed out a fix (2020.1a) to address this.
Note: If you are already running 2020.1, you do not need to reinstall. The 2020.1a release is only for those who weren’t able to successfully install 2020.1
We have also pushed out an updated image, both 32-bit and 64-bit for Raspberry Pi, due to some files being corrupt in the initial image.
Since the introduction of a non-root user, we have switched the default user to be
kali. We also moved the vagrant image to this user as well. However, we reverted it back to
vagrant to be more in line with their best practices.
Not long after this fix, we have received a contribution to fix a bug that would occur if you defined an additional network inteface in the Vagrantfile.
You can find both of those fixes in the latest version of the Vagrant box (2020.1.2).
Thanks to everyone who reported an issue on the bug tracker (Sorry, twitter doesn’t count). Keep them coming so we can make 2020.2 even stronger! If you have read this far, we are aiming for a Tuesday in May for its release.