Navnath Mantra
Martta
You also need a device with an unlocked bootloader, for flashing the kernel, and you must be able to get root on the device. Root is needed so we can write applications to system, such as busybox and bootkali, and execute commands that allow us to get Kali running.
If your device is older, please check to make sure your kernel version is 3.4+ and above. With the switch to kali rolling we are starting to see errors inside chroot where the kernel is not able to support loading Kali.
Another good resource is usually XDA forums as someone else might have already built a working kernel and they must provide the sources under GPL. Most kernel development pages on XDA must provide a link to their sources.
You also need a device with an unlocked bootloader, for flashing the kernel, and you must be able to get root on the device. Root is needed so we can write applications to system, such as busybox and bootkali, and execute commands that allow us to get Kali running.
You can find multiple example config files available in local.config.examples.If your device is older, please check to make sure your kernel version is 3.4+ and above. With the switch to kali rolling we are starting to see errors inside chroot where the kernel is not able to support loading Kali.
Another good resource is usually XDA forums as someone else might have already built a working kernel and they must provide the sources under GPL. Most kernel development pages on XDA must provide a link to their sources.
[Optional step] You can find multiple example config files available in local.config.examples.
If you find something that matches your device, copy it to kali-nethunter-kernel named as local.config (Make sure to then edit it to check that everything matches your kernel!)
If the build was successful, add your device details like codename, boot_block, slot_device, etc with 8. Edit Anykernel config
Create your first test kernel installer with 6. Create Anykernel zip and then flash your kernel to see it in action.
Make sure that the local.config file that you used has everything properly configured
Know exactly what errored out by looking for what went wrong to search it on google
Look if there is any patch inside 4. Apply Nethunter kernel patches that addresses the same error and patch it if it does
If none of the above works, then it would be best to go back and forth between viewing build.sh script and Porting nethunter to try and manually fix the issue.
Kali NetHunter is available for un-rooted devices (NetHunter Rootless), for rooted devices that have a custom recovery (NetHunter Lite), and for rooted devices with custom recovery for which a NetHunter specific kernel is available (NetHunter).
Both rooted editions provide additional tools & services.A custom kernel can extend that functionality by adding additional network and USB gadget drivers as well as wifi injection support for selected wifi chips.
NetHunter Lite can be installed on all Android devices that are rooted and have a custom recovery.The full NetHunter experience requires a devices specific kernel that has been purpose built for Kali NetHunter.The NetHunter GitLab repository contains over 164 kernels for over 65 devices. Kali Linux publishes over 25 images for the most popular devices on the NetHunter download page.The following live reports are generated automatically by GitLab CI:
Once the zip file has downloaded, verify the SHA256 sum of the NetHunter zip image against the values on the download page. If the SHA256 sums do not match, do not attempt to continue with the installation procedure.
Those of you who want to build a NetHunter image from our Gitlab repository may do so using our Python build scripts. Check out our Building NetHunter page for more information.You can find additional instructions on using the NetHunter installer builder or adding your own device in the README located in the nethunter-installer git directory.
I'd love, along with Debian and Ubuntu, to have Kali selectable as distribution option - linux kernel, dtb, headers, u-boot, overlays and armbian-config would be the perfect base for it (and every other distribution imho)
Being inspired by GoVanguard/karmbian, which is based on armbian's previous framework, I tried grossly "injecting" kali support into armbian branch v24.02 - but I'm lost; definitely no developer, just playing around
I think orange pi boards are nice and hold potential, but manufacturer is stuck at an old forked armbian framework, old kernel and hacky dtbs - Armbian is great and I hope to get kali tools on it without "Frankensteining" Debian with overlapping repos, conflicts and pinnings
Would love to get some proper support - sunxi64-current (6.6) works a charm, injection patches are ok, but even when deployed on trixie and using a kali extension script, the are overlapping packages - It would be great to have Kali distro just integrated in this framework
Hi @going, thanks for following up!
Kali is the de-facto (in my opinion) penetration-testing and learning platform (I'm passionate about wireless) - orangepi boards are very decent hardware-wise but software support is lacking
I enjoyed learning and playing around with armbian for the past 3 days, and I think it's the best framework for building self-contained small distros
I'm looking towards a clean, lean, cli distro for my SBCs, kali is a great platform and Armbian with its framework works better than the patched-up google-drive solutions from vendor (kernel 6.1 vs kernel 6.6)
Being a debian derivative (kali), I see the potential of converging armbian cleanliness with kali - especially since with older framework GoVanguard did it for some boards, and orangepi itself is based on a previous generation of armbian
As of now, for running kali, I'm bound to RaspberryPI boards, as are the only ones with broad "mainline" kali coverage - in full honesty though I think armbian is a much superior framework than kali-arm for building
I like a lot mainline support and armbian brought mainline support for both u-boot and kernel on orangepizero3 - I want to try and come up with a board config for orangepizero2w on armbian as soon as I find a kali solution!
Specifically Kali has a lot of metapackages provididing wireless tools, metasploit and windows powershell toolkits and so on; it's specialized in offensive/defensive security; an assortment difficult to find elsewhere without major efforts
Kali is in a lot of ways a polished SID with all of their own custom bits added. It can be debootstrap'd just like Debian, Devuan and Ubuntu. I did find some services didn't work on boot; 'ssh avahi bluetooth ntp'. But there could be some option they have I'm not aware of to allow those services to start out of the box. Creating a custom service to start those does the trick though.
As far as patched for hacking wireless drivers or/and kernel tweaks, we should have most of them, probably more then Kali Linux. In technical sense there are just userspace applications, which are IMO included into that extension. The rest, majority, about Kali is myth, produced by Hollywood and community.
@Igor I get your point, Kali is mostly userspace and the convenience to have everything packaged (and rolling) in the same place - the only thing Armbian lacked was wifi injection capabilities which I solved by placing kali kernel patches in
As you can see there are Armbian packages being overriden by Kali's counterpart: how may I know there's no "Frankestein" effect under the hood? I'd feel much safer knowing that Kali packages have been bootstrapped during image build itself - If I select "Bookworm" with "kali-extension.sh", the list gets much longer
@c0rnelius Kali network services, especially avahi being able to broadcast services, thus giving away a penetration tester "presence", are disabled by default - in the past HCIUART was disabled by default too due to some reason I can't remember; nevertheless everything can be (re-)enabled, unmasked, etc by standard means - Kali does even include some fancy cryptroot-luks kernel patches that automatically "destroy" data on boot when full-disk-encryption is active in case of specific passwords being passed (like a dead man's switch I suppose)
Ive tried a couple of times but it comes up with a blank screen every time
Give it a go yourself, i cleaned up the guide clockwork pi has made for making your own images compatible, there are links to the original too if needed
This code repository offers downloads for the latest images of various uConsole models, along with kernel patches, firmware for the keyboard and 4G expansion module, hardware schematics, assembly i...
Yh the process is long, but there is instructions on how to start it. Everything you need is in the specified core once you go into the patchs folder. But yh im still a little confused on how it all works though. Might have to look at it again in the future.
Kali Linux Release History We release fresh images of Kali Linux every few months as a result of accumulative fixes, major security updates, installer updates, etc.Please see bugs.kali.org/changelog_page.php for the most up-to-date log of...
Find many great new & used options and get the best deals for Male to Female Micro TF SD Memory Card Adapter Extender Test Kit Extension Tool at the best online prices at eBay! Free delivery for many products.
I burned the image on the sd card and it shows the rainbow image then it loads something but it never made it to the desktop. I don't use the SD reader on the pi because for some reason it doesn't boot kali but when I use the SD as a usb it "boots". I am stuck on a screen that it recognises usb ports, mouse and keyboard but doesn't show the desktop
I had issues installing Kali to the USB too. I didn't have an SD card and so I had to fix it without one. It was getting stuck at the rainbow screen because it couldn't find the boot files. I fixed the issue by modifying cmdline.txt to point to my USB device partitions. I also had to change /etc/fstab to point to my USB device partitions. I've written a detailed guide here:How to install Kali Linux on a USB for the RaspberryPi?
You wrote you have a brand new Pi b+ so it's very likely it is a Raspberry Pi 3B+. This need updated firmware and drivers and it is known that other distributions than Raspbian haven't supported it very quick. You can look about this issue at Why am I getting a rainbow screen and flashing red PWR LED with a new Raspberry Pi 3B+?.
Using first Raspbian and then putting kali linux back on will not help because the firmware/drivers are part of the image. Raspbian has two partitions. The first partition is the boot partition and is formated as fat