Back from the Dead with Confluent Community Pain

So I am back from the dead!! I know I have not posted anything in a very long time.

So I decided to try to install Confluent’s Apache Kafka Community version on Ubuntu 18.04 server, and was it painful!!

Confluent, please look at your documentation on this as well as your packages, it is very broken with no existent users specified in service files !!

Anyway I created a gist detailing installation instructions for Confluent Community on ubuntu 18.04 server so that others don’t have to go through the same pain.

There will be more posts shortly…


Building a UsaBUSe – Part 1

So a while ago, I was watching some of the Defcon 24 videos and presentations, one of the ones that caught my eye was by a couple of guys at Sensepost, it was basically a USB device (arduino avr) that emulates devices and performs USB HID attacks coupled with an ESP8266 acting as a WI-FI bridge.

They used an $11 Cactus Micro Rev2 with some custom firmware to hack a windows 8.1 box.You can see more at their blog post on it here, there is also the code needed to build it on their github repo here.

So I started with a Ubuntu 14.04 LTS install and recvursively cloned the repository of the code.

Next you have to put the files from the releases section of the github repo in the following places shown in the pictures below:-

Create the firmware directory in esp-vnc and put user1.bin in it.


The file KeyboardMouseGeneric.hex in avr/KeyboardMouseGeneric


Program_ESP.hex in the Program_ESP directory


Lastly do the following in the root of the repo.

$ wget --content-disposition ""

$ unzip

To give you this:-

UsaBUSe files 1

Now you can plug in the Cactus and program the firmware for the ESP8266 and the arduino remembering to press the reset  button twice at the appropriate points. If all goes well, the output should be similar to below.

In part 2, we shall move onto functional testing and see how we go.





How to build Metasploitable 3

I haven’t blogged in a while for many reasons, but I hope to add some more posts during the next few months.

In this post, I will show you how to build the new Metasploitable VM from Rapid7.

I will build the virtual machine on Windows 10 on which I had previously installed virtualbox.

You need the following

The vagrant version is important as if you use a latter version, the build will fail.

Once you have the tools installed, make sure they are added to the system path. I stored mine in c:\users\<username>\temp.

You should now be able to execute them without specifying the whole path. Next, from an administrative command prompt install the vagrant reload command with the command ‘vagrant plugin install vagrant-reload

Once, you have the reload plugin installed, now head over to the Github Metasploitable3 repository at Download the zip file and extract it to a directory of your choosing.

Now change into the directory within your admin command prompt, enter the commands below to build the vm.

  1. packer build windows_2008_r2.json
  2. vagrant box add –name=metasploitable3
  3. vagrant up

The first command will take some time as it has to download the base vm. If all goes well you should have a nice new vm as shown below.







Digital Jersey Medical Hackathon

This my story of entering the Digital Jersey Medical Hackathon which took place over last weekend, now that I have recovered from lack of sleep.

The Concept

To build a low cost open source messaging platform using a Raspberry Pi, MQTT broker and a custom version of Android with a web app to monitor air quality. The name of the project was called “Health Stage”

Friday Night

I got to Digital Jersey  early on friday evening to setup, I choose one of the side rooms as it has a wall mounted TV with a good sized desk. As you can see, I had quite a bit of equipment with me for the build.


At 20:00 hours, the hackathon started, so I started my build of Android whilst soldering the pcb daughter board for the Raspberry Pi. By just after 11:00, the pcb was soldered, so next came polarity checking to make sure it was all good.

Yeah, we have a powered board that did not go bang!!!

Working Board

So I had basic hardware build out of the way, but this is when I hit “the software wall”. A mix of library issues, caused sensors  to provide no data, as well as not seating boards correctly. Also the Android build had an issue, which could not be corrected remotely correctly. At just before 2 a.m, I decided that was it, time to go home to kick off the Android build and get some sleep at about 02:30 a.m.


I woke up at about 07:30 a.m, checked my Android build on my server at home, it had completed. Next, I had some breakfast, transferred it to the phone and tried to “boot it”. The phone booted fine after a cache wipe, so that was another objective completed, the “about phone ” screen is shown below:-

Build state rom

On returning back to DJ at  around 11:30 a.m, it was obvious that some people had pulled an “all-nighter”, @JerseyITGuy was still in the corner seat where I had left him the night before. The the next few hours were spent breaking and fixing various software libraries. I ended up writing some custom python to get one of the sensors (AM2302 Temperature and Relative Humidity) working. I went out to lunch with the family and then returned to start building the Health Stage website, as I now had sensor data going to the internet.

At this point, I still had to build the MQTT broker, website and dashboard. It became clear that I would have to abandon building the broker  in order to get over the finishing line. So the point I want to make, is that you should have a plan that is flexible enough to cope with road blocks induced by time and or other factors.

So I set about building the website. Around 7 p.m, the majority of the website was uploaded. Lastly, there was the dashboard to code. I had allowed the whole of Saturday afternoon to code it, as I had recognised it was my weakest area of the build. I then had to reassess my plan once again, using directly for the dashboard rather than integrating it in the website.

By 10.00 p.m, I decided to stop and let the system settle down as I had live data on the dashboard at with the web application left to finish. A few of the hackathon competitors, decided to adjourn for a beer / cider across the road. I walked home after that to bed.

Working Dashboard.


I got to DJ just after 8 a.m, I decided to get my submission out of the way and then concentrate on the web application. I had a basic shell of an application to build and then I hit more software issues with the Android SDK, it became clear I was not going to solve it before the presentations.

At around this time, I saw Bendict who came in to see how the project was going. I showed him the project running with the light level, that I was going to demonstrate. Suddenly,to mu surprise, Benedict picked up his vape stick and blew on the contaminant sensor, it reacted crazy showing a large decrease in air quality. I asked Benedict, if he would not mind polluting the sensor during my presentation.

The Pitch

The four minute pitch went well, with the demo working perfectly, demonstrating the light level and Benedict’s pollution.

The Judging

I did not envy the judge’s task, as all the pitches were of an incredible standard with an amazing amount of variety of ideas. Everyone waited for the decision. Third place was awarded to MyGP, for their app which enabled better patient and doctor communication. Next second place. Boom, it was awarded to my project. I collected my prize (“a green laser printed robot trophy” plus £500) feeling immense. Now it was just time to see who had won.  The winner were Beacon, an app to help people call emergency services to their location. Here is my cool green robot trophy.

A Cool Trophy

The Future

The project is currently running as an indoor sensor with a thirty second update interval. I hope to move it outside, in an enclosure soon.

I will continue to work on the project, as I want to finish the web application part. In the next few weeks, I will putting up a detailed build guide and software configuration in the cyberkryption github repository. I intend to redesign the pcb, so that the modified sensors can be properly installed with jumper wires.

In the near future, I hope to get my hands on a “ehealth” shield and a set of sensors with a view to integrating it all with the new raspberry pi touchscreen. I also hope that we can get the air monitoring live in a few locations as well.

A Final Thank You

Finally, I would just like to thank the event sponsors and  Digital Jersey for a great event.



AV Evasion using on Kali Linux

A little while ago, I came across a script from Mike Czumak from SecuritySift here.

It was written as an experiment in AV Evasion as part of Mike’s OSCE course, but it has uses for defenders as well such as being able to dump sections of a Windows PE file.

The script can be downloaded from the SecuritySift here. It has three requirements, these are pefile, pydasm and SectionDoubleP.

The script uses a modified version of python’s pefile, so If you have that installed, then un-install it. After you have uninstalled it, modify the code as shown below:-


Add lines 2222-2225


Add line 2254


Now change to the pefile directory and do the usual ‘python install’ to install the module as shown below:-


You should also bear in mind, that the modified version may not be compatible with other tools using pefile.

Next we need pydasm, which is part of the libdasm project on googlecode here. Next download the zip file, extract it to a directory of your choice, change to the ‘libdasm-beta’ directory and run ‘python ./ install’, the output should be similar to below.


Now browse to the SectionDoubleP git repository here. Now click on ‘snapshot’ link, save the tar.gz archive to the same folder as pefile, extract the SectionDoubleP.y file to be in the same folder as as shown below.


Now to test if we can create an pecloaked file, first create a meterpreter binary and put it in the same directory making sure it is writeable. Let’s try to cloak it.


Happy pecloaking!!!!!

Planes,TV Tuners and Kali Linux

For a number of years, I worked within aviation as an engineer looking after flight systems such as Radars, Voice Switches and Aeronautical Radio. A while ago, I bought a Nooelec DVB-T TV tuner to play with Software Defined Radio (SDR), but I never quite got around it due to life.

Anyway, this post is about testing it to receive ADSB signals from aircraft.

The first stage is to blacklist the kernel driver ‘dvb_usb_rtl28xxu’ in /etc/modprobe.d/blacklist.local.conf.

Simply add the following to the file

blacklist dvb_usb_rtl28xxu

Now reboot your kali box and plug in your NooElec tuner, run ‘dmesg’ and you should get something like shown below.


Now git clone the rtl-sdr repo and build the software as root.

git clone git://
cd rtl-sdr/
mkdir build
cd build
cmake ../
make sudo
make install
sudo ldconfig

You can now run the rtl_adsb utility to test your configuration, the output should be as below.

Now that your DVB-T tuner is working you can run the command ‘rtl_adsb -V’ to do a basic test to see if you can receive any ADSB signals from aircraft. Assuming that is good then you can git clone the dump1090  repository and set it up as follows:-

git clone
cd dump1090

Now run the dump1090 program in interactive mode using the command ‘dump1090 –interactive’.

Below is a screen shot taken today.


As you can see ADSB provides quite a lot of information.

Jersey Hackathon Entry – A Ossec Hids and Simple Phishing console

I have been participating in the jersey hackathon held at the Digital Jersey hub in Jersey. My entry is a secure responsive console for ossec hids with simple phishing toolkit based on the poplular Bootstrap framework

Here the pitch

The cybersecurity malware industry costs the UK alone 27 billion pounds.Increasingly, we see that anti virus fails to protect our systems.

Recently, in the Channel Islansds, the Dridex banking trojan has been circulating which has been passing under the radar of anti virus solutions. This is where host intrusion detection comes into play as a second layer of defense for fintech systems. The ossec system is capable of performing not only intrusion detection but also file integrity monitoring enabling businesses to satisfy regulatory reguirements such as PCI-DSS.The system supports all major operating systems as well firewall / security applinaces from all major vendors. It is also possible to create alerts should a system try to contact a malware domain.

Whilst, technical solutions are great, they ignore the human factors. This is addressed with the solution by using a spear phishing toolkit. This enables fintech companies to train their users to prevent virus / malware infection at source.

The inclusion of these technologies in a single responsive console provides a complete solution for all device types for the fintech industry.

Furthermore, it would be possibly to deploy the console in a cloud environment as all communications are secured.

So thats the pitch, heres the screenshots

Console for users with policy information


Ossec Hids and Simple Phishing console for admin users

security2 security3

Wish me luck


Kali Linux 1.10 on a Pi-2 Update

Hi, this is an update on Kali 1.10 after my last post. It appears Muts(@kalilinux) and the Offensive Security crew have updated their github repo. Within the kali-arm-build-scripts is a new script for the Raspberry Pi-2 called The stages to build the image are as follows:-

  • gitclone the offensive security repository
  • put the the kernel image file in the kernel configs directory from here, making sure it is called ‘rpi-3.1.8.config’.
  • run the ‘rpi2/sh. 1.1.10’
  • burn the image to your sdcard

In bash, it goes something like this :-

mkdir arm-stuff
cd arm-stuff
<code>git clone
export PATH=${PATH}:/root/arm-stuff/gcc-arm-linux-gnueabihf-4.7/bin</code>
git clone
cd kernel-configs
wget -O rpi-3.1.8.config
cd ..
./ 1.10
dd bs=4M if=kali-image-name of=/dev/mmcblk0

The good news, is that the image has a patch for wireless injection for the 3.18 kernel and we should not need to copy the /lib/modules across as we have had to in previous builds. The only extra task, I would consider is to copy a config.txt to the boot directory to assign more graphics memory from the XFCE desktop. You can get one here.



In a further development, I received a comment from comment from YunHui Fu about a script that he has developed which not only builds Kali Linux but also Arch Linux with the wireless patches as well. YunHui github repo is here and you can build it as follows:-

git clone
cd arch-kali-rpi2


In order to build by YunnHui method, you need to use a Ubuntu host or soething similiar with Glibc > 2.14 otherwise the build will fail, a good choice would be Ubuntu 14.04.

You will need to make sure that you have alll the dependancies sorted, so use the ‘’ script from the kali arm repository above. Note ‘boot-umakeimage’ is now superseeded by ‘u-boot-tools’ and ia32libs is replaced by a number of packages, these are lib32z1,lib32ncurses5 and lib32bz2-1.0 respectively.

I am currently building Yunn Hui’s build and will post some screen shots on here.



Simple Screen Recorder on Kali Linux

I needed a screen recorder for some upcoming video tutorials that I might put together, but found that normal recorders such as recordmydesktop did not do the job well. After some ‘googling’, I can across Simple Screen Recorder, but there were no packages in the Debian or Kali repo’s. However, the developer’s github page has all that you need here.

The compile it, do the following:-

sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install build-essential pkg-config qt4-qmake libqt4-dev libavformat-dev libavcodec-dev libavutil-dev libswscale-dev libasound2-dev libpulse-dev libjack-jackd2-dev libgl1-mesa-dev libglu1-mesa-dev libx11-dev libxfixes-dev libxext-dev libxi-dev g++-multilib libx11-6 libxext6 libxfixes3 libxfixes3:i386 libglu1-mesa:i386
cd /usr/lib/i386-linux-gnu
sudo ln -s
sudo ln -s
sudo ln -s
sudo ln -s
sudo ln -s
sudo ldconfig

Now clone the developer’s repo , so that you have a local copy.

git clone
cd ssr

If you run in Kali as root (which is considered a bad security practice) then you need to comment out the root check in the install script as shown below:-


Now simply run the install script..