What’s new? I have received various inquiries as to whether this blog is still being maintained. Yes he still will! Currently, however, a lot has changed in my life and through various security settings of my provider I have created a few tutorials directly on GitHub. So here are 2 categories which I would like to introduce to you.
In this GitHub repository you will find instructions on how to use the small development board as a security analysis device. These instructions are simply intended to show which options the Raspberry PI offers and to provide an introduction to the topic of cyber security.
I love the Adafruit Matrix LED! With a little python you can achieve everything your heart desires super quickly and easily. To make the start a little easier for you, I’ve created a few examples with Python. You are welcome to use these or (even better) develop them further.
More???
I also started to post some pictures and videos of my work on Instagram … Yes, I have to go with time too. π
So if you find the time and feel like it, just drop by these platforms and let yourself be inspired for your projects.
This time I am not writing a tutorial on software. I would like to introduce you to my DIY project here. At a later point in time, however, I will focus on the newly used and partly self-developed software deeper.
Why this little project?
Over the years I have accumulated various electronic devices, cables and lots of other electrical scrap. Always storing it neatly is hell (I hate cardboard or plastic boxes). In addition, I do not live alone and should actually take all other people in the household into account. So I was looking for a better solution for my beloved girlfriend, my dog ββ(who also likes to eat things) and of course my self. In addition, everything should be tidy, ready to hand and mobile. When I then remembered my training as an electrician (especially on my toolbox), it quickly became clear to me which solution would be suitable for me. Different Suitcases made of aluminum (light and stable), where each of them have slightly different scope.
What’s in there?
Actually there are several suitcases with different contents (depending on what I have planned). I would like to show you now, two of my personal favorites here.
In addition, all cases are filled with brackets and foam so that the connecting cables are not visible (this is not shown in the pictures) and each device has a specific place.
Do you want such suitcases, too?
If you also want one (or more) suitcases and don’t have the time or inclination to build them yourself – just contact me! We can talk about it.
Note: It is important to know that each case and its contents are freely configurable (but it should fit).
In my last tutorial, I showed you how to install RfCat and the ooktools on your macOS, as I promised to go into more detail on the ooktools later – I want to keep this promise now.
Requirements
RfCat installed
ooktools installed
jq installed (optional)
you own a Yard Stick One (or any rfcat compatible device)
you own a Garage Door opener (or similar device)
Objective
Learn and understand the ooktools sub command ‘signal’.
ooktools signal
The ooktools offers many great features (look at the command line help)! In this tutorial I will focus on signal search, signal record, signal plot and signal play.
# show sub command signal help
$ python2.7 -m ooktools.console signal --help
...
Usage: console.py signal [OPTIONS] COMMAND [ARGS]β¦
Signal Commands.
Options:
--help Show this message and exit.
Commands:
brute Bruteforce a binary range.
jam Jam a frequency by just sending noise.
play Play frames from a source file.
plot Plot frames from a recorded signal.
record Record frames to a file.
search Search for signals.
send Send signals using a RFCat dongle.
Search a signal
My garage door opener has information about the frequency (868.3 MHz) on the back, which makes my search a little easier! If this is not the case for you, search for the FCC identifier.
If you have a rough idea about the frequency (and other values), look in the signal search help and compare all standard values with your needs! You only have to overwrite the values ββwhich do not match (as arguments).
# show help for signal search
$ python2.7 -m ooktools.console signal search --help
# search signal in specific range
$ python2.7 -m ooktools.console signal search -S 868200000 -E 868400000
Note: Only signal search throws sometimes an Python/USB exception on my OS (after finish the search), all other commands work perfectly. If you have the same problem, reconnect the USB device (Yard Stick One)!
Record a signal
Now run the signal record. Go the same way like you did for the signal search! First look at the sub command help, overwrite the default values and run the command.
# show help for signal record
$ python2.7 -m ooktools.console signal record --help
# start a signal record
$ python2.7 -m ooktools.console signal record -F 868300000 -f 60 -D ~/Desktop/test.json
After the signal record is finished, you can have a look on the JSON file.
# view file content and pipe output to jq (optional)
$ cat ~/Desktop/test.json | jq .
Plot the recorded signal
With signal plot you can easily create and watch frames from a recorded signal (json file). The help shows you the possible fine adjustments for the plot output. I have recorded 9 Frames, maybe that differs for you!
# show help for signal plot
$ python2.7 -m ooktools.console signal plot --help
# plot a signal record (number of frames)
$ python2.7 -m ooktools.console signal plot -c 6 -S ~/Desktop/test.json
To specify the plot you can use sub command agrument --series.
# plot a signal record (series of fields)
$ python2.7 -m ooktools.console signal plot -s 1:4 -S ~/Desktop/test.json
Play a signal
It’s time to try. For that I have to walk a long way to the parking garage gate (I usually drive this route). For signal play sub command only two arguments are needed (source & repeats).
# show help for signal play
$ python2.7 -m ooktools.console signal play --help
# play a signal record
$ python2.7 -m ooktools.console signal play -r 2 -S ~/Desktop/test.json
I did not modify the record file, just run all recorded frames for 2 times. If you are wondering if this worked for me? No – the signal is sent too quickly this way. The gate doesn’t open like this. With tools like GQRX / URH & HackRF One I was able to compare the signals. So some fine-tuning is needed (baud rate/modulation/etc.). Nevertheless, you should have got a good overview of the ooktools.
Some time ago, I wrote a tutorial about RfCat installation on Kali Linux. Many people asked me for similar tutorial on macOS (Big Sur). So I will use this time now (my first tutorial of year 2021), to show and try to explain (as best I can do). Also I will try to provide some basics for usage, as the community seems not so big and less online documentation is available like for other topics. You can reuse the knowledge for other OS, too.
First you need to download libusb tarball, unzip the downloaded archive and compile/install it (don’t worry sounds harder as it is). If you choose other sources like macports, you may run into location issues (paths to binaries/libraries).
Note: the following examples will just provide the latest version (1.0.24), while I was writing this tutorial. Please look beforehand if there is a newer libusb version already available.
# download via curl
$ curl -L -C - "https://github.com/libusb/libusb/releases/download/v1.0.24/libusb-1.0.24.tar.bz2" -o ~/Downloads/libusb-1.0.24.tar.bz2
# unzip archive
$ tar -xf ~/Downloads/libusb-1.0.24.tar.bz2 -C ~/Downloads/
# change into extraced archive directory
$ cd Downloads/libusb-1.0.24
# verify dependencies for build and install process are available
$ ./configure
# run build
$ make
# run installation
$ sudo make install
# verify installation (optional)
$ ls -la /usr/local/lib/libusb*
# delete archive and directory (optional)
$ rm -fr ~/Downloads/libusb-1.0.24*
Install required Python packages with Python Pip. Without these the RfCat compilation, installation and usage will not correctly work!
Note: As I do have different Python version installed, I specify the excat Python version (2.7.x) in the following examples. If you have only the default MacOS Python version installed – you could use pip directly (without python2.7 -m).
Clone RfCat Git repository from Github (may some older online documentations still link to Bitbucket). In the following example I choose the Downloads directory – of course you can choose any preferred destination.
# clone from GitHub
$ git clone https://github.com/atlas0fd00m/rfcat.git ~/Downloads/rfcat
# change directory
$ cd Downloads/rfcat
# run the installation
$ sudo python2.7 setup.py install
# verify the installation (optional)
$ ls -la /usr/local/bin/rfcat*
# show rfcat help (optional)
$ /usr/local/bin/rfcat -h
# delete cloned directory (optional)
$ rm -fr ~/Downloads/rfcat
If everything went well so far, you should take a look at your installed Python packages.
Now I recommend to install the ooktools packages via Python Pip. The ooktools will make your life much easier and you will have much faster results.
# install ooktools via pip
$ python2.7 -m pip install ooktools
# verify and show help (optional)
$ python2.7 -m ooktools.console --help
# verify and show specific help topic (optional)
$ python2.7 -m ooktools.console wave --help
I’ll go into the ooktools in a later tutorial, but not today.
Run RfCat
So far so good. Let’s start to connect the Yard Stick One (plug into USB) and run the first example. Always have in mind, the official operating frequencies (for the Yard Stick One):
300 – 348 MHz
391 – 464 MHz
782 – 928 MHz
Note: RfCat expact the values in “Hz”, so 315 MHz are 315000000 Hz.
Hint: don’t put any other transmitter next to the Yard Stick One while you use it (eq. Mobile, Wifi router, etc.). You could destroy it or weaken/disrupt your signals.
# start scan on specific frequency (315 MHz)
In [1]: d.specan(315000000)
You should see now the spectrum analyser.
Okay, stop the scanning process by closing the spectrum analyzer window. Now let’s start a simple record (also if you don’t have a signal nearby).
Note: there are many more settings and I cannot describe all here! It always depends to the problem you like/need to solve.
# enter the IDLE state (important after any action)
In [2]: d.setModeIDLE()
# specific frequency (315 MHz)
In [3]: d.setFreq(315000000)
# specific modulation (ASK/OOK/Manchester encoding)
In [4]: d.setMdmModulation(MOD_ASK_OOK)
# specific baudrate (4800 Hz)
In [5]: d.setMdmDRate(4800)
# turn on the amplifier
In [6]: d.setMaxPower()
# drops most blocks to pkts (CARRIER)
In [7]: d.lowball()
# start and dump data to screen
In [8]: d.RFlisten()
# stop listen (press Enter to stop)
# enter the IDLE state (or you need to unplug from USB)
In [9]: d.setModeIDLE()
# exit
In [10]: exit()
Your result should look like:
Hint: use the Tabulator key for command-line completion (also tab completion) and take use of the internal help of RfCat (eq. help(d.setMdmModulation))
The popular frequencies are mostly near by:
315 MHz (car fobs)
433 MHz (door openers, medical devices)
868 MHz (door openers in EU/swiss)
915 MHz (industrial equipment, medical devices)
Send via Python script
It would be not enough to show you only Command line and nothing about transmit. Therefore now a small Python script, which send out some example data. I think the following script is self explanatory.
from rflib import *
d = RfCat()
d.setFreq(315000000)
d.setMdmModulation(MOD_ASK_OOK)
d.setMdmDRate(4800)
print("Transmission starting")
d.RFxmit("\x2e\x2e\x2d\x2e\x2e\x2d\x2e\x00\x00\x00\x00\x00\x00"*10)
print("Transmission complete")
Hint: \x escape sequence means the next two characters are interpreted as hex digits for the character code (\x is used inside strings to represent a character), 0x is used for literal numbers in Python.
I’ve tried many times and different ways but the installation of Gqrx and GNU Radio on macOS Big Sur via MacPorts failed always. I did not give up and found a working solution for me (my HackRF One) and these two needed tools. In this tutorial I would like to show you the installation (Gqrx & GNU Radio). If you need first to install HackRF One on macOS, please have a look here.
Install XQuartz
First download and installation starts with XQuartz. Download the latest DMG, run the installation and logout/login from your system.
Install Gqrx SDR
As already mentioned, Gqrx (at least for me) cannot installed on Big Sur via MacPorts. Therefore download and install the precompiled binary from Gqrx. As soon the installation was successful, you can connect and use the HackRF One.
Install Python 3.7
The third step also requires a download and installation. Look for the version Python 3.7! Any version below will not work.
Install GNU Radio
Finally, at the last step, we can start to download and install GNU Radio. It’s a quite big application, so please be patient while processing. Also the startup of GNU Radio (inside XQuartz) takes always some few seconds.
If you consider the time (download/installation) compared to the MacPorts installation (download/build/installation), a time gain. Of course Xquartz is also needed for MacPorts. Here if you will try via MacPorts:
# install gr-osmosdr (incl hackrf + gnu radio)
$ sudo port install gr-osmosdr
# install gr-fosphor (needed by gnu radio)
$ sudo port install gr-fosphor
# install gqrx
$ sudo port install gqrx
This time it’s about installing HackRF One binaries on the macOS Big Sur. In another later tutorial I will dive deeper into macOS, HackRF ONE and GnuRadio (gnuradio-companion), but not yet. The installation takes place via latest MacPorts.
My first installation failed with a error (even as MacPorts where completely new installed and Command Line Tools where installed, too). I looked into log file and saw a issue with clang version.
# read log file (optional)
$ cat /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_hackrf/hackrf/main.log
β¦
clang: error: invalid version number in 'MACOSX_DEPLOYMENT_TARGET=11.0'
β¦
# show clang version (optional)
$ clang --version
So looked it up on the Internet and saw that the clang version in the new SDK is higher and will solve this issue. To confirm I had a look installed SDK’s.
# list SDKs (optional)
$ ls /Library/Developer/CommandLineTools/SDKs/
MacOSX.sdk MacOSX10.14.sdk MacOSX10.15.sdk
To be really sure. Yes new SDK is installed.
# list SDKs (optional)
$ ls /Library/Developer/CommandLineTools/SDKs/
MacOSX.sdk MacOSX10.14.sdk MacOSX10.15.sdk MacOSX11.1.sdk
# show xcrun configs (optional)
$ xcrun --sdk macosx11.1 --show-sdk-path
$ xcrun --sdk macosx11.1 --show-sdk-version
Installation
After the installation and verification (yes the new sdk was getting installed), I tried the macPorts installation again.
# install hackrf via mac ports
$ sudo port install hackrf
Test installation
This time all went fine and I could start testing the device.
# show USB device info (optional)
$ ioreg -p IOUSB -l -w 0 -b
# show hackrf info
$ hackrf_info
# start debug (optional)
$ hackrf_debug --si5351c -n 0 -r
# start record
$ hackrf_transfer -r myRecord.raw -f 433780000
# start transmit record
$ hackrf_transfer -t myRecord.raw -f 433780000 -x 20
MG made something really cool (and dangerous too) to perform keystroke injection attacks (via Rubber Ducky scripts) simply over wireless interface. In this tutorial I want to show you the first important steps before you can start the penetration testing. The cables, programmer and other awesome MG products are available from Hak5.
Important: You should own (or buy) at least one O.MG Cable Programmer, otherwise you will not be able to follow the steps below!
Preparation
First check whether Python 3.7 (or higher) and pyserial (incl. dependencies) is installed. It is already pre-installed in my Kali Linux.
Download the latest O.MG Firmware (incl. needed scripts/binaries) now.
# download latest Firmware via CURL
$ curl -L -C - https://github.com/O-MG/O.MG_Cable-Firmware/releases/download/v1.5.3/O.MG_Cable-Firmware-v1.5.3.zip -o ~/Downloads/O.MG_Cable-Firmware-v1.5.3.zip
# unzip archive
$ unzip ~/Downloads/O.MG_Cable-Firmware-v1.5.3.zip -d ~/Downloads/
# list content (optional)
$ ls -la ~/Downloads/O.MG_Cable-Firmware-v1.5.3/
# list physical USB device hierarchy (optional)
$ lsusb
Install Firmware
Now plug the O.MG programmer into your computer and the O.MG cable into the programmer. This can be a bit more difficult at first, so be careful not to destroy everything right away. Even when pulling out – Treat it like a beautiful woman.
Note: If you are running Kali Linux as VM (e.g. VirtualBox), passthrough needed USB devices.
Change into directory O.MG_Cable-Firmware-v1.5.3 and set the file permissions for file flash.py and start the Firmware configuration and setup.
# list physical USB device hierarchy (optional)
$ lsusb
# run python script
$ sudo python3 ./flash.py
Caution: If you see the following output (or similar) Connecting........_____..... but flashing the firmware ends with an error – means that the programmer was recognized correctly but the cable was not. Remove the cable and plug it in again. In addition, the cable needs a reset after every firmware flash.
If everything works (which is the normal case) you will be asked in which mode (AP or STA) the wifi should work. In my example, I am using for this tutorial the Access Point (AP) mode. So I’ll set the SSID as well as wifi credentials. You can later access with any modern browser via URL http://192.168.4.1. Whether you need AP or STA mode depends on your environment and your attack vector. But try to get to know both as well as their respective advantages and disadvantages.
SELECT WIFI MODE ...: 2
ENTER WIFI SSID ...: OMGtest
ENTER WIFI PASS ...: test12345
Confirm your entries and wait a moment. An overview is displayed (do not forget the password).
Flash Operation Complete!
[ WIFI SETTINGS ]
WIFI_SSID: OMGtest
WIFI_PASS: test12345
WIFI_MODE: 2
WIFI_TYPE: ACCESS POINT
[ FIRMWARE USED ]
INIT: firmware/esp_init_data_default_v08.bin
ELF0: firmware/image.elf-0x00000.bin
ELF1: firmware/image.elf-0x10000.bin
PAGE: firmware/page.mpfs
<<< PROCESS FINISHED, REMOVE PROGRAMMER >>>
Press Enter to continue...
That was done super quickly and easily. Now pull the cable out of the programmer and you can start.
After you receive your new Shark Jack device from Hak5, you need to upgrade the Firmware. This tiny tutorial will guide you through the process. You should plan a maximum of 10 minutes of your life for this action.
Preparation
Enable the Arming mode (middle switch position) and connect with your RJ45 interface, also connect USB-C for charging. Do not stop charging while the whole upgrade process! In case your local device does not provide such interface, I have really good experience with the multiport adapter from SATECHI.
# download Firmware (via command line)
$ curl -L -C - https://downloads.hak5.org/api/devices/sharkjack/firmwares/1.1.0-stable -o ~/Downloads/upgrade-1.1.0.bin
# verify SHA256 checksum (optional)
$ shasum -a 256 ~/Downloads/upgrade-1.1.0.bin
# copy Firmware from local to Shark Jack device
$ scp -C4 ~/Downloads/upgrade-1.1.0.bin root@172.16.24.1:/tmp/
# SSH into SharkJack device
$ ssh -C4 root@172.16.24.1
# list directory content (optional)
root@shark:~# ls -la
# show current version
root@shark:~# cat VERSION
1.0
# start update
root@shark:~# sysupgrade -n /tmp/upgrade-1.1.0.bin
Now be patient and do not remove the Shark Jack from RJ45 or the USB-C for charging! The device installs the new firmware and reboots. For me it was around 3 – 4 minutes.
# check interface status (optional)
$ ifconfig
# SSH into Shark Jack device
$ ssh -C4 root@172.16.24.1
# show current version
root@shark:~# cat VERSION
1.1.0