One of our goals when developing Kali Linux was to provide multiple metapackages that would allow us to easily install subsets of tools based on their particular needs. Until recently, we only had a handful of these meta packages but we have since expanded the metapackage list to include far more options.
After several weeks of “back and forth” with the Amazon EC2 team, Kali Linux has finally been approved into the Amazon EC2 marketplace. This means that our users can now activate and access Kali Linux instances in the Amazon cloud quickly and easily. We are “selling” these images on the marketplace for free, so other than the regular amazon charges, there no extras to pay. We have currently published a single 64 bit minimal instance of Kali Linux, which can be found in the marketplace by searching for “Kali Linux” or accessed via its direct link.
Kali Linux contains a large number of very useful tools that are beneficial to information security professionals. One set of such tools belongs to the Pass-the-Hash toolkit, which includes favorites such as pth-winexe among others, already packaged in Kali Linux. An example of easy command line access using pth-winexe is shown below.
There’s been a fair amount of discussion around the recently introduced LUKS nuke patch we added to the cryptsetup package in Kali Linux. We wanted to take this opportunity to better explain this feature, as well as demonstrate some useful approaches which are worthwhile getting to know.
It’s been a while since our last minor release which makes 1.0.6 a more significant update than usual. With a new 3.12 kernel, a LUKS nuke feature, new Kali ARM build scripts, and Kali AMAZON AMI and Google Compute image generation scripts, not to mention numerous tool additions and updates – this release is really heavily laden with goodness. For more information about what’s new in this release, check the Kali changelog.
A couple of days ago one of us had the idea of adding a “nuke” option to our Kali install. In other words, having a boot password that would destroy, rather than decrypt the data on our drive. A few Google searches later, we found an old cryptsetup patch by Juergen Pabel which does just that – adds a “nuke” password to cryptsetup, which when used, deletes all keyslots and makes the data on the drive inacessible. We ported this patch for a recent version of cryptsetup, and posted it on github.