Kali Linux Deep Dive Webinars
NC-Expert, in partnership with WLPC, has presented a Kali Linux Deep Dive at WLPC Phoenix and WLPC Prague.
Keith Parsons and Phil Morgan want to maximixe the learning potential for the attendees. Because of this, we are pleased to announce that NC-Expert will be running follow-up webinars which cover the content of the Kali Linux Deep Dives. These webinars will be recorded, and available on NC-Expert's video platform. The current plan is to cover the material over several webinar sessions. We also intend to record updated information as new technologies are released, and information added, to future Deep Dives.
Access to these webinars and recordings is only available to (past or future) attendees of the Kali Linux Deep Dive at WLPC. Attendees of WLPC Kali Linux 3-day Bootcamps will also be permitted access.
December 4, 2019 - 6:00PM (pacific) - Introduction
December 18, 2019 - 6:00PM (pacific) - Introduction to the Kit
December 23, 2019 - 6:00PM (pacific) - Kali Tools and Using Kali
January 22, 2020 - 6:00PM (pacific) - Pentesting and Wi-Fi (theory)
February 5, 2020 - 6:00PM (pacific) - Pentesting and Wi-Fi (practical)
February 12, 2020 - 6:00PM (pacific) - Pentesting with Scripted Attack Tools
Duration: approximately 1 hour per webinar
Email firstname.lastname@example.org to register to attend the webinars.
Further Study Resources Information
WLPC 2019 Prague
WLPC 2019 Phoenix
Email us, per the contact information from your Kali Linux BootCamp or DeepDive, for a set of comprehensive instructions.
These instructions are only available to Kali Linux BootCamp or DeepDive attendees (WLPC), or members of the Wireless LAN Association (WLA).
Under “what you need to do” follow "Step 2”. The model you need to configure for is G5.
Then when completed, follow “step 3”.
Now you need to reinstall Kali Linux on the ChromeBook. Refer to "Setting Up your Kali Laptop" section (above) for instructions.
There seems to be an issue where, if you close the screen on the Kali Laptop, it “forgets” that it is a Kali Laptop and not a ChromeBook.
This seems to be a problem with Chromebooks in general - especially if you install a different operating system on them. Basically, the NVRAM attribute that says “boot from USD/SD” is being lost.
I want to fix this, asap, but it is going to require some testing and some studying. I propose to fix this in three phases...
Phase 1 - Solution A
We already have a solution:
a) Follow the instructions under “Resetting your Kali Laptop Back to Chrome” (above)
b) Then follow the instructions under “Setting up Your Kali Laptop” (above)
Phase 2 - Solution B
Because Phase 1 - Solution A is quite time consuming and frustrating (requiring you to reinstall Kali), I have come up with Phase 2 - Solution B.
Basically, we follow a similar process to Phase 1 - Solution A, only we install Kali onto an SD card (min 32G).
This is the procedure:
a) Follow the instructions under "Resetting your Kali Laptop Back to Chrome"
b) Insert the SD card into the slot
c) Then follow the instructions under “Setting up Your Kali Laptop”. Only this time, choose the SD card as the repository for Kali Linux NOT the internal 32G drive
Now if the Kali Laptop fails again, you only have to:
a) Remove the SD card
b) Follow the instructions under “Resetting your Kali Laptop Back to Chrome“
c) Then follow the instructions under “Setting up Your Kali Laptop”. But only follow them until the end of installing “mrchromebox’s” hack. Once you reboot after this point, slip in the SD card, and select it to boot
This should radically speed up the recovery process, as you will no longer need to re-install Kali.
Phase 3- Solution C
This one is going to take time.
I want to experiment with other options of "mrchromebox’s" script, but it means I have to disassemble* the Chromebook, remove the write-protect screw, and then try the other options.
This may take a while… so keep checking back. I will update you once I have had a chance to play with this.
(...also I don’t want my Chromebook to run around shouting, “No disassemble Johnny 5!” LOL)