https://wiki.elvis.science/api.php?action=feedcontributions&user=Silvie&feedformat=atomEmbedded Lab Vienna for IoT & Security - User contributions [en]2024-03-28T19:19:16ZUser contributionsMediaWiki 1.37.2https://wiki.elvis.science/index.php?title=Hak5_Key_Croc&diff=11578Hak5 Key Croc2023-03-03T15:45:30Z<p>Silvie: </p>
<hr />
<div>==Summary==<br />
This article describes the Hak5 Key Croc, a smart hardware keylogging device. <br />
[[File:keycroc_photo.png]]<ref name="Pictures"></ref><br />
<br />
==Key Croc Basics==<br />
[[File:Keycroc_specs.png]]<ref name="Pictures"></ref><br />
<br />
KeyCroc is Hak5's smart keylogger and a remote penetration testing tool. In May 2020 Key Croc was introduced by HAK5 founder Darren Kitchen. A hardware keylogger is a small electronic hardware device that records keyboard activity.<br />
The keylogger software saves the keystrokes to a file, which he can later access remotely over the internet via the cloud from HAK5.<br />
To use the keylogger, connect KeyCroc to your computer. Then connect the USB port of a standard PC compatible USB keyboard to the other end. Key Croc automatically clones the hardware identifiers of attached keyboards. Target USB plugs can emulate USB keyboards, memory, serial, and ethernet. The payload can be executed using commands written in Ducky Script 2.0. LED lights indicate the current status. Additionally, the device is WiFi enabled and SSH enabled and is priced at $119.99. The main drawback is that Key Croc can only be connected to external keyboards.<br />
The Key Croc contains a Quad Core ARM processor, 512 MB RAM, and an 8 GB SSD. It can be connected to the internet by entering a Wi-Fi name and password into its config file. The Key Croc has to be connected to the target device via USB. Once it is installed between a PC and its keyboard, it starts its booting process, indicated by the LED changing its color. After it has booted, the LED is turned off and the Key Croc is now in Attack Mode. <br />
<br />
===Attack Mode===<br />
Attack Mode is visible from the outside by the LED being turned off. In this mode, the Key Croc clones the hardware identifier of the keyboard connected to it and poses as this keyboard. Thus, each keystroke entered via the keyboard is sent to the PC, but also recorded in the Key Croc’s loot file. Payloads may be triggered by typing the required keyword. Pressing the hidden button on the back of the Key Croc will cause it to enter Arming Mode.<br />
<br />
===Arming Mode===<br />
Arming Mode is visible from the outside by the LED blinking blue. In Arming Mode, no further keystrokes are recorded and payloads can’t be activated anymore. Instead, the Key Croc emulates a USB flash disk and a serial device, allowing the user to access it via the device’s file manager. A password and timeout to enter the Arming Mode can be configured in the Key Croc’s config file, if they aren’t configured the Key Croc will enter Arming Mode as soon as the button is pressed.<br />
<br />
===Key Croc's File System===<br />
*config.txt – configuration file<br />
*upgrade.html – shortcut to software update documentation<br />
*version.txt – current version<br />
*docs/ – license and quick start guide<br />
*languages/ – hosts keymap files used for recording and injection<br />
*library/ – hosts inactive payloads<br />
*loot/ – hosts captured keystrokes and other logs<br />
*payloads/ – hosts active payloads<br />
*tools/ – used to install additional packages<br />
<br />
===LED Colors===<br />
<br />
*Green – Booting up<br />
*Red – Error<br />
*Cyan – Configuring Wi-Fi per config.txt<br />
*Magenta – Configuring Keylogger<br />
*Blue – Arming Mode<br />
*Yellow – Disk Full<br />
*White – No Keyboard Detected<br />
<br />
===Basic Commands===<br />
*MATCH – specifies a pattern that must be typed to trigger payload execution<br />
*SAVEKEYS – saves next or last typed keys to a specified file when a MATCH is found<br />
*QUACK – injects keystrokes using Ducky Script 2.0<br />
*QUACKFILE – injects keystrokes from specified file<br />
*ATTACKMODE – specifies which device type to emulate<br />
*LED – controls the multi-color LED<br />
*GET_VARS – returns useful variables for use in payload<br />
*INSTALL_EXTRAS – installs optional <br />
*WAIT_FOR_LOOT – halts payload until specified loot is received<br />
*C2NOTIFY – sends a notification to the configured Cloud C2 server<br />
*C2EXFIL – sends a file to the configured Cloud C2 server<br />
<br />
==Payloads==<br />
<br />
[[File:Keycroc_payload.png]]<ref name="Payload"></ref><br />
<br />
The Key Croc offers the possibility to execute payloads on the targeted device. To be able to get activated, the payloads have to exist as either .txt or .sh files in the payloads/ directory on the Key Croc. Payloads that aren’t currently used can be stored in the library/ directory. <br />
Most payloads activate on MATCH, meaning that if a certain string is typed, the payload will be triggered. The date and time of activation of a payload is logged in the associated log file in the loot/ folder. The language used in the payloads is Ducky Script 2.0, or QUACK.<br />
Payloads can be written by the pentester themselves, or downloaded from the Hak5 GitHub repository.<br />
<br />
[[File:Sudo-pass.png | 400px]]<br />
<br />
This example shows how to get the password of a user on an Ubuntu machine.<br />
First you need to tell it to wait for the "sudo" string. If the user types "sudo", the victim's keystrokes are recorded. SAVEKEYS UNTIL, like MATCH, can be a simple string or a complex regular expression. As the name suggests, it saves the entered key until it matches.<br />
This little regex basically says that the key will be saved until ENTER is pressed twice. First his ENTER key is known to be at the end of the sudo command. Then enter your password when prompted. So it checks passwords using all regular expressions (.*?) until the last statement is the final ENTER key.<br />
In this case, the WAIT_FOR_LOOT command tells the payload to wait until the specified loot file is written. Use this awk -F to create a new file containing only the extracted password and send it to Cloud C2 with a notification.<br />
<br />
==Tools==<br />
Additional pentesting tools like Metasploit might be installed on the Key Croc. Installation requires an active WiFi connection (which can be configured in the config.txt) and can be done via SSH, Cloud C2, or serial connection.<br />
After installation, these tools can be found in the tools/ directory.<br />
==Accessing Key Croc==<br />
<br />
The Key Croc can be accessed via its USB flash disk, using any device's file manager. This enables the user to configure the Key Croc, check its loot files and change its active payloads. If a WiFi network and password is entered into the Key Croc's configuration file and it is configured to connect to a Cloud C2 server, captured keystrokes may also be streamed to this server. The Cloud C2 server also offers the possibility for a user to send payloads remotely to the Key Croc. Another way to remotely access the Key Croc is per SSH connection, which also has to be configured in the config.txt first. <br />
Finally, having a serial console connection to the Key Croc enables the user to access its Linux shell. <br />
Additional pentesting tools like Metasploit may be installed via Cloud C2, SSH, or serial console connection using the INSTALL_EXTRAS command.<br />
<br />
==References==<br />
[https://docs.hak5.org/hc/en-us/categories/360003797793-Key-Croc Hak5 Key Croc Documentation]<br />
<references><br />
<ref name="Pictures">https://hak5.org/products/key-croc</ref><br />
<ref name="Payload">https://github.com/hak5/keycroc-payloads/blob/master/payloads/examples/example_text-expander.txt</ref><br />
</references><br />
<br />
[[Category:Documentation]]</div>Silviehttps://wiki.elvis.science/index.php?title=PandwaRF&diff=9800PandwaRF2022-02-03T16:27:30Z<p>Silvie: </p>
<hr />
<div>[[File:PandwaRF.png]] <ref>https://wiki.elvis.science/index.php?title=File:PandwaRF.png</ref><br />
<br />
== Description ==<br />
<br />
PandwaRF is a family of pocket-sized, portable RF analysis tools operating the sub-1<br />
GHz range produced by the Comthings, a French startup focused on the PandwaRF<br />
analysis tool and custom RF penetration testing tools for professionals and law enforcement agencies. <ref>Tania. Home: https://www.comthings.com/</ref><br />
analysis and re-transmission of RF via an Android device or a Linux PC.<br />
<br />
It can be connected to an Android smartphone using BLE or USB, and to Linux using USB. <br />
It is based on the well-known RfCat and Yard Stick One tools with the Texas<br />
Instruments CC1111 RF transceiver <ref>Texas Instruments. instruments guide, https://www.ti.com/product/CC1110-CC1111 ,<br />
2013.</ref>, but with a lot of new features, making<br />
PandwaRF the perfect portable RF analysis tool. Practically, it removes the<br />
‘standard SDR Grind’ of capturing, demodulating, analyzing, modifying and replaying<br />
by hand – replacing it with a simple but powerful interface.<br />
<br />
The PandwaRF system consists of two elements: the hardware device and the software controller, either an Android device or a PC. <br />
The hardware is a very capable<br />
device, tailored for beginners and advanced users alike.<br />
Beyond the functionality provided by the Android interface, the PandwaRF can be<br />
easily controlled and customized. No need to risk bricking your device or writing in C,<br />
the PandwaRF can be controlled by JavaScript, directly on the smartphone.<br />
The Rogue Pro was designed for advanced users like pentesters or security professionals and it is specialized on brute forcing wireless devices in order to test their<br />
security.<br />
<br />
==General Overview==<br />
PandwaRF is a Radio Frequency hacking tool used to:<ref>https://www.comthings.com/</ref><br />
===Receive===<br />
<li>Capture any data in ASK/OOK/MSK/2-FSK/GFSK modulation from the frequency range: 300-348 MHz, 391-464 MHz and 782-928 MHz</li><br />
<li>Transfer the captured data to your smartphone & save/share it<br />
<li>Send the captured data in JSON to your own server for post-processing<br />
<li>Write your own scripts or use a provided one<br />
===Transmit===<br />
<li>Transmit previously captured data or write your own<br />
<li>Transmit data from a smartphone or directly from PandwaRF<br />
<li>Brute force with a predefined transmission pattern (encoders or devices)<br />
<li>Transmit power: +10dBm<br />
===Analyze===<br />
<li>Visualize the frequency used by any device using the PandwaRF built-in Spectrum Analyzer<br />
<li>Directly show the maximum and average RSSI for a specific frequency band<br />
<br />
==Technical Overview==<br />
PandwaRF is composed of 2 elements:<br />
<li>PandwaRF HW dongle<br />
<li>PandwaRF Android application<br />
<br />
===PandwaRF HW dongle===<br />
The PandwaRF dongle contains<ref> https://pandwarf.com/pandwarf-rogue-pro/ </ref>:<br />
<li>Bluetooth Smart Module ISP130301, based on nRF51<br />
<li>CC1111 Low-Power SoC with Sub-1 GHz RF Transceiver<br />
<li>16 Mbit Flash Memory to save custom RF protocols<br />
<li>Rechargeable battery powered for stand-alone operation<br />
<li>Battery fuel gauge<br />
<li>SMA connector<br />
<li>4 buttons<br />
<li>4 Status LEDs<br />
<li>Debug connectors & GPIOs<br />
<br />
==Possible applications==<br />
<li>Receive keyfobs transmission (car, alarm, gate opener, …)<br />
<li>Replay captured transmission from keyfobs<br />
<li>Replay a modified captured transmission<br />
<li>Transmit your own custom payload<br />
<li>Capture RF data and transmit it on another frequency<br />
<li>Brute force wireless devices (alarms, gate openers etc)<ref>https://github.com/ComThings/PandwaRF/wiki</ref><br />
<li>Spectrum Analyzer<br />
<li>Find the frequency used by a RF device<br />
<li>Reverse engineer unknown protocols<br />
<li>Measure the data rate of a transmission<br />
<li>Check the RF jam-resistance of your own devices<br />
<li>Send captured data to a server for post-processing<br />
<li>Write custom Javascript scenarios<br />
<li>Develop your own Android application<br />
<br />
==Hardware Antennas==<br />
<br />
In its antenna pack version, PandwaRF is shipped with 3 miniature SMA antennas (315/433/868-915 MHz).<br />
<br />
Using the proper antenna is critical to have good RF performance.<br />
Antennas are labelled with the first digit of their frequency band:<br />
<li>3 for 315 MHz,<br />
<li>4 for 433 MHz,<br />
<li>8/9 for 868/915 MHz<br />
<br />
<br />
===Warning===<br />
PandwaRF is a test equipment for RF systems. It has not been tested for compliance with the regulations governing the transmission of radio signals. You are responsible for using your PandwaRF legally. The intentional jamming of RF signals is ILLEGAL. PandwaRF should only be used for testing the robustness of your own devices.<br />
<br />
== References ==<br />
<br />
<references /><br />
<br />
[[Category:Documentation]]</div>Silviehttps://wiki.elvis.science/index.php?title=Genome_Browser_in_a_Box_(UCSC_GBiB)_Setup&diff=7944Genome Browser in a Box (UCSC GBiB) Setup2021-10-27T12:26:26Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
This article describes the setup of the UCSC Genome Browser in a Box (GBiB).<br />
<br />
== Requirements ==<br />
<br />
* Software: 7zip[https://www.7-zip.org/download.html], WinRAR[https://www.win-rar.com/start.html?&L=1], VirtualBox[https://www.virtualbox.org/wiki/Downloads]<br />
<br />
== Description ==<br />
<br />
=== Step 1 ===<br />
<br />
Download GBiB (Genome Browser Store[https://genome-store.ucsc.edu/])<br />
<br />
You will need at least 20GB free space (you can also use an external hdd/ssd).<br />
<br />
=== Step 2 ===<br />
<br />
Unzip the ''gbib.zip'' file:<br />
<br />
* Windows: use 7zip or WinRAR<br />
* MacOS: double-click on zip-file (do not unzip via command-line)<br />
<br />
=== Step 3 ===<br />
<br />
Add GBiB to VirtualBox:<br />
<br />
* Double-click on ''browserbox.vbox'' file<br />
'''OR'''<br />
* Start VirtualBox, select Machine >> Add, and open the file ''browserbox.vbox''<br />
<br />
* Finally, start GBiB in VirtualBox by clicking ''Start(en)''; now some updates will be done - this might take a few minutes.<br />
<br />
=== Step 4 ===<br />
<br />
In a browser open the Genome Browser by entering the following address:<br />
<br />
127.0.0.1:1234<br />
<br />
(avoid using localhost:1234)<br />
<br />
<br />
== Courses ==<br />
<br />
* [[Netzwerk- und Internettechnologien]] (2021)<br />
<br />
== References ==<br />
<br />
* https://genome.ucsc.edu<br />
<br />
[[Category:Basic]]</div>Silviehttps://wiki.elvis.science/index.php?title=Genome_Browser_in_a_Box_(UCSC_GBiB)_Setup&diff=7943Genome Browser in a Box (UCSC GBiB) Setup2021-10-27T11:56:06Z<p>Silvie: Created page with "== Summary == This article describes the setup of the UCSC Genome Browser in a Box (GBiB). == Requirements == * Software: 7zip[https://www.7-zip.org/download.html], WinRAR..."</p>
<hr />
<div>== Summary == <br />
<br />
This article describes the setup of the UCSC Genome Browser in a Box (GBiB).<br />
<br />
== Requirements ==<br />
<br />
* Software: 7zip[https://www.7-zip.org/download.html], WinRAR[https://www.win-rar.com/start.html?&L=1], VirtualBox[https://www.virtualbox.org/wiki/Downloads]<br />
<br />
== Description ==<br />
<br />
=== Step 1 ===<br />
<br />
Download GBiB (Genome Browser Store[https://genome-store.ucsc.edu/])<br />
<br />
You will need at least 20GB free space (you can also use an external hdd/ssd).<br />
<br />
=== Step 2 ===<br />
<br />
Unzip the ''gbib.zip'' file:<br />
<br />
* Windows: use 7zip or WinRAR<br />
* MacOS: double-click on zip-file (do not unzip via command-line)<br />
<br />
=== Step 3 ===<br />
<br />
Add GBiB to VirtualBox:<br />
<br />
* Double-click on ''browserbox.vbox'' file<br />
'''OR'''<br />
* Start VirtualBox, select Machine >> Add, and open the file ''browserbox.vbox''<br />
<br />
* Finally, start GBiB in VirtualBox by clicking ''Start(en)''; now some updates will be done - this might take a few minutes.<br />
<br />
=== Step 4 ===<br />
<br />
In a browser open the Genome Browser by entering the following address:<br />
<br />
127.0.0.1:1234<br />
<br />
(avoid using localhost:1234)<br />
<br />
<br />
== Courses ==<br />
<br />
* [[Netzwerk- und Internettechnologien]] (2021)<br />
<br />
== References ==<br />
<br />
* https://genome.ucsc.edu<br />
<br />
[[Category:Basics]]</div>Silviehttps://wiki.elvis.science/index.php?title=Riot-OS_Setup&diff=7891Riot-OS Setup2021-10-13T16:58:46Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
Setting up Riot-OS on a Atmel SAM R21 Xpro Board.<br />
<br />
== Requirements ==<br />
<br />
* Operating system: Ubuntu 20.04 <br />
* Packages: git<br />
<br />
== Description ==<br />
<br />
=== Step 1 ===<br />
<br />
Install the following packages<br />
<br />
<br />
sudo apt-get update<br />
sudo apt-get install git <br />
openocd<br />
gcc-multilib<br />
build-essential<br />
python3-serial<br />
libudev-dev<br />
moserial<br />
<br />
=== Step 2 ===<br />
<br />
Install the toolchain<br />
<br />
sudo apt-get install gcc-arm-none-eabi<br />
<br />
If you use a recent version of RIOT-OS (Release-2021.07) you can go on with '''Step 3'''.<br />
<br />
<br />
If you use an older RIOT-OS version, you will have to do the following steps:<br />
<br />
Goto https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm and download<br />
<br />
gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2<br />
<br />
Move it to your home directory.<br />
<br />
Uninstall old packages<br />
<br />
sudo apt remove binutils-arm-none-eabi gcc-arm-none-eabi libnewlib-arm-none-eabi<br />
<br />
Unzip the downloaded file<br />
<br />
tar -xjvf gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2<br />
<br />
Add the toolchain to your path<br />
<br />
export PATH=$PATH:/home/(your user)/gcc-arm-none-eabi-7-2018-q2-update/bin/<br />
<br />
For now: you will have to do this in the bash where you build your application - after each restart.<br />
<br />
=== Step 3 ===<br />
<br />
Download Riot-OS<br />
<br />
git clone https://github.com/RIOT-OS/RIOT.git myRIOT<br />
<br />
Move to the "Hello World"-Example<br />
<br />
cd myRIOT/examples/hello-world<br />
<br />
Build the application on "native"<br />
<br />
make all term<br />
<br />
Now, you should see this output in your terminal:<br />
<br />
RIOT native interrupts/signals initialized.<br />
LED_RED_OFF<br />
LED_GREEN_ON<br />
RIOT native board initialized.<br />
RIOT native hardware initialization complete.<br />
<br />
main(): This is RIOT! (Version: 2022.01-devel-129-g554d3)<br />
Hello World!<br />
You are running RIOT on a(n) native board.<br />
This board features a(n) native MCU.<br />
<br />
=== Step 4 ===<br />
<br />
Build and run "Hello World" on the SAM R21 Board.<br />
<br />
Set the rights for your username to be able to flash the application on the board.<br />
<br />
sudo usermod -a -G dialout <username><br />
<br />
Then reboot your computer.<br />
<br />
Connect the board to your computer via micro USB cable (USB EDBG interface).<br />
<br />
[[File:samr21EDBGconnect.jpg]]<br />
<br />
Connect via Moserial.<br />
<br />
[[File:moSerial.jpg]]<br />
<br />
Build and flash the application.<br />
<br />
cd myRIOT/examples/hello-world<br />
make BOARD=samr21-xpro<br />
make BOARD=samr21-xpro flash<br />
<br />
If you do not use a serial terminal like moserial or terraterm use term<br />
<br />
make BOARD=samr21-xpro term<br />
<br />
You may also set the BOARD in the Makefile of the application.<br />
<br />
== Used Hardware ==<br />
<br />
[[Atmel SAM R21 Xplained Pro Evaluation Platform]]<br />
<br />
== Courses ==<br />
<br />
* [[Mobile and Embedded Security]] (2019)<br />
<br />
<br />
== References ==<br />
<br />
* https://github.com/RIOT-OS/RIOT/wiki<br />
* http://riot-os.org/api<br />
* https://github.com/RIOT-OS/Tutorials<br />
<br />
[[Category:Documentation]]</div>Silviehttps://wiki.elvis.science/index.php?title=Riot-OS_Setup&diff=7890Riot-OS Setup2021-10-13T14:37:39Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
Setting up Riot-OS on a Atmel SAM R21 Xpro Board.<br />
<br />
== Requirements ==<br />
<br />
* Operating system: Ubuntu 20.04 <br />
* Packages: git<br />
<br />
== Description ==<br />
<br />
=== Step 1 ===<br />
<br />
Install the following packages<br />
<br />
<br />
sudo apt-get update<br />
sudo apt-get install git <br />
openocd<br />
gcc-multilib<br />
build-essential<br />
python3-serial<br />
libudev-dev<br />
moserial<br />
<br />
=== Step 2 ===<br />
<br />
Install the toolchain<br />
<br />
sudo apt-get install gcc-arm-none-eabi<br />
<br />
If you use a recent version of RIOT-OS (Release-2021.07) you can go on with '''Step 3'''.<br />
<br />
<br />
If you use an older RIOT-OS version, you will have to do the following steps:<br />
<br />
Goto https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm and download<br />
<br />
gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2<br />
<br />
Move it to your home directory.<br />
<br />
Uninstall old packages<br />
<br />
sudo apt remove binutils-arm-none-eabi gcc-arm-none-eabi libnewlib-arm-none-eabi<br />
<br />
Unzip the downloaded file<br />
<br />
tar -xjvf gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2<br />
<br />
Add the toolchain to your path<br />
<br />
export PATH=$PATH:/home/(your user)/gcc-arm-none-eabi-7-2018-q2-update/bin/<br />
<br />
For now: you will have to do this in the bash where you build your application - after each restart.<br />
<br />
=== Step 3 ===<br />
<br />
Download Riot-OS<br />
<br />
git clone https://github.com/RIOT-OS/RIOT.git myRIOT<br />
<br />
Move to the "Hello World"-Example<br />
<br />
cd myRIOT/examples/hello-world<br />
<br />
Build the application on "native"<br />
<br />
make all term<br />
<br />
Now, you should see this output in your terminal:<br />
<br />
RIOT native interrupts/signals initialized.<br />
LED_RED_OFF<br />
LED_GREEN_ON<br />
RIOT native board initialized.<br />
RIOT native hardware initialization complete.<br />
<br />
main(): This is RIOT! (Version: 2022.01-devel-129-g554d3)<br />
Hello World!<br />
You are running RIOT on a(n) native board.<br />
This board features a(n) native MCU.<br />
<br />
=== Step 4 ===<br />
<br />
Build and run "Hello World" on the SAM R21 Board.<br />
<br />
Set the rights for your username to be able to flash the application on the board.<br />
<br />
sudo usermod -a -G dialout <username><br />
<br />
Then reboot your computer.<br />
<br />
Attach the antenna to the board - '''never use it without the antenna!''' Connect the board to your computer via micro USB cable (USB EDBG interface).<br />
<br />
[[File:samr21EDBGconnect.jpg]]<br />
<br />
Connect via Moserial.<br />
<br />
[[File:moSerial.jpg]]<br />
<br />
Build and flash the application.<br />
<br />
cd myRIOT/examples/hello-world<br />
make BOARD=samr21-xpro<br />
make BOARD=samr21-xpro flash<br />
<br />
If you do not use a serial terminal like moserial or terraterm use term<br />
<br />
make BOARD=samr21-xpro term<br />
<br />
You may also set the BOARD in the Makefile of the application.<br />
<br />
== Used Hardware ==<br />
<br />
[[Atmel SAM R21 Xplained Pro Evaluation Platform]]<br />
<br />
== Courses ==<br />
<br />
* [[Mobile and Embedded Security]] (2019)<br />
<br />
<br />
== References ==<br />
<br />
* https://github.com/RIOT-OS/RIOT/wiki<br />
* http://riot-os.org/api<br />
* https://github.com/RIOT-OS/Tutorials<br />
<br />
[[Category:Documentation]]</div>Silviehttps://wiki.elvis.science/index.php?title=Riot-OS_Setup&diff=7889Riot-OS Setup2021-10-13T14:36:53Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
Setting up Riot-OS on a Atmel SAM R21 Xpro Board.<br />
<br />
== Requirements ==<br />
<br />
* Operating system: Ubuntu 20.04 <br />
* Packages: git<br />
<br />
== Description ==<br />
<br />
=== Step 1 ===<br />
<br />
Install the following packages<br />
<br />
<br />
sudo apt-get update<br />
sudo apt-get install git <br />
openocd<br />
gcc-multilib<br />
build-essential<br />
python3-serial<br />
libudev-dev<br />
moserial<br />
<br />
=== Step 2 ===<br />
<br />
Install the toolchain<br />
<br />
sudo apt-get install gcc-arm-none-eabi<br />
<br />
If you use a recent version of RIOT-OS (Release-2021.07) you can go on with '''Step 3'''.<br />
<br />
<br />
If you use an older RIOT-OS version, you will have to do the following steps:<br />
<br />
Goto https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm and download<br />
<br />
gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2<br />
<br />
Move it to your home directory.<br />
<br />
Uninstall old packages<br />
<br />
sudo apt remove binutils-arm-none-eabi gcc-arm-none-eabi libnewlib-arm-none-eabi<br />
<br />
Unzip the downloaded file<br />
<br />
tar -xjvf gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2<br />
<br />
Add the toolchain to your path<br />
<br />
export PATH=$PATH:/home/(your user)/gcc-arm-none-eabi-7-2018-q2-update/bin/<br />
<br />
For now: you will have to do this in the bash where you build your application - after each restart.<br />
<br />
=== Step 3 ===<br />
<br />
Download Riot-OS<br />
<br />
git clone https://github.com/RIOT-OS/RIOT.git myRIOT<br />
<br />
Move to the "Hello World"-Example<br />
<br />
cd myRIOT/examples/hello-world<br />
<br />
Build the application on "native"<br />
<br />
make all term<br />
<br />
Now, you should see this output in your terminal:<br />
<br />
RIOT native interrupts/signals initialized.<br />
LED_RED_OFF<br />
LED_GREEN_ON<br />
RIOT native board initialized.<br />
RIOT native hardware initialization complete.<br />
<br />
main(): This is RIOT! (Version: 2022.01-devel-129-g554d3)<br />
Hello World!<br />
You are running RIOT on a(n) native board.<br />
This board features a(n) native MCU.<br />
<br />
=== Step 4 ===<br />
<br />
Build and run "Hello World" on the SAM R21 Board.<br />
<br />
Set the rights for your username to be able to flash the application on the board.<br />
<br />
sudo usermod -a -G dialout <username><br />
<br />
Then reboot your computer.<br />
<br />
Attach the antenna to the board - '''never use it without the antenna!''' Connect the board to your computer via micro USB cable (USB EDBG interface).<br />
<br />
[[File:samr21EDBGconnect.jpg]]<br />
<br />
Connect via Moserial.<br />
<br />
[[File:moSerial.jpg]]<br />
<br />
Build and flash the application.<br />
<br />
cd myRIOT/examples/hello-world<br />
make BOARD=samr21-xpro<br />
make BOARD=samr21-xpro flash<br />
<br />
If you do not use a serial terminal like moserial or terraterm use term<br />
<br />
make BOARD=samr21-xpro term<br />
<br />
You may also set the BOARD in the Makefile of the application.<br />
<br />
== Used Hardware ==<br />
<br />
[[Atmel SAM R21 Xplained Pro Evaluation Platform]]<br />
<br />
== Courses ==<br />
<br />
* [[Mobile and Embedded Security]] (2019)<br />
<br />
<br />
== References ==<br />
<br />
* https://github.com/RIOT-OS/RIOT/wiki<br />
* http://riot-os.org/api<br />
* https://github.com/RIOT-OS/Tutorials<br />
<br />
[[Category:Documentation]]</div>Silviehttps://wiki.elvis.science/index.php?title=Riot-OS_Setup&diff=7888Riot-OS Setup2021-10-13T14:34:46Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
Setting up Riot-OS on a Atmel SAM R21 Xpro Board.<br />
<br />
== Requirements ==<br />
<br />
* Operating system: Ubuntu 20.04 <br />
* Packages: git<br />
<br />
== Description ==<br />
<br />
=== Step 1 ===<br />
<br />
Install the following packages<br />
<br />
<br />
sudo apt-get update<br />
sudo apt-get install git <br />
openocd<br />
gcc-multilib<br />
build-essential<br />
python3-serial<br />
libudev-dev<br />
moserial<br />
<br />
=== Step 2 ===<br />
<br />
Install the toolchain<br />
<br />
sudo apt-get install gcc-arm-none-eabi<br />
<br />
If you use a recent version of RIOT-OS (Release-2021.07) you can go on with '''Step 3'''.<br />
<br />
<br />
If you use an older RIOT-OS version, you will have to do the following steps:<br />
<br />
Goto https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm and download<br />
<br />
gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2<br />
<br />
Move it to your home directory.<br />
<br />
Uninstall old packages<br />
<br />
sudo apt remove binutils-arm-none-eabi gcc-arm-none-eabi libnewlib-arm-none-eabi<br />
<br />
Unzip the downloaded file<br />
<br />
tar -xjvf gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2<br />
<br />
Add the toolchain to your path<br />
<br />
export PATH=$PATH:/home/(your user)/gcc-arm-none-eabi-7-2018-q2-update/bin/<br />
<br />
For now: you will have to do this in the bash where you build your application - after each restart.<br />
<br />
=== Step 3 ===<br />
<br />
Download Riot-OS<br />
<br />
git clone https://github.com/RIOT-OS/RIOT.git myRIOT<br />
<br />
Move to the "Hello World"-Example<br />
<br />
cd myRIOT/examples/hello-world<br />
<br />
Build the application on "native"<br />
<br />
make all term<br />
<br />
Now, you should see this output in your terminal:<br />
<br />
Release-2021.07<br />
<br />
=== Step 4 ===<br />
<br />
Build and run "Hello World" on the SAM R21 Board.<br />
<br />
<br />
Set the rights for your username to be able to flash the application on the board.<br />
<br />
sudo usermod -a -G dialout <username><br />
<br />
Then reboot your computer.<br />
<br />
Attach the antenna to the board - never use it without the antenna! Connect the board to your computer via micro USB cable (USB EDBG interface).<br />
<br />
[[File:samr21EDBGconnect.jpg]]<br />
<br />
Connect via Moserial.<br />
<br />
[[File:moSerial.jpg]]<br />
<br />
Build and flash the application.<br />
<br />
cd myRIOT/examples/hello-world<br />
make BOARD=samr21-xpro<br />
make BOARD=samr21-xpro flash<br />
<br />
If you do not use a serial terminal like moserial or terraterm use term<br />
<br />
make BOARD=samr21-xpro term<br />
<br />
You may also set the BOARD in the Makefile of the application.<br />
<br />
== Used Hardware ==<br />
<br />
[[Atmel SAM R21 Xplained Pro Evaluation Platform]]<br />
<br />
== Courses ==<br />
<br />
* [[Mobile and Embedded Security]] (2019)<br />
<br />
<br />
== References ==<br />
<br />
* https://github.com/RIOT-OS/RIOT/wiki<br />
* http://riot-os.org/api<br />
* https://github.com/RIOT-OS/Tutorials<br />
<br />
[[Category:Documentation]]</div>Silviehttps://wiki.elvis.science/index.php?title=Riot-OS_Setup&diff=7887Riot-OS Setup2021-10-13T13:34:46Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
Setting up Riot-OS on a Atmel SAM R21 Xpro Board.<br />
<br />
== Requirements ==<br />
<br />
* Operating system: Ubuntu 20.04 <br />
* Packages: git<br />
<br />
== Description ==<br />
<br />
=== Step 1 ===<br />
<br />
Install the following packages<br />
<br />
<br />
sudo apt-get update<br />
sudo apt-get install git <br />
make<br />
openocd<br />
gcc-multilib<br />
build-essential<br />
python´3-serial<br />
libudev-dev<br />
moserial<br />
<br />
=== Step 2 ===<br />
<br />
Install the toolchain<br />
<br />
Goto https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm and download<br />
<br />
gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2<br />
<br />
Move it to your home directory.<br />
<br />
Uninstall old packages<br />
<br />
sudo apt remove binutils-arm-none-eabi gcc-arm-none-eabi libnewlib-arm-none-eabi<br />
<br />
Unzip the downloaded file<br />
<br />
tar -xjvf gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2<br />
<br />
Add the toolchain to your path<br />
<br />
export PATH=$PATH:/home/(your user)/gcc-arm-none-eabi-7-2018-q2-update/bin/<br />
<br />
For now: you will have to do this in the bash where you build your application - after each restart.<br />
<br />
=== Step 3 ===<br />
<br />
Download Riot-OS<br />
<br />
git clone https://github.com/RIOT-OS/RIOT.git myRIOT<br />
<br />
=== Step 4 ===<br />
<br />
Build and run "Hello World" on the SAM R21 Board.<br />
<br />
<br />
Set the rights for your username to be able to flash the application on the board.<br />
<br />
sudo usermod -a -G dialout <username><br />
<br />
Then reboot your computer.<br />
<br />
Attach the antenna to the board - never use it without the antenna! Connect the board to your computer via micro USB cable (USB EDBG interface).<br />
<br />
[[File:samr21EDBGconnect.jpg]]<br />
<br />
Connect via Moserial.<br />
<br />
[[File:moSerial.jpg]]<br />
<br />
Build and flash the application.<br />
<br />
cd myRIOT/examples/hello-world<br />
make BOARD=samr21-xpro<br />
make BOARD=samr21-xpro flash<br />
<br />
If you do not use a serial terminal like moserial or terraterm use term<br />
<br />
make BOARD=samr21-xpro term<br />
<br />
You may also set the BOARD in the Makefile of the application.<br />
<br />
== Used Hardware ==<br />
<br />
[[Atmel SAM R21 Xplained Pro Evaluation Platform]]<br />
<br />
== Courses ==<br />
<br />
* [[Mobile and Embedded Security]] (2019)<br />
<br />
<br />
== References ==<br />
<br />
* https://github.com/RIOT-OS/RIOT/wiki<br />
* http://riot-os.org/api<br />
* https://github.com/RIOT-OS/Tutorials<br />
<br />
[[Category:Documentation]]</div>Silviehttps://wiki.elvis.science/index.php?title=Riot-OS_Setup&diff=7886Riot-OS Setup2021-10-13T12:07:49Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
Setting up Riot-OS on a Atmel SAM R21 Xpro Board.<br />
<br />
== Requirements ==<br />
<br />
* Operating system: Ubuntu 18.04 bionic amd64<br />
* Packages: git<br />
<br />
== Description ==<br />
<br />
=== Step 1 ===<br />
<br />
Install the following packages<br />
<br />
<br />
sudo apt-get update<br />
sudo apt-get install git <br />
make<br />
openocd<br />
gcc-multilib<br />
build-essential<br />
python-serial<br />
libudev-dev<br />
moserial<br />
<br />
=== Step 2 ===<br />
<br />
Install the toolchain<br />
<br />
Goto https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm and download<br />
<br />
gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2<br />
<br />
Move it to your home directory.<br />
<br />
Uninstall old packages<br />
<br />
sudo apt remove binutils-arm-none-eabi gcc-arm-none-eabi libnewlib-arm-none-eabi<br />
<br />
Unzip the downloaded file<br />
<br />
tar -xjvf gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2<br />
<br />
Add the toolchain to your path<br />
<br />
export PATH=$PATH:/home/(your user)/gcc-arm-none-eabi-7-2018-q2-update/bin/<br />
<br />
For now: you will have to do this in the bash where you build your application - after each restart.<br />
<br />
=== Step 3 ===<br />
<br />
Download Riot-OS<br />
<br />
git clone https://github.com/RIOT-OS/RIOT.git myRIOT<br />
<br />
=== Step 4 ===<br />
<br />
Build and run "Hello World" on the SAM R21 Board.<br />
<br />
<br />
Set the rights for your username to be able to flash the application on the board.<br />
<br />
sudo usermod -a -G dialout <username><br />
<br />
Then reboot your computer.<br />
<br />
Attach the antenna to the board - never use it without the antenna! Connect the board to your computer via micro USB cable (USB EDBG interface).<br />
<br />
[[File:samr21EDBGconnect.jpg]]<br />
<br />
Connect via Moserial.<br />
<br />
[[File:moSerial.jpg]]<br />
<br />
Build and flash the application.<br />
<br />
cd myRIOT/examples/hello-world<br />
make BOARD=samr21-xpro<br />
make BOARD=samr21-xpro flash<br />
<br />
If you do not use a serial terminal like moserial or terraterm use term<br />
<br />
make BOARD=samr21-xpro term<br />
<br />
You may also set the BOARD in the Makefile of the application.<br />
<br />
== Used Hardware ==<br />
<br />
[[Atmel SAM R21 Xplained Pro Evaluation Platform]]<br />
<br />
== Courses ==<br />
<br />
* [[Mobile and Embedded Security]] (2019)<br />
<br />
<br />
== References ==<br />
<br />
* https://github.com/RIOT-OS/RIOT/wiki<br />
* http://riot-os.org/api<br />
* https://github.com/RIOT-OS/Tutorials<br />
<br />
[[Category:Documentation]]</div>Silviehttps://wiki.elvis.science/index.php?title=Main_Page&diff=6631Main Page2021-04-08T21:59:40Z<p>Silvie: </p>
<hr />
<div>This Wiki contains documentations from the ELVIS project.<br />
<br />
{| style="margin: auto;"<br />
|-<br />
| [[File:ElvisLogo.png]]<br />
|}<br />
<br />
You can find a [[:Category:Hardware|List of available hardware]] as well as a list of [[:Category:Documentation|documentations]].<br />
<br />
== Acknowledgments ==<br />
<br />
The ELVIS project is generously funded by the MA23<br />
<br />
{| style="margin: auto;"<br />
|-<br />
| [[File:Ma23 funded.png|300px]]<br />
|}</div>Silviehttps://wiki.elvis.science/index.php?title=Main_Page&diff=6630Main Page2021-04-08T21:59:27Z<p>Silvie: </p>
<hr />
<div>This Wiki contains documentations from the ELVIS project.<br />
<br />
{| style="margin: auto;"<br />
|-<br />
| [[File:ElvisLogo.png]]<br />
|}<br />
<br />
You can find a [[:Category:Hardware|List of available hardware]] as well as a list of [[:Category:Documentation|documentations]].<br />
<br />
== Acknowledgments ==<br />
<br />
The ELVIS project is generously funded by the MA23<br />
<br />
{| style="margin: auto;"<br />
|-<br />
| [[File:Ma23 funded.png|150px]]<br />
|}</div>Silviehttps://wiki.elvis.science/index.php?title=File:Ma23_funded.png&diff=6629File:Ma23 funded.png2021-04-08T21:58:57Z<p>Silvie: </p>
<hr />
<div></div>Silviehttps://wiki.elvis.science/index.php?title=Proxmark3:_Installation&diff=6628Proxmark3: Installation2021-04-02T13:41:11Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
Installation of [[Proxmark3 RDV2 Kit|Proxmark3]] on macOS, Linux and Windows for RFID and NFC sniffing.<br />
<br />
<pre style="color: red"><br />
To use the Bluetooth Module of the Proxmark3 RDV4 you need to install the https://github.com/RfidResearchGroup/proxmark3.git repository<br />
<br />
For installing on Linux please visit https://github.com/RfidResearchGroup/proxmark3/blob/master/doc/md/Installation_Instructions/Linux-Installation-Instructions.md<br />
</pre><br />
<br />
== MacOS installation == <br />
<br />
=== Requirements ===<br />
<br />
Xcode (AppStore) is a must.<br />
<br />
In addition to make the installation easier have either HomeBrew or MacPorts ready.<br />
A Tutorial for installing:<br />
A) HomeBrew: https://docs.brew.sh/Installation<br />
B) MacPorts: https://www.macports.org/install.php<br />
<br />
Because of their different architecture (HomeBrew/MacPorts), some parts of this tutorial are split into:<br />
A) Installation with HomeBrew<br />
B) Installation with MacPorts<br />
Just choose the tutorial that suits your current setup.<br />
<br />
=== Installation with HomeBrew ===<br />
<br />
1. Download ("tap") the proxmark repository:<br />
<br />
brew tap proxmark/proxmark3<br />
<br />
2. Install proxmark3:<br />
<br />
brew install proxmark3<br />
<br />
=== Manual Installation ===<br />
<br />
Download the drivers and install them.<br />
If you have MacPorts:<br />
<br />
sudo port install p7zip readline libusb libusb-compat perl5 wget qt5\\ arm-none-eabi-gcc pkgconfig<br />
<br />
If you have HomeBrew:<br />
<br />
brew tap nitsky/stm32<br />
brew install readline libusb p7zip libusb-compat wget qt5 pkgconfig\\ arm-none-eabi-gcc<br />
<br />
Now you will need to add QT to the PKG_CONFIG_PATH so it find QT5 (replace YOUR_VERSION with your version number:<br />
<br />
export\\ PKG_CONFIG_PATH=/usr/local/Cellar/qt5/<<YOUR_VERSION>>/lib/pkgconfig/<br />
<br />
3. And add moc_location in Qt5Core.pc file:<br />
<br />
export QT_PKG_CONFIG_QT5CORE=$(find /usr -name Qt5Core.pc 2>/dev/null)<br />
chmod 666 $QT_PKG_CONFIG_QT5CORE<br />
echo "moc_location=\${prefix}/bin/moc" >> $QT_PKG_CONFIG_QT5CORE<br />
chmod 444 $QT_PKG_CONFIG_QT5CORE<br />
<br />
4. For link creation to avoid any errors of "readline" (may happen):<br />
<br />
brew link --force readline<br />
<br />
5. Now either git clone or manually download the Proxmark project. Git clone:<br />
<br />
git clone https://github.com/Proxmark/proxmark3.git<br />
<br />
6. "cd" to the proxmark3 folder<br />
<br />
7. Now jump to the section "Connecting your Proxmark"<br />
<br />
=== Connecting your Proxmark ===<br />
<br />
1. Insert your Proxmark and run<br />
<br />
system_profiler SPUSBDataType<br />
<br />
2.a) If your Proxmark is CDC you should somewhere see in the output:<br />
<br />
Product ID: 0x504d<br />
Vendor ID: 0x2d2d<br />
<br />
2.b) If your Proxmark is an HID device you should see:<br />
<br />
Product ID: 0x4b8f<br />
Vendor ID: 0x9ac4<br />
<br />
If it is an HID Device you will need to upgrade it, then go to "Upgrading my Proxmark HID->CDC"<br />
If you have an CDC Proxmark you can jump to "Finish Line"<br />
<br />
=== Upgrading my Proxmark HID->CDC ===<br />
<br />
1. Compile the bootrom, OS and software:<br />
<br />
make clean; make<br />
<br />
2. Also compile the HID compatible flash program:<br />
<br />
cd client/hid-flasher;make<br />
<br />
3. Disconnect Apple's HID driver, by installing a dummy kernel driver:<br />
<br />
sudo make install_kext<br />
sudo kextcache -system-caches<br />
<br />
4. Keep the Proxmark button pressed while reconnecting it to USB. Its yellow and red lights should light up (you can release the button after 5-ish seconds).<br />
<br />
5. Now upgrade the bootrom:<br />
<br />
./flasher -b ../../bootrom/obj/bootrom.elf<br />
<br />
6. cd ../..<br />
<br />
7. Disconnect your proxmark and keep the button pressed while reconnecting to USB.<br />
<br />
8. While keeping the button pressed run to get the device name:<br />
<br />
ls /dev/cu*<br />
<br />
You should find a name like "/dev/cu.usbmodem####" (#### represents a number).<br />
<br />
9. While still KEEPING PRESSED the button update the FPGA and its OS:<br />
<br />
./client/flasher /dev/cu.usbmodem#### armsrc/obj/fullimage.elf<br />
<br />
10. Disconnect the proxmark and release the button.<br />
<br />
11. Now reconnect your proxmark to USB and run it:<br />
<br />
cd proxmark3/client<br />
./proxmark3 /dev/cu.usbmodem####<br />
<br />
No need to go to "Finish Line", you are already finished with setting up the Proxmark Environment<br />
<br />
=== Finish Line ===<br />
<br />
1. Compile the bootrom and OS:<br />
<br />
make clean; make<br />
<br />
2. Disconnect your Proxmark from USB. Then keep the button pressed while reconnecting it back to USB. You can release the button when you see yellow/orange and red lights on your proxmark. (If you have an Elechouse v2 Proxmark3 or Elechouse v3 Proxmark3 Easy you do not need to press the button)<br />
<br />
3. Figure out your device name:<br />
<br />
ls /dev/cu*<br />
<br />
It should be something with /dev/cu.usbmodem#### (#### represents a number).<br />
<br />
4. After you have found your device run the program:<br />
<br />
cd proxmark3/client<br />
./proxmark3 /dev/cu.usbmodem####<br />
<br />
== Linux installation ==<br />
<br />
=== Requirements ===<br />
<br />
* Operating system: Ubuntu 16.04 trusty amd64<br />
<br />
=== Step 1 Compile resources:===<br />
<br />
1. download and install some needed packages and libs<br />
<br />
sudo apt-get install p7zip git build-essential libreadline5 libreadline-dev libusb-0.1-4 libusb-dev libqt4-dev perl pkg-config wget libncurses5-dev gcc-arm-none-eabi libstdc++-arm-none-eabi-newlib<br />
<br />
2. clone proxmark3 git repository<br />
<br />
git clone https://github.com/proxmark/proxmark3.git<br />
<br />
3. enter repo<br />
<br />
cd proxmark3<br />
<br />
4. get newest version<br />
<br />
git pull<br />
<br />
5. Install the blacklist rules<br />
<br />
sudo cp -rf driver/77-mm-usb-device-blacklist.rules /etc/udev/rules.d/77-mm-usb-device-blacklist.rules<br />
sudo udevadm control --reload-rules<br />
<br />
6. add current user to group<br />
<br />
sudo adduser $USER dialout<br />
<br />
7. log out and log into your account<br />
<br />
8. compile proxmark3<br />
<br />
make clean && make all<br />
<br />
=== Step 2 Identify proxmark3 device ===<br />
<br />
dmesg | grep -i usb<br />
[ 9704.503904] usb 1-3: Manufacturer: proxmark.org<br />
[ 9704.539638] cdc_acm 1-3:1.0: ttyACM0: USB ACM device<br />
<br />
=== Step 3 Flash the firmware of the proxmark ===<br />
<br />
!!! Do '''NOT''' press enter during the flashing process !!!<br />
<br />
./client/flasher /dev/ttyACM0 -b bootrom/obj/bootrom.elf armsrc/obj/fullimage.elf<br />
<br />
=== Step 4 Start the proxmark3 client ===<br />
<br />
./client/proxmark3 /dev/ttyACM0<br />
<br />
== Windows installation ==<br />
<br />
=== Requirements ===<br />
The tested Version for Windows was Windows 10, therefore the requirements for successfully completing our installation guide are:<br />
* Windows 10<br />
* [https://git-scm.com/download/win Git for Windows]<br />
<br />
=== Installation ===<br />
In order to be able to connect to your Proxmark3 under Windows you need to emulate a Linux environment which is done through a tool called ProxSpace.<br />
<br />
1. First you need to download the download the ProxSpace Repository through git.<br />
<br />
'''Caution!''' Your current working directory should contain no whitespaces!<br />
<br />
git clone https://github.com/Gator96100/ProxSpace.git<br />
<br />
2. Inside your ProxSpace Folder you should find "runme.bat". Start it.<br />
<br />
3. This will create and install all necessary packets and folders. After you should see the pm3-console.<br />
<br />
4. From this console you should change the directory to ProxSpace and download the Proxmark3 Repository:<br />
<br />
git clone https://github.com/Proxmark/proxmark3.git<br />
<br />
5. After this process is complete, cd to the proxmark3 directory:<br />
<br />
cd proxmark3<br />
<br />
6. Compile the proxmark3 project:<br />
<br />
make clean && make all<br />
<br />
7. Install the proxmark3 driver<br />
<br />
==== Windows 10 ====<br />
Since this driver is not officially signed by a trusted authority the installation is a bit tricky. You first have to start Windows in save-mode. This is done easiest, when pressing the shift-key while restarting your PC. On reboot you choose Startup-Settings followed by #7 Disable driver signature enforcement.<br />
After the computer restarted you connect the proxmark3 and go to the device manager, right click on the non-identified device (which is the proxmark3) and go to the settings. Click on update driver and search locally for the proxmark3.inf. If you have trouble getting the proxmark3 driver to work, please visit this [[https://store.ryscc.com/blogs/news/how-to-install-a-proxmark3-driver-on-windows-10 picture-guided tutorial]]<br />
<br />
<br />
After, the installation should be complete and you can safely restart your PC to normal mode again. From there start the runme.bat and the pm3-console should appear.<br />
<br />
==== Windows 7 ====<br />
[[File:Win7-disable-driversignature.png|520px|right]]<br />
<br />
* Start command prompt (cmd.exe) as '''administrator''' and execute:<br />
<br />
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS<br />
bcdedit.exe -set TESTSIGNING ON<br />
<br />
* Open the device manager, right-click on the unknow device "proxmark3" and select "update"<br />
* Select the manual driver selection, and within your ''ProxSpace'' folder select the ''msys2\proxmark3\driver'' subfolder<br />
<br />
After the successful driver setup you may want to disable testsigning again, and restart windows<br />
<br />
bcdedit.exe -set TESTSIGNING OFF<br />
<br />
=== Update your Proxmark3 ===<br />
<br />
To update the firmware of your Proxmark3 to the latest version, open cmd and type in (with x standing for the right number of your COM port, e.g. COM2):<br />
<br />
./proxmark/client/flasher COMx -b /bootrom/obj/bootrom.elf<br />
./proxmark/client/flasher COMX ./armsrc/obj/fullimage.elf<br />
<br />
=== Connecting to your Proxmark3 ===<br />
<br />
After having done all the steps above you can safely connect to your Proxmark3 through (where x again stands for the right number of your COM port, e.g. COM2):<br />
<br />
./client/proxmark3.exe COMx<br />
<br />
== Usage ==<br />
<br />
For using the Proxmark3 please visit our second documentation [[Proxmark3: Useful commands]] and feel free to have a look at the [https://github.com/Proxmark/proxmark3 Proxmark Repository!]<br />
<br />
== Resources and Tutorials ==<br />
<br />
* Client commands: https://github.com/Proxmark/proxmark3/wiki/commands<br />
* Usage example: https://www.youtube.com/watch?v=FODGYfhqb4Q<br />
* Basic tutorial for RFID usage: https://blog.kchung.co/rfid-hacking-with-the-proxmark-3/<br />
* Advanced tutorial: https://blog.kchung.co/rfid-hacking-with-the-proxmark-3/<br />
* Capture NFC traffic of apple pay transaction: https://salmg.net/2017/12/29/analyzing-an-apple-pay-transaction-with-proxmark3/<br />
<br />
== Used Hardware ==<br />
<br />
[[Proxmark 3]]<br />
<br />
== References ==<br />
* Product page and infos: https://www.elechouse.com/elechouse/index.php?main_page=product_info&cPath=90_93&products_id=2264&zenid=kmvhiob7nq1orc4pfjtf53sbr7<br />
* Manual: https://www.elechouse.com/elechouse/images/product/proxmark3_V2/Proxmark3%20V2%20User%20Guid.pdf<br />
* MacOS 10.x client installation: https://github.com/Proxmark/proxmark3/wiki/MacOS<br />
* Linux 16.04 client installation: https://github.com/Proxmark/proxmark3/wiki/Ubuntu-Linux<br />
* Windows 10 client installation: https://github.com/Proxmark/proxmark3/wiki/Windows<br />
<br />
[[Category:Documentation]]</div>Silviehttps://wiki.elvis.science/index.php?title=Proxmark3:_FHCW_Card_Security_Evaluation&diff=6627Proxmark3: FHCW Card Security Evaluation2021-04-01T15:57:12Z<p>Silvie: </p>
<hr />
<div>== Zusammenfassung == <br />
<br />
In unserer Arbeit wird gezegt, dass der größte Teil der Implementationen des FH-Campus-Karten-Systems gravierende Schwachstellen besitzt und diese mittels modifiziertem Proxmark3 Repository relativ schnell ausgenutzt werden können. Somit ist man in der Lage mit dem [[:File:iso14443a.zip|SourceCodes]] sich als beliebiger Nutzer an dem Drucker, Getränke und Snack-Automaten anzumelden und damit zu zahlen.<br />
<br />
Genauere Dokumentation findet man hier:<br />
[[:File:Proxmark.pdf|Proxmark3: Securityanalyse der Universitätsausweise]]<br />
<br />
== Anforderungen ==<br />
<br />
* Betriebssystem:<br />
** Ubuntu 16.04/18.03<br />
** Windows 10<br />
** MacOS 10.x<br />
* Proxmark3<br />
<br />
Folgende Dokumentation ist hilfreich, jedoch nicht zwingend notwendig, da im [[:File:Proxmark.pdf|Paper]] genauer darauf eingegangen wird:<br />
* [[Proxmark3: Installation]]<br />
* [[Proxmark3: Useful commands]]<br />
<br />
== Beschreibung ==<br />
<br />
Dieses Projekt beschäftigt sich mit der Analyse und Sicherheit kontaktloser Karten (NFC). Dabei wird das Gerät Proxmark3 zur Hilfe genommen, um die Daten von kontaktlosen Karten mitzulesen und um mit diesen Karten zu kommunizieren.<br />
<br />
In dieser Arbeit wird zunächst kurz die NFC-Technologie erläutert, die diese kontaktlose Identifikation ermöglicht. Danach gehen wir auf die unterschiedlichen Problemzonen und Schwachstellen dieser Technologie ein und erarbeiten die möglichen Angriffsvektoren.<br />
<br />
Im Anschluss daran wird dieses Wissen in die Tat umgesetzt, indem wir eine Arbeitsumgebung für den Proxmark3 aufsetzen und zunächst die simplere RFID Karte Mifare Classic analysieren und die Schwächen dieses Typen inspizieren. Daraufhin wenden wir uns der Weiterentwickelten Karte, namens Mifare Plus S, die den Kartentyp unserer Universität widerspiegelt. Die gewonnenen Erkenntnisse werden genutzt, um das Kartensystem an der Universität auf ihre Sicherheit zu überprüfen.<br />
<br />
* [[:File:Proxmark.pdf|Results.pdf]]<br />
* [[:File:iso14443a.zip|SourceCode.c]]<br />
<br />
== Benutzte Hardware ==<br />
<br />
[[Proxmark 3]]<br />
<br />
== Kurse ==<br />
<br />
* [[Einführendes Wahlfachprojekt]] (2019)<br />
<br />
== Authoren ==<br />
<br />
* Ostrowski, John<br />
* Arseven, Can<br />
<br />
== Referenzen ==<br />
<br />
siehe [[File:Proxmark.pdf]]</div>Silviehttps://wiki.elvis.science/index.php?title=Proxmark3:_FHCW_Card_Security_Evaluation&diff=6626Proxmark3: FHCW Card Security Evaluation2021-04-01T15:47:36Z<p>Silvie: Created page with "== Zusammenfassung == In unserer Arbeit wird gezegt, dass der größte Teil der Implementationen des FH-Campus-Karten-Systems gravierende Schwachstellen besitzt und diese mi..."</p>
<hr />
<div>== Zusammenfassung == <br />
<br />
In unserer Arbeit wird gezegt, dass der größte Teil der Implementationen des FH-Campus-Karten-Systems gravierende Schwachstellen besitzt und diese mittels modifiziertem Proxmark3 Repository relativ schnell ausgenutzt werden können. Somit ist man in der Lage mit dem [[:File:iso14443a.zip|SourceCodes]] sich als beliebiger Nutzer an dem Drucker, Getränke und Snack-Automaten anzumelden und damit zu zahlen.<br />
<br />
Genauere Dokumentation findet man hier:<br />
[[:File:Proxmark.pdf|Proxmark3: Securityanalyse der Universitätsausweise]]<br />
<br />
== Anforderungen ==<br />
<br />
* Betriebssystem:<br />
** Ubuntu 16.04/18.03<br />
** Windows 10<br />
** MacOS 10.x<br />
* Proxmark3<br />
<br />
Folgende Dokumentation ist hilfreich, jedoch nicht zwingend notwendig, da im [[:File:Proxmark.pdf|Paper]] genauer darauf eingegangen wird:<br />
* [[Proxmark3: Installation]]<br />
* [[Proxmark3: Useful commands]]<br />
<br />
== Beschreibung ==<br />
<br />
Dieses Projekt beschäftigt sich mit der Analyse und Sicherheit kontaktloser Karten (NFC). Dabei wird das Gerät Proxmark3 zur Hilfe genommen, um die Daten von kontaktlosen Karten mitzulesen und um mit diesen Karten zu kommunizieren.<br />
<br />
In dieser Arbeit wird zunächst kurz die NFC-Technologie erläutert, die diese kontaktlose Identifikation ermöglicht. Danach gehen wir auf die unterschiedlichen Problemzonen und Schwachstellen dieser Technologie ein und erarbeiten die möglichen Angriffsvektoren.<br />
<br />
Im Anschluss daran wird dieses Wissen in die Tat umgesetzt, indem wir eine Arbeitsumgebung für den Proxmark3 aufsetzen und zunächst die simplere RFID Karte Mifare Classic analysieren und die Schwächen dieses Typen inspizieren. Daraufhin wenden wir uns der Weiterentwickelten Karte, namens Mifare Plus S, die den Kartentyp unserer Universität widerspiegelt. Die gewonnenen Erkenntnisse werden genutzt, um das Kartensystem an der Universität auf ihre Sicherheit zu überprüfen.<br />
<br />
* [[:File:Proxmark.pdf|Results.pdf]]<br />
* [[:File:iso14443a.zip|SourceCode.c]]<br />
<br />
== Benutzte Hardware ==<br />
<br />
[[Proxmark 3]]<br />
<br />
== Kurse ==<br />
<br />
* [[Einführendes Wahlfachprojekt]] (2019)<br />
<br />
== Authoren ==<br />
<br />
* Ostrowski, John<br />
* Arseven, Can<br />
<br />
== Referenzen ==<br />
<br />
siehe [[File:Proxmark.pdf]]<br />
<br />
[[Category:Documentation]]</div>Silviehttps://wiki.elvis.science/index.php?title=NoNameArticle&diff=6625NoNameArticle2021-04-01T15:41:27Z<p>Silvie: Silvie moved page NoNameArticle to Proxmark3: FH-Campus Card NFC Security Valuation: revert</p>
<hr />
<div>#REDIRECT [[Proxmark3: FH-Campus Card NFC Security Valuation]]</div>Silviehttps://wiki.elvis.science/index.php?title=Proxmark3:_FH-Campus_Card_NFC_Security_Valuation&diff=6624Proxmark3: FH-Campus Card NFC Security Valuation2021-04-01T15:41:27Z<p>Silvie: Silvie moved page NoNameArticle to Proxmark3: FH-Campus Card NFC Security Valuation: revert</p>
<hr />
<div></div>Silviehttps://wiki.elvis.science/index.php?title=Category:Security/Crypto&diff=6623Category:Security/Crypto2021-03-24T15:34:14Z<p>Silvie: </p>
<hr />
<div>All ELVIS-'''devices''' providing Cryptography or Security testing abilities.</div>Silviehttps://wiki.elvis.science/index.php?title=Category:IoT_Development&diff=6622Category:IoT Development2021-03-24T15:33:55Z<p>Silvie: </p>
<hr />
<div>'''Devices''' used for IoT development available in the ELVIS lab.</div>Silviehttps://wiki.elvis.science/index.php?title=Category:Networking&diff=6621Category:Networking2021-03-24T15:33:34Z<p>Silvie: </p>
<hr />
<div>'''Devices''' used for Networking available in the ELVIS lab.</div>Silviehttps://wiki.elvis.science/index.php?title=Category:Smart_Home&diff=6620Category:Smart Home2021-03-24T15:33:21Z<p>Silvie: </p>
<hr />
<div>'''Devices''' used in Smart Homes available in the ELVIS lab.</div>Silviehttps://wiki.elvis.science/index.php?title=Category:Hardware&diff=6619Category:Hardware2021-03-24T15:33:00Z<p>Silvie: </p>
<hr />
<div>Here you can find the '''entire hardware''', i.e. '''all devices''' available in the ELVIS lab.</div>Silviehttps://wiki.elvis.science/index.php?title=Category:Documentation&diff=6618Category:Documentation2021-03-24T15:32:24Z<p>Silvie: </p>
<hr />
<div>'''All documentations''' created by students, researchers, and lecturers for the ELVIS project.<br />
<br />
<inputbox><br />
type=create<br />
width=100<br />
break=no<br />
buttonlabel=Create a new documentation<br />
default=(Article title)<br />
preload=Template:Documentation<br />
</inputbox></div>Silviehttps://wiki.elvis.science/index.php?title=Category:Security/Crypto&diff=6617Category:Security/Crypto2021-03-24T15:31:00Z<p>Silvie: </p>
<hr />
<div>All ELVIS-'''devices''' providing cryptography or security testing abilities.</div>Silviehttps://wiki.elvis.science/index.php?title=Category:Literature&diff=6615Category:Literature2021-03-24T15:23:55Z<p>Silvie: </p>
<hr />
<div>This page contains '''books and magazines''', which you can lend from ElvisLab.</div>Silviehttps://wiki.elvis.science/index.php?title=Category:IoT_Development&diff=6614Category:IoT Development2021-03-24T15:22:43Z<p>Silvie: </p>
<hr />
<div>A list of '''devices''' used for IoT development available in the ELVIS lab.</div>Silviehttps://wiki.elvis.science/index.php?title=Category:Hardware&diff=6613Category:Hardware2021-03-24T15:22:23Z<p>Silvie: </p>
<hr />
<div>A list of the '''entire hardware''', i.e. '''all devices''' available in the ELVIS lab.</div>Silviehttps://wiki.elvis.science/index.php?title=Category:Networking&diff=6612Category:Networking2021-03-24T15:21:59Z<p>Silvie: </p>
<hr />
<div>A list of '''devices''' used for Networking available in the ELVIS lab.</div>Silviehttps://wiki.elvis.science/index.php?title=Category:Smart_Home&diff=6611Category:Smart Home2021-03-24T15:21:42Z<p>Silvie: </p>
<hr />
<div>A list of '''devices''' used in Smart Homes available in the ELVIS lab.</div>Silviehttps://wiki.elvis.science/index.php?title=Category:Hardware&diff=6610Category:Hardware2021-03-24T15:21:03Z<p>Silvie: </p>
<hr />
<div>A list of the '''entire hardware''' available in the ELVIS lab.</div>Silviehttps://wiki.elvis.science/index.php?title=Category:Documentation&diff=6609Category:Documentation2021-03-24T15:20:17Z<p>Silvie: </p>
<hr />
<div>A list of '''all documentations''' created by the ELVIS project.<br />
<br />
<inputbox><br />
type=create<br />
width=100<br />
break=no<br />
buttonlabel=Create a new documentation<br />
default=(Article title)<br />
preload=Template:Documentation<br />
</inputbox></div>Silviehttps://wiki.elvis.science/index.php?title=Category:Basic&diff=6608Category:Basic2021-03-24T15:19:50Z<p>Silvie: </p>
<hr />
<div><br />
Here you find '''documentations''' regarding fundamental topics, basics, and setup tutorials.</div>Silviehttps://wiki.elvis.science/index.php?title=Category:Pentesting&diff=6607Category:Pentesting2021-03-24T15:16:54Z<p>Silvie: </p>
<hr />
<div>This page shows '''documentations''' regarding software and hardware used for penetration testing.</div>Silviehttps://wiki.elvis.science/index.php?title=Proxmark3:_Useful_commands&diff=6587Proxmark3: Useful commands2021-03-19T15:06:46Z<p>Silvie: Protected "Proxmark3: Useful commands" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))</p>
<hr />
<div>== Summary == <br />
<br />
"NFC Hacking with Proxmark3" has been conducted during a school project, in which we analyzed the implementation of our NFC System. Which includes our on-campus cards, the printing system, snacks and drinks machines and the classroom doors. The additional output of this project was a (tested) guide on how to install the Proxmark3. For further details with regards to our project, concrete tests and more advanced commands please see our documentation [[Proxmark3: FH-Campus Card NFC Security Valuation]].<br />
<br />
In this thread we show a short overview of the different commands the proxmark3 environment has to offer.<br />
<br />
== Requirements ==<br />
<br />
Please see the [[Proxmark3: Installation]] guide for a full overview of requirements.<br />
However, the Operating systems on which we tested the installation are: <br />
*Ubuntu 16.04/18.03<br />
*Windows 10<br />
*MacOS 10.x<br />
<br />
In order to complete the "Introduction" described below, you have to complete the [[Proxmark3: Installation]] guide first.<br />
<br />
This overview is based on the proxmark3 client, published on Github on the 29. May 2019<br />
<br />
== Introduction ==<br />
<br />
This introduction should only give you a glimpse of the available commands and possibilities of the Proxmark3. The official Proxmark3-Repository, as well as the more advanced Ice-Man-Fork Repository (both linked in the reference section), provide lots of functions, though most of them are still in their alpha stage and therefore still need a bit of tinkering in order to work well. For further commands and our security analysis of our university feel free to have a look at our documentation!<br />
<br />
=== The Commands ===<br />
<br />
Connect via:<br />
: Linux: <code>./client/proxmark3 /dev/ttyACM0</code><br />
: Windows <code>./client/proxmark3.exe COMx</code><br />
<br />
After you have successfully completed the Install Proxmark3 guide, you should see a screen similar to this when connecting to your proxmark3:<br />
<br />
proxmark3><br />
<br />
You can always (in whichever menu you are) type 'help' in order to have a full list of available commands in that menu.<br />
If you enter help in the start menu, you will get following output:<br />
help This help. Use '<command> help' for details of a particular command.<br />
data { Plot window / data buffer manipulation... }<br />
hf { High Frequency commands... }<br />
hw { Hardware commands... }<br />
lf { Low Frequency commands... }<br />
emv { EMV iso14443 and iso7816... }<br />
sc { Smartcard commands... }<br />
script { Scripting commands }<br />
quit Exit program<br />
exit Exit program<br />
<br />
==== command: hw ====<br />
<br />
"hw" stands for hardware and lists a bunch of commands to get basic hardware information of the Proxmark3.<br />
<br />
detectreader ['l'|'h'] -- Detect external reader field (option 'l' or 'h' to limit to LF or HF)<br />
fpgaoff Set FPGA off<br />
lcd <HEX command> <count> -- Send command/data to LCD<br />
lcdreset Hardware reset LCD<br />
readmem [address] -- Read memory at decimal address from flash<br />
reset Reset the Proxmark3<br />
setlfdivisor <19 - 255> -- Drive LF antenna at 12Mhz/(divisor+1)<br />
setmux <loraw|hiraw|lopkd|hipkd> -- Set the ADC mux to a specific value<br />
tune ['l'|'h'] -- Measure antenna tuning (option 'l' or 'h' to limit to LF or HF)<br />
version Show version information about the connected Proxmark<br />
status Show runtime status information about the connected Proxmark<br />
ping Test if the pm3 is responsive<br />
<br />
We can check the version of the different builds of the Proxmark3 currently running on it:<br />
<br />
proxmark3> hw version<br />
Prox/RFID mark3 RFID instrument<br />
bootrom: master/v3.1.0-94-gd38bb3a-dirty-suspect 2019-06-01 14:36:05<br />
os: master/v3.1.0-94-gd38bb3a-dirty-suspect 2019-06-01 14:36:22<br />
fpga_lf.bit built for 2s30vq100 on 2015/03/06 at 07:38:04<br />
fpga_hf.bit built for 2s30vq100 on 2019/03/20 at 08:08:07<br />
<br />
We can now check the antenna strength of the attached antennas. If you have borrowed the proxmark3 of the Elvis IoT Lab you will get following output:<br />
<br />
(If no smart card is in proximity):<br />
<br />
proxmark3> hw tune<br />
Measuring antenna characteristics, please wait.........<br />
# LF antenna: 43.86 V @ 125.00 kHz<br />
# LF antenna: 21.04 V @ 134.00 kHz<br />
# LF optimal: 44.14 V @ 123.71 kHz<br />
# HF antenna: 30.41 V @ 13.56 MHz<br />
<br />
If we now lay a NFC card on the antennas the voltages changes:<br />
<br />
proxmark3> hw tune<br />
Measuring antenna characteristics, please wait.........<br />
# LF antenna: 44.27 V @ 125.00 kHz<br />
# LF antenna: 21.04 V @ 134.00 kHz<br />
# LF optimal: 44.27 V @ 123.71 kHz<br />
# HF antenna: *19.39 V* @ 13.56 MHz<br />
<br />
We can see, that the voltage of the HF antenna dropped from 30 volts to about 19 volts. We can assume that the placed NFC card is a high frequency card.<br />
<br />
==== command: hf ====<br />
"hf" stands for high frequency, which are specified at a carrier frequency of about 13.56 MHz.<br />
Possible commands that can be issued are listed below:<br />
<br />
proxmark3> hf<br />
14a { ISO14443A RFIDs... }<br />
14b { ISO14443B RFIDs... }<br />
15 { ISO15693 RFIDs... }<br />
epa { German Identification Card... }<br />
legic { LEGIC RFIDs... }<br />
iclass { ICLASS RFIDs... }<br />
mf { MIFARE RFIDs... }<br />
mfu { MIFARE Ultralight RFIDs... }<br />
mfp { MIFARE Plus RFIDs... }<br />
topaz { TOPAZ (NFC Type 1) RFIDs... }<br />
fido { FIDO and FIDO2 authenticators... }<br />
tune Continuously measure HF antenna tuning<br />
list List protocol data in trace buffer<br />
plot Plot signal<br />
search Search for known HF tags [preliminary]<br />
snoop <samples to skip (10000)> <triggers to skip (1)> Generic HF Snoop<br />
<br />
Most of these command-options are for specific cards from specific manufacturers (e.g. legic, iclass, mf). On the other hand, 14a is an NFC card standard that describes low-level communication of smart cards. Not all follow the same standard and some implement proprietary protocols. The Mifare cards are built upon the 14a standard and have additional commands which can be found in their specific directory.<br />
<br />
You usually start with the '''hf search''' command, which sends the card some data and analyses the return messages of the card. With this information, the Proxmark3 can make assumptions on what kind of card it may be.<br />
<br />
proxmark3> hf search<br />
UID : 01 02 03 04<br />
ATQA : 00 04<br />
SAK : 08 [2]<br />
TYPE : NXP MIFARE CLASSIC 1k | Plus 2k SL1<br />
proprietary non iso14443-4 card found, RATS not supported<br />
Chinese magic backdoor commands (GEN 1a) detected<br />
Prng detection: WEAK<br />
Valid ISO14443A Tag Found - Quiting Search<br />
<br />
Here we see that this card is classified as a Mifare Classic 1k. In particular, it also answers back to the Chinese magic backdoor command which tells us that this card is a fully cloneable card that allows us to change the UID block of the card. More on this can be found in the Documentation [[Proxmark3: FH-Campus Card NFC Security Valuation]]<br />
<br />
We can now issue the '''hf plot''' command which will display a waveform with the just sent and received data.<br />
<br />
[[File:Waveform.PNG|frameless]]<br />
<br />
Thankfully people wrote programs that will parse this data to a dedicated protocol ('''hf list'''). In this case, we want to parse it as a Mifare classic communication with '''hf list mf'''.<br />
<br />
proxmark3> hf list mf<br />
Recorded Activity (TraceLen = 156 bytes)<br />
Start = Start of Start Bit, End = End of last modulation. Src = Source of Transfer<br />
iso14443a - All times are in carrier periods (1/13.56Mhz)<br />
iClass - Timings are not as accurate<br />
Start | End | Src | Data (! denotes parity error, ' denotes short bytes) | CRC | Annotation |<br />
-----------|------------|-----|-----------------------------------------------------------------|-----|--------------------|<br />
0 | 992 | Rdr | 40' | | MAGIC WUPC1<br />
2484 | 3060 | Tag | 0a' | |<br />
7040 | 8352 | Rdr | 43 | | MAGIC WUPC2<br />
9524 | 10100 | Tag | 0a' | |<br />
14080 | 18848 | Rdr | 50 00 57 cd | ok | HALT<br />
0 | 992 | Rdr | 52' | | WUPA<br />
2228 | 4596 | Tag | 04 00 | |<br />
7040 | 9504 | Rdr | 93 20 | | ANTICOLL<br />
10676 | 16564 | Tag | 01 02 03 04 04 | |<br />
19328 | 29856 | Rdr | 93 70 01 02 03 04 04 8e 25 | ok | SELECT_UID<br />
31028 | 34548 | Tag | 08 b6 dd | |<br />
47488 | 52192 | Rdr | 60 00 f5 7b | ok | AUTH-A(0)<br />
54196 | 58932 | Tag | 01 20 01 45 | | AUTH: nt<br />
<br />
More on what is happening here can be found in the documentation [[Proxmark3: FH-Campus Card NFC Security Valuation]]<br />
<br />
<br />
There are many more commands. For example, '''hf data''' to manipulate the raw data, or '''hf mf''' to interact with Mifare Classic cards. Since this is only a short introduction to commands of the Proxmark3 we won't go deeper. If one is interested and wants to find out more about the Proxmark you we highly recommend the documentation [[Proxmark3: FH-Campus Card NFC Security Valuation]] - where not only the essentials are covered, but also an in-depth explanation about the technology used, the Proxmark itself, the Mifare Classic Standard and a validation of the FH-Campus card system.<br />
<br />
It is definitely worth checking out the paper since it also shows which vulnerabilities were found in the school card system.<br />
<br />
== Used Hardware ==<br />
<br />
[https://wiki.elvis.science/index.php?title=Proxmark_3 Proxmark3]<br />
<br />
== Additional Documentation ==<br />
<br />
* [[Proxmark3: Installation]]<br />
* [[Proxmark3: FH-Campus Card NFC Security Valuation]]<br />
<br />
== References ==<br />
<br />
* https://github.com/Proxmark/proxmark3<br />
* https://github.com/iceman1001/proxmark3<br />
<br />
[[Category:Documentation]]</div>Silviehttps://wiki.elvis.science/index.php?title=Proxmark3:_Installation&diff=6586Proxmark3: Installation2021-03-19T15:06:32Z<p>Silvie: Protected "Proxmark3: Installation" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))</p>
<hr />
<div>== Summary == <br />
<br />
Installation of [[Proxmark3 RDV2 Kit|Proxmark3]] on macOS, Linux and Windows for RFID and NFC sniffing.<br />
<br />
<pre style="color: red"><br />
To use the Bluetooth Module of the Proxmark3 RDV4 you need to install the https://github.com/RfidResearchGroup/proxmark3.git repository<br />
<br />
For installing on Linux please visit https://github.com/RfidResearchGroup/proxmark3/blob/master/doc/md/Installation_Instructions/Linux-Installation-Instructions.md<br />
</pre><br />
<br />
== MacOS installation ==<br />
<br />
=== Requirements ===<br />
<br />
Xcode (AppStore) is a must.<br />
<br />
In addition to make the installation easier have either HomeBrew or MacPorts ready.<br />
A Tutorial for installing:<br />
A) HomeBrew: https://docs.brew.sh/Installation<br />
B) MacPorts: https://www.macports.org/install.php<br />
<br />
Because of their different architecture (HomeBrew/MacPorts), some parts of this tutorial are split into:<br />
A) Installation with HomeBrew<br />
B) Installation with MacPorts<br />
Just choose the tutorial that suits your current setup.<br />
<br />
=== Installation with HomeBrew ===<br />
<br />
1. Download ("tap") the proxmark repository:<br />
<br />
brew tap proxmark/proxmark3<br />
<br />
2. Install proxmark3:<br />
<br />
brew install proxmark3<br />
<br />
=== Manual Installation ===<br />
<br />
Download the drivers and install them.<br />
If you have MacPorts:<br />
<br />
sudo port install p7zip readline libusb libusb-compat perl5 wget qt5\\ arm-none-eabi-gcc pkgconfig<br />
<br />
If you have HomeBrew:<br />
<br />
brew tap nitsky/stm32<br />
brew install readline libusb p7zip libusb-compat wget qt5 pkgconfig\\ arm-none-eabi-gcc<br />
<br />
Now you will need to add QT to the PKG_CONFIG_PATH so it find QT5 (replace YOUR_VERSION with your version number:<br />
<br />
export\\ PKG_CONFIG_PATH=/usr/local/Cellar/qt5/<<YOUR_VERSION>>/lib/pkgconfig/<br />
<br />
3. And add moc_location in Qt5Core.pc file:<br />
<br />
export QT_PKG_CONFIG_QT5CORE=$(find /usr -name Qt5Core.pc 2>/dev/null)<br />
chmod 666 $QT_PKG_CONFIG_QT5CORE<br />
echo "moc_location=\${prefix}/bin/moc" >> $QT_PKG_CONFIG_QT5CORE<br />
chmod 444 $QT_PKG_CONFIG_QT5CORE<br />
<br />
4. For link creation to avoid any errors of "readline" (may happen):<br />
<br />
brew link --force readline<br />
<br />
5. Now either git clone or manually download the Proxmark project. Git clone:<br />
<br />
git clone https://github.com/Proxmark/proxmark3.git<br />
<br />
6. "cd" to the proxmark3 folder<br />
<br />
7. Now jump to the section "Connecting your Proxmark"<br />
<br />
=== Connecting your Proxmark ===<br />
<br />
1. Insert your Proxmark and run<br />
<br />
system_profiler SPUSBDataType<br />
<br />
2.a) If your Proxmark is CDC you should somewhere see in the output:<br />
<br />
Product ID: 0x504d<br />
Vendor ID: 0x2d2d<br />
<br />
2.b) If your Proxmark is an HID device you should see:<br />
<br />
Product ID: 0x4b8f<br />
Vendor ID: 0x9ac4<br />
<br />
If it is an HID Device you will need to upgrade it, then go to "Upgrading my Proxmark HID->CDC"<br />
If you have an CDC Proxmark you can jump to "Finish Line"<br />
<br />
=== Upgrading my Proxmark HID->CDC ===<br />
<br />
1. Compile the bootrom, OS and software:<br />
<br />
make clean; make<br />
<br />
2. Also compile the HID compatible flash program:<br />
<br />
cd client/hid-flasher;make<br />
<br />
3. Disconnect Apple's HID driver, by installing a dummy kernel driver:<br />
<br />
sudo make install_kext<br />
sudo kextcache -system-caches<br />
<br />
4. Keep the Proxmark button pressed while reconnecting it to USB. Its yellow and red lights should light up (you can release the button after 5-ish seconds).<br />
<br />
5. Now upgrade the bootrom:<br />
<br />
./flasher -b ../../bootrom/obj/bootrom.elf<br />
<br />
6. cd ../..<br />
<br />
7. Disconnect your proxmark and keep the button pressed while reconnecting to USB.<br />
<br />
8. While keeping the button pressed run to get the device name:<br />
<br />
ls /dev/cu*<br />
<br />
You should find a name like "/dev/cu.usbmodem####" (#### represents a number).<br />
<br />
9. While still KEEPING PRESSED the button update the FPGA and its OS:<br />
<br />
./client/flasher /dev/cu.usbmodem#### armsrc/obj/fullimage.elf<br />
<br />
10. Disconnect the proxmark and release the button.<br />
<br />
11. Now reconnect your proxmark to USB and run it:<br />
<br />
cd proxmark3/client<br />
./proxmark3 /dev/cu.usbmodem####<br />
<br />
No need to go to "Finish Line", you are already finished with setting up the Proxmark Environment<br />
<br />
=== Finish Line ===<br />
<br />
1. Compile the bootrom and OS:<br />
<br />
make clean; make<br />
<br />
2. Disconnect your Proxmark from USB. Then keep the button pressed while reconnecting it back to USB. You can release the button when you see yellow/orange and red lights on your proxmark. (If you have an Elechouse v2 Proxmark3 or Elechouse v3 Proxmark3 Easy you do not need to press the button)<br />
<br />
3. Figure out your device name:<br />
<br />
ls /dev/cu*<br />
<br />
It should be something with /dev/cu.usbmodem#### (#### represents a number).<br />
<br />
4. After you have found your device run the program:<br />
<br />
cd proxmark3/client<br />
./proxmark3 /dev/cu.usbmodem####<br />
<br />
== Linux installation ==<br />
<br />
=== Requirements ===<br />
<br />
* Operating system: Ubuntu 16.04 trusty amd64<br />
<br />
=== Step 1 Compile resources:===<br />
<br />
1. download and install some needed packages and libs<br />
<br />
sudo apt-get install p7zip git build-essential libreadline5 libreadline-dev libusb-0.1-4 libusb-dev libqt4-dev perl pkg-config wget libncurses5-dev gcc-arm-none-eabi libstdc++-arm-none-eabi-newlib<br />
<br />
2. clone proxmark3 git repository<br />
<br />
git clone https://github.com/proxmark/proxmark3.git<br />
<br />
3. enter repo<br />
<br />
cd proxmark3<br />
<br />
4. get newest version<br />
<br />
git pull<br />
<br />
5. Install the blacklist rules<br />
<br />
sudo cp -rf driver/77-mm-usb-device-blacklist.rules /etc/udev/rules.d/77-mm-usb-device-blacklist.rules<br />
sudo udevadm control --reload-rules<br />
<br />
6. add current user to group<br />
<br />
sudo adduser $USER dialout<br />
<br />
7. log out and log into your account<br />
<br />
8. compile proxmark3<br />
<br />
make clean && make all<br />
<br />
=== Step 2 Identify proxmark3 device ===<br />
<br />
dmesg | grep -i usb<br />
[ 9704.503904] usb 1-3: Manufacturer: proxmark.org<br />
[ 9704.539638] cdc_acm 1-3:1.0: ttyACM0: USB ACM device<br />
<br />
=== Step 3 Flash the firmware of the proxmark ===<br />
<br />
!!! Do '''NOT''' press enter during the flashing process !!!<br />
<br />
./client/flasher /dev/ttyACM0 -b bootrom/obj/bootrom.elf armsrc/obj/fullimage.elf<br />
<br />
=== Step 4 Start the proxmark3 client ===<br />
<br />
./client/proxmark3 /dev/ttyACM0<br />
<br />
== Windows installation ==<br />
<br />
=== Requirements ===<br />
The tested Version for Windows was Windows 10, therefore the requirements for successfully completing our installation guide are:<br />
* Windows 10<br />
* [https://git-scm.com/download/win Git for Windows]<br />
<br />
=== Installation ===<br />
In order to be able to connect to your Proxmark3 under Windows you need to emulate a Linux environment which is done through a tool called ProxSpace.<br />
<br />
1. First you need to download the download the ProxSpace Repository through git.<br />
<br />
'''Caution!''' Your current working directory should contain no whitespaces!<br />
<br />
git clone https://github.com/Gator96100/ProxSpace.git<br />
<br />
2. Inside your ProxSpace Folder you should find "runme.bat". Start it.<br />
<br />
3. This will create and install all necessary packets and folders. After you should see the pm3-console.<br />
<br />
4. From this console you should change the directory to ProxSpace and download the Proxmark3 Repository:<br />
<br />
git clone https://github.com/Proxmark/proxmark3.git<br />
<br />
5. After this process is complete, cd to the proxmark3 directory:<br />
<br />
cd proxmark3<br />
<br />
6. Compile the proxmark3 project:<br />
<br />
make clean && make all<br />
<br />
7. Install the proxmark3 driver<br />
<br />
==== Windows 10 ====<br />
Since this driver is not officially signed by a trusted authority the installation is a bit tricky. You first have to start Windows in save-mode. This is done easiest, when pressing the shift-key while restarting your PC. On reboot you choose Startup-Settings followed by #7 Disable driver signature enforcement.<br />
After the computer restarted you connect the proxmark3 and go to the device manager, right click on the non-identified device (which is the proxmark3) and go to the settings. Click on update driver and search locally for the proxmark3.inf. If you have trouble getting the proxmark3 driver to work, please visit this [[https://store.ryscc.com/blogs/news/how-to-install-a-proxmark3-driver-on-windows-10 picture-guided tutorial]]<br />
<br />
<br />
After, the installation should be complete and you can safely restart your PC to normal mode again. From there start the runme.bat and the pm3-console should appear.<br />
<br />
==== Windows 7 ====<br />
[[File:Win7-disable-driversignature.png|520px|right]]<br />
<br />
* Start command prompt (cmd.exe) as '''administrator''' and execute:<br />
<br />
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS<br />
bcdedit.exe -set TESTSIGNING ON<br />
<br />
* Open the device manager, right-click on the unknow device "proxmark3" and select "update"<br />
* Select the manual driver selection, and within your ''ProxSpace'' folder select the ''msys2\proxmark3\driver'' subfolder<br />
<br />
After the successful driver setup you may want to disable testsigning again, and restart windows<br />
<br />
bcdedit.exe -set TESTSIGNING OFF<br />
<br />
=== Update your Proxmark3 ===<br />
<br />
To update the firmware of your Proxmark3 to the latest version, open cmd and type in (with x standing for the right number of your COM port, e.g. COM2):<br />
<br />
./proxmark/client/flasher COMx -b /bootrom/obj/bootrom.elf<br />
./proxmark/client/flasher COMX ./armsrc/obj/fullimage.elf<br />
<br />
=== Connecting to your Proxmark3 ===<br />
<br />
After having done all the steps above you can safely connect to your Proxmark3 through (where x again stands for the right number of your COM port, e.g. COM2):<br />
<br />
./client/proxmark3.exe COMx<br />
<br />
== Usage ==<br />
<br />
For using the Proxmark3 please visit our second documentation [[Proxmark3: Useful commands]] and feel free to have a look at the [https://github.com/Proxmark/proxmark3 Proxmark Repository!]<br />
<br />
== Resources and Tutorials ==<br />
<br />
* Client commands: https://github.com/Proxmark/proxmark3/wiki/commands<br />
* Usage example: https://www.youtube.com/watch?v=FODGYfhqb4Q<br />
* Basic tutorial for RFID usage: https://blog.kchung.co/rfid-hacking-with-the-proxmark-3/<br />
* Advanced tutorial: https://blog.kchung.co/rfid-hacking-with-the-proxmark-3/<br />
* Capture NFC traffic of apple pay transaction: https://salmg.net/2017/12/29/analyzing-an-apple-pay-transaction-with-proxmark3/<br />
<br />
== Used Hardware ==<br />
<br />
[[Proxmark 3]]<br />
<br />
== References ==<br />
* Product page and infos: https://www.elechouse.com/elechouse/index.php?main_page=product_info&cPath=90_93&products_id=2264&zenid=kmvhiob7nq1orc4pfjtf53sbr7<br />
* Manual: https://www.elechouse.com/elechouse/images/product/proxmark3_V2/Proxmark3%20V2%20User%20Guid.pdf<br />
* MacOS 10.x client installation: https://github.com/Proxmark/proxmark3/wiki/MacOS<br />
* Linux 16.04 client installation: https://github.com/Proxmark/proxmark3/wiki/Ubuntu-Linux<br />
* Windows 10 client installation: https://github.com/Proxmark/proxmark3/wiki/Windows<br />
<br />
[[Category:Documentation]]</div>Silviehttps://wiki.elvis.science/index.php?title=Proxmark3:_Debricking&diff=6585Proxmark3: Debricking2021-03-19T15:05:51Z<p>Silvie: Protected "Proxmark3: Debricking" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))</p>
<hr />
<div>== Summary == <br />
<br />
This tutorial will show how to reset a Proxmark3 RDV2 via the JTAG interface.<br />
<br />
This is useful when the '''Proxmark3 RDV2''' is bricked and won't connect to the computer. This will solve any software failures like a corrupt firmware or bootloader.<br />
<br />
'''1.''' Debricking process via '''Raspberry Pi''' 3+ (version 2, 3 and 4 work exactly the same)<br><br />
'''2.''' Debricking process via '''Bus Pirate''' 3.6<br />
: Note: The method with the Bus Pirate did '''not work''' for me. Maybe you have better luck.<br />
<br />
== Requirements ==<br />
<br />
* Proxmark3<br />
* Raspberry Pi 2, 3, or 4<br />
* Bus Pirate v3 (or higher)<br />
* Linux: Debian<br />
<br />
== Raspberry Pi ==<br />
<br />
[[File:Proxmark raspi.jpg|thumb|500px]]<br />
<br />
; This tutorial is based on:<br />
: http://www.lucasoldi.com/2017/01/17/unbrick-proxmark3-with-a-raspberry-pi-and-openocd/<br />
: https://github.com/synthetos/PiOCD/wiki/Using-a-Raspberry-Pi-as-a-JTAG-Dongle<br />
: http://openocd.org/doc/html/OpenOCD-Project-Setup.html<br />
<br />
-----<br />
<br />
=== Compile Proxmark ===<br />
<br />
See [https://wiki.elvis.science/index.php?title=Proxmark3:_Installation Proxmark: Installation] or from the [https://github.com/Proxmark/proxmark3/wiki/Ubuntu-Linux official website]<br />
<br />
=== Compile OpenOCD ===<br />
<br />
<pre><br />
sudo apt-get update<br />
sudo apt-get install -y autoconf libtool libftdi-dev textinfo pkg-config pkgconf git<br />
git clone https://git.code.sf.net/p/openocd/code openocd<br />
cd openocd<br />
./bootstrap<br />
./configure --enable-sysfsgpio --enable-bcm2835gpio<br />
make<br />
sudo make install<br />
sudo cp -r tcl/ /usr/share/openocd<br />
</pre><br />
<code>make</code> will take about 15 minutes.<br />
<br />
-> '''Note:''' make, bootstrap and configure should give no compilation errors !!! (if not so check if you have all necessary libraries installed) <br />
<br />
-> '''Note:''' also make sure that you compiled the proxmark repository without any compilation errors! (if not so check if you have all necessary libraries installed) <br />
<br />
=== Connect physically ===<br />
<br />
Connect the following pins from the Raspberry Pi to the Proxmark3<br />
<br />
: {| class="wikitable"<br />
! Proxmark3<br />
! Raspberry Pi<br />
! Cable colour<br />
|-<br />
| TMS || 22 || yellow<br />
|-<br />
| TDI || 19 || blue<br />
|-<br />
| TDO || 21 || green<br />
|-<br />
| TCK || 23 || orange<br />
|-<br />
| GND || 6 || grey<br />
|-<br />
| 3.3V || 1 || purple<br />
|}<br />
<br />
For the pin layout of the Raspberry Pi see [https://www.theengineeringprojects.com/wp-content/uploads/2018/07/introduction-to-raspberry-pi-3-b-plus-2.png link].<br />
<br />
[[File:Proxmark raspi pin.jpg|border|600px]]<br />
<br />
The pin configuration can be changed in: <code>/usr/share/openocd/interface/raspberrypi2-native.cfg</code>. (Not necessary for this tutorial)<br />
<br />
-----<br />
<br />
=== Connect via OpenOCD ===<br />
<br />
''Note: Power the Proxmark separately from the Raspberry Pi''<br />
<br />
; 1. Start OpenOCD<br />
: switch to the Proxmark folder<br />
:: <code>cd proxmark3</code><br />
:: ''Note: the source code of the Proxmark should be already be complied.''<br />
; 2. Create OpenOCD configuration<br />
:: <code>nano tools/raspi.cfg</code><br />
:: Past following code into the file<br />
<br />
<pre><br />
# Ports<br />
telnet_port 4444<br />
gdb_port 3333<br />
<br />
# Interface<br />
adapter_khz 1000<br />
source [find interface/raspberrypi2-native.cfg]<br />
<br />
# use combined on interfaces or targets that can't set TRST/SRST separately<br />
reset_config srst_only srst_pulls_trst<br />
<br />
jtag newtap sam7x cpu -irlen 4 -ircapture 0x1 -irmask 0xf<br />
<br />
target create sam7x.cpu arm7tdmi -endian little -chain-position sam7x.cpu <br />
<br />
sam7x.cpu configure -event reset-init { <br />
soft_reset_halt<br />
mww 0xfffffd00 0xa5000004 # RSTC_CR: Reset peripherals<br />
mww 0xfffffd44 0x00008000 # WDT_MR: disable watchdog<br />
mww 0xfffffd08 0xa5000001 # RSTC_MR enable user reset<br />
mww 0xfffffc20 0x00005001 # CKGR_MOR : enable the main oscillator<br />
sleep 10<br />
mww 0xfffffc2c 0x000b1c02 # CKGR_PLLR: 16MHz * 12/2 = 96MHz<br />
sleep 10<br />
mww 0xfffffc30 0x00000007 # PMC_MCKR : MCK = PLL / 2 = 48 MHz<br />
sleep 10<br />
mww 0xffffff60 0x00480100 # MC_FMR: flash mode (FWS=1,FMCN=72)<br />
sleep 100<br />
<br />
}<br />
<br />
gdb_memory_map enable<br />
#gdb_breakpoint_override hard<br />
#armv4_5 core_state arm<br />
<br />
sam7x.cpu configure -work-area-virt 0 -work-area-phys 0x00200000 -work-area-size 0x10000 -work-area-backup 0<br />
flash bank sam7x512.flash.0 at91sam7 0 0 0 0 sam7x.cpu 0 0 0 0 0 0 0 18432<br />
flash bank sam7x512.flash.1 at91sam7 0 0 0 0 sam7x.cpu 1 0 0 0 0 0 0 18432<br />
</pre><br />
<br />
; 3. Start OpenOCD with the configuration file just created<br />
:: <code>sudo openocd -f tools/raspi.cfg</code><br />
:: Now a openOCD session is started. Do '''not''' close it.<br />
~/git/proxmark3 $ sudo openocd -f tools/raspi.cfg<br />
Open On-Chip Debugger 0.10.0+dev-01404-g393448342-dirty (2020-09-17-17:59)<br />
Licensed under GNU GPL v2<br />
For bug reports, read<br />
http://openocd.org/doc/doxygen/bugs.html<br />
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.<br />
Info : Listening on port 6666 for tcl connections<br />
Info : Listening on port 4444 for telnet connections<br />
Info : BCM2835 GPIO JTAG/SWD bitbang driver<br />
Info : clock speed 1001 kHz<br />
Info : JTAG tap: sam7x.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787 (<unknown>), part: 0xf0f0, ver: 0x3)<br />
Info : Embedded ICE version 1<br />
Info : sam7x.cpu: hardware has 2 breakpoint/watchpoint units<br />
Info : starting gdb server for sam7x.cpu on 3333<br />
Info : Listening on port 3333 for gdb connections<br />
Info : accepting 'telnet' connection on tcp/4444<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
cpsr: 0x000000d3 pc: 0x00122a74<br />
<br />
'''Note:''' If the output does not look like that and rather looks like this:<br />
~/git/proxmark3 $ sudo openocd -f tools/raspi.cfg<br />
Open On-Chip Debugger 0.10.0+dev-01404-g393448342-dirty (2020-09-17-17:59)<br />
Licensed under GNU GPL v2<br />
For bug reports, read<br />
http://openocd.org/doc/doxygen/bugs.html<br />
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.<br />
Info : Listening on port 6666 for tcl connections<br />
Info : Listening on port 4444 for telnet connections<br />
Info : BCM2835 GPIO JTAG/SWD bitbang driver<br />
Info : clock speed 1001 kHz<br />
Info : JTAG tap: sam7x.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787 (<unknown>), part: 0xf0f0, ver: 0x3)<br />
Info : TAP auto0.tap does not have valid IDCODE (idcode=0x0)<br />
Info : TAP auto1.tap does not have valid IDCODE (idcode=0x0)<br />
Info : TAP auto2.tap does not have valid IDCODE (idcode=0x0)<br />
Info : TAP auto3.tap does not have valid IDCODE (idcode=0x0)<br />
Info : TAP auto4.tap does not have valid IDCODE (idcode=0x0)<br />
Info : TAP auto5.tap does not have valid IDCODE (idcode=0x0)<br />
, then erase the chip manually and enable the JTAG interface by connecting the pin of the AT91SAM7S512 to 3.3V (see http://www.proxmark.org/forum/viewtopic.php?id=6159)<br />
<br />
; 4. Connect to OpenOCD session<br />
: Open a new terminal window and telnet to the port that was specified in the .cfg file<br />
:: <code>telnet localhost 4444</code><br />
; 5. Flash via JTAG<br />
; 6. Halt the Proxmark3<br />
:: <code>halt</code><br />
; 7. Erase the flash content:<br />
:: <code>flash erase_sector 0 0 15</code><br />
:: <code>flash erase_sector 1 0 15</code><br />
; 8. Flash the new firmware:<br />
:: <code>flash write_image ./armsrc/obj/fullimage.elf</code><br />
:: <code>flash write_image ./bootrom/obj/bootrom.elf</code><br />
<br />
$ telnet localhost 4444<br />
Trying ::1...<br />
Trying 127.0.0.1...<br />
Connected to localhost.<br />
Escape character is '^]'.<br />
Open On-Chip Debugger<br />
> halt<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
cpsr: 0x000000d3 pc: 0x00122a74<br />
> flash erase_sector 0 0 15<br />
erased sectors 0 through 15 on flash bank 0 in 0.032174s<br />
<br />
> flash erase_sector 1 0 15<br />
erased sectors 0 through 15 on flash bank 1 in 0.031851s<br />
<br />
> flash write_image ./armsrc/obj/fullimage.elf<br />
wrote 257448 bytes from file ./armsrc/obj/fullimage.elf in 21.204687s (11.857 KiB/s)<br />
<br />
> flash write_image ./bootrom/obj/bootrom.elf<br />
wrote 3888 bytes from file ./bootrom/obj/bootrom.elf in 0.352596s (10.768 KiB/s)<br />
<br />
'''Done!'''<br />
<br />
Disconnect the Raspberry Pi from the Proxmark<br />
<br />
Now you should be able to connect to the Proxmark as usual:<br />
<br />
<code>./client/proxmark3 /dev/ttyACM0</code><br />
<br />
For useful commands visit: [[Proxmark3: Useful commands]]<br />
<br />
== Bus Pirate ==<br />
<br />
''Note: Here the Bus Pirate 3.6 will be used''<br />
<br />
''Note: This did not work for me, maybe it was faulty hardware or faulty firmware''<br />
<br />
This tutorial is based on https://scund00r.com/all/rfid/2018/05/18/debrick-proxmark.html<br />
<br />
; Update the Bus Pirate<br />
: you can use following guide: [[Bus Pirate: First steps]]<br />
; Get the latest Proxmark3 repository & build<br />
: <code>git clone https://github.com/Proxmark/proxmark3.git</code><br />
: <code>cd proxmark3</code><br />
: install needed components:<br />
: <code>sudo apt install p7zip git build-essential libreadline5 libreadline-dev libusb-0.1-4 libusb-dev libqt4-dev perl pkg-config wget libncurses5-dev gcc-arm-none-eabi libstdc++-arm-none-eabi-newlib libpcsclite-dev pcscd</code><br />
: <code> make clean && make all</code><br />
: Install proxmark3 driver:<br />
:: <code>sudo cp -rf driver/77-mm-usb-device-blacklist.rules /etc/udev/rules.d/77-mm-usb-device-blacklist.rules</code><br />
:: <code>sudo udevadm control --reload-rules</code><br />
: Add user<br />
:: <code>sudo adduser $USER dialout</code><br />
:: Now logout and login in again<br />
; Install OpenOCD<br />
: <code>sudo apt-get install openocd</code><br />
; Connect the Proxmark3 to the Bus Pirate<br />
: use this pin configuration:<br />
: {| class="wikitable"<br />
! Proxmark3<br />
! Bus Pirate<br />
|-<br />
| TMS || CS<br />
|-<br />
| TDI || MOSI<br />
|-<br />
| TDO || MISO<br />
|-<br />
| TCK || CLK<br />
|-<br />
| GND || GND<br />
|-<br />
| 3.3V || 3.3V<br />
|}<br />
; Flashing<br />
: check on with Port the Bus Pirate is connected:<br />
:: <code>ls /dev/tty*</code><br />
:: OR<br />
:: <code>dmesg -wH</code> and plugout and connect the Bus Pirate again<br />
: Set OpenOCD config<br />
:: <code>nano tools/at91sam7s512-buspirate.cfg</code><br />
# Interface<br />
interface buspirate<br />
buspirate_port /dev/ttyUSB0<br />
adapter_khz 1000<br />
; Start OpenOCD<br />
: Launch OpenOCD<br />
:: <code>sudo openocd -f tools/at91sam7s512-buspirate.cfg</code><br />
<br />
:~/git/proxmark3$ sudo openocd -f tools/at91sam7s512-buspirate.cfg<br />
[sudo] password for j: <br />
Open On-Chip Debugger 0.10.0-rc1-dev-gc404ff5d-dirty (2019-11-11-15:43)<br />
Licensed under GNU GPL v2<br />
For bug reports, read<br />
http://openocd.org/doc/doxygen/bugs.html<br />
Warn : Adapter driver 'buspirate' did not declare which transports it allows; assuming legacy JTAG-only <br />
Info : only one transport option; autoselect 'jtag' <br />
adapter speed: 1 000 kHz <br />
srst_only srst_p ulls_tr st srst_gates_jtag srst_open_drain connect_deassert_srst <br />
Info : Buspirate Interf ace ready! <br />
Info : This adap ter doe sn't suppo rt configurable speed <br />
Info : JTAG tap: sam7x. cpu tap/de vice found: 0x3f0f0f0f (mfg: 0x787 (<unknown>), part: 0xf0f0, ver: 0x3 ) <br />
Info : Embedded ICE version 1 <br />
Info : sam7x.cpu: hardware has 2 breakpoint/watchpoint units<br />
Info : accepting 'telnet' connection on tcp/4444<br />
<br />
: Open a new terminal window<br />
:: and type: <code>telnet localhost 4444</code><br />
<br />
j@laptop:~/git/proxmark3$ telnet localhost 4444<br />
Trying 127.0.0.1...<br />
Connected to localhost.<br />
Escape character is '^]'.<br />
Open On-Chip Debugger<br />
> <br />
<br />
: Halt the Proxmark3<br />
:: <code>halt</code><br />
: Erase the flash content:<br />
:: <code>flash erase_sector 0 0 15</code><br />
:: <code>flash erase_sector 1 0 15</code><br />
: Flash the new firmware:<br />
:: <code>flash write_image ./armsrc/obj/fullimage.elf</code><br />
:: This will take a while (about 6 minutes)<br />
:: <code>flash write_image ./bootrom/obj/bootrom.elf</code><br />
<br />
== Used Hardware ==<br />
<br />
[[Proxmark3 RDV2 Kit]]<br />
[[Bus Pirate v3.6 Universal serial interface]]<br />
<br />
== References ==<br />
<br />
* https://scund00r.com/all/rfid/2018/05/18/debrick-proxmark.html<br />
<br />
[[Category:Documentation]]</div>Silviehttps://wiki.elvis.science/index.php?title=Proxmark3_RDV4:_SmartCard&diff=6584Proxmark3 RDV4: SmartCard2021-03-19T15:05:33Z<p>Silvie: Protected "Proxmark3 RDV4: SmartCard" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))</p>
<hr />
<div>[[File:Smartcard chip.jpg|thumb|300px|Smartcard Chip]]<br />
<br />
== Summary == <br />
<br />
The Proxmark3 RDV4 comes with a built-in smartcard chip reader allowing to read and send data to the smartcard. A smartcard chip is a small passive-powered microprocessor that can be used in many ways. Most common, it enables some type of identification and can store a small amount of data. These chips usually are built with security in mind only allowing communication over the contact plates.<br />
<br />
== Requirements ==<br />
<br />
* Proxmark3 RDV4<br />
* Some Smartcards<br />
<br />
== Setup ==<br />
<br />
Hidden under the lid of the Proxmark RDV4 you can find a smart card reader. You can directly insert a smartcard directly into to the slot or insert it into the optional smartcard extender that allows for card size formats.<br />
<br />
[[File:Prox smartcard.jpg|800px|Proxmark with the smartcard extender]]<br />
<br />
== SC-Command ==<br />
<br />
SC stands for smartcard and allows communication over the metal chip contact plates. The protocol used for communication is defined by the ISO/IEC 7816 standard.<br />
<br />
A very informative and high-level introduction can be found here: [https://salmg.net/2018/10/18/proxmark3-rdv4-extracting-data-from-chip-and-pin-cards/ data-extraction from chip]<br />
<br />
At the moment following commands are present on the Proxmark3 RDV4:<br />
<br />
[usb] pm3 --> sc<br />
help This help <br />
list List ISO 7816 history <br />
info Tag information <br />
reader Act like an IS07816 reader <br />
raw Send raw hex data to tag <br />
upgrade Upgrade sim module firmware <br />
setclock Set clock speed <br />
brute Bruteforce SFI <br />
<br />
At the moment there are not many specific commands available as this feature is rather new. The two main commands are <code>sc info</code> to get the ATS response of the smartcard and <code>sc raw</code> that enables to send command/ data to the chip allowing to interact with it.<br />
<br />
I tested the <code>sc info</code> command on an Austrian e-card<br />
<br />
[usb] pm3 --> sc info<br />
[=] --- Smartcard Information --------- <br />
[=] ------------------------------------------------------------- <br />
[=] ISO7618-3 ATR : 3B DD 96 FF 81 B1 FE 45 1F 03 80 xx xx xx xx xx xx xx xx xx xx xx 05 18 <br />
<br />
[=] http:/ /smartcard-atr.appspot.com/ parse?ATR= 3BDD96FF81B1FE451F0380xxxxx xxxxxxxxxxxxxxxxx0518 <br />
<br />
<br />
[=] ATR <br />
- TA1 (Maximum clock frequency, p roposed bit duration) [ 0x96 ] <br />
- TC1 (Extra delay between bytes required by card) [ 0xff ] <br />
- TD1 (First offered transmission protocol, presence of TA2..TD2) [ 0x81 ] Protoc ol T1 <br />
- TD2 (A supported pr otocol or more global parameters, presence of TA3..T D3) [ 0xb1 ] Pr otocol T1 <br />
- TA3: 0xfe <br />
- TB3: 0x45 <br />
- TD3 [ 0x1f ] Protoc ol T15 <br />
- TA4: 0x03 <br />
[=] Check sum OK. <br />
<br />
[=] Histor ical bytes | le n 0x13 | format 80<br />
<br />
[=] Hi storical bytes <br />
00: 80 xx xx xx xx xx xx xx xx xx xx xx 05<br />
<br />
[=] D/F (T A1) <br />
- Di 3 2 <br />
- Fi 5 12 <br />
- F 5 ,0 MHz <br />
- Cycl es/ETU 16 <br />
- 2500 00,0 bits/s ec a t 4 MHz <br />
- 3125 00,0 bits/s ec a t Fmax (5,0MHz) <br />
<br />
Following the weblink we get the addional information that the smartcard is probably running the operating system StarCOS 3.4<br />
<br />
On website: https://smartcard-atr.apdu.fr/<br />
Austrian "e-card" G3 (State Health Insurance Card)<br />
(running StarCOS 3.4 by Giesecke & Devrient) <br />
<br />
----<br />
<br />
I had an old sim-card (GSM SIM card of the Austrian provider A1) laying around and tested the <code>sc raw</code> command.<br />
<br />
For a high-level overview of sim-card commands and responses I recommend:<br />
* http://rebelsimcard.com/sim-commands.html<br />
* http://rebelsimcard.com/what-is-an-apdu.html<br />
* http://rebelsimcard.com/sim-file-system.html<br />
<br />
[usb] pm3 --> sc raw s t d A0 A4 00 00 02 3F 00<br />
[+] 9F16 | Command successfully executed; 'xx' bytes of data are available and can be requested using GET RESPONSE. <br />
[=] Requesting 0x16 bytes response <br />
[+] 9000 | Command successfully executed (OK). <br />
[!] TLV ERROR: Can't parse response as TLV tree. <br />
[usb] pm3 --> sc list<br />
[+] Recorded activity (trace len = 109 bytes) <br />
[=] Start = Start of Start Bit, End = End of last modulation. Src = Source of Transfer <br />
[=] ISO7816-4 / Smartcard - Timings N/A yet <br />
<br />
Start | End | Src | Data (! denotes parity error) | CRC | Annotation <br />
------------+------------+-----+-------------------------------------------------------------------------+-----+-------------------- <br />
0 | 0 | Tag |3b 3f 96 00 80 69 af 03 3d 00 c6 00 00 00 0e 83 1e 9f | | <br />
| | |16 | | <br />
0 | 0 | Rdr |a0 a4 00 00 02 3f 00 | | R-block ACK <br />
0 | 0 | Tag |a4 9f 16 | | <br />
0 | 0 | Rdr |00 c0 00 00 16 | | GET RESPONSE <br />
0 | 0 | Tag |c0 00 00 59 09 3f 00 01 00 00 00 00 00 09 13 02 0f 08 | | <br />
| | |00 83 8a 83 8a 90 00 | | <br />
<br />
I sent the Requet-Block command <code> A0 A4 00 00 02</code> and appended <code>3F 00</code> that tells the chip that I want to read out the file at the destination 0x3F00.<br />
<br />
== EMV-Command ==<br />
<br />
EMV originally stood for "Europay, Mastercard, Visa" which are the three companies that defined the standard that allows contact and contactless paying.<br />
<br />
[usb] pm3 --> emv<br />
help This help <br />
exec Executes EMV contactless transaction. <br />
pse Execute PPSE. It selects 2PAY.SYS.DDF01 or 1PAY.SYS.DDF01 directory. <br />
search Try to select all applets from applets list and print installed applets. <br />
select Select applet. <br />
gpo Execute GetProcessingOptions. <br />
readrec Read files from card. <br />
genac Generate ApplicationCryptogram. <br />
challenge Generate challenge. <br />
intauth Internal authentication. <br />
scan Scan EMV card and save it contents to json file for emulator. <br />
test Crypto logic test. <br />
list List ISO7816 history <br />
roca Extract public keys and run ROCA test <br />
<br />
With the extension of the smartcard-chip reader, it is now possible to perform the commands not only wirelessly but also wired. All the commands can be invoked with the parameter -w:<br />
<br />
[usb] pm3 --> emv exec --help<br />
Usage: emv exec [-h|-H|--help] [-s|-S|--select] [-a|-A|--apdu] [-t|-T|--tlv] [-j|-J|--jload] [-f|-F|--forceaid] By default: [-v|-V|--qvsdc] [-c|-C|--qvsdccda] [-x|-X|--vsdc] [-g|-G|--acgpo] [-w|-W|--wired] <br />
Executes EMV contactless transaction <br />
<br />
-h, -H, --help This help<br />
-s, -S, --select activate field and select card.<br />
-a, -A, --apdu show APDU reqests and responses.<br />
-t, -T, --tlv TLV decode results.<br />
-j, -J, --jload Load transaction parameters from `emv_defparams.json` file.<br />
-f, -F, --forceaid Force search AID. Search AID instead of execute PPSE.<br />
By default: Transaction type - MSD<br />
-v, -V, --qvsdc Transaction type - qVSDC or M/Chip.<br />
-c, -C, --qvsdccda Transaction type - qVSDC or M/Chip plus CDA (SDAD generation).<br />
-x, -X, --vsdc Transaction type - VSDC. For test only. Not a standard behavior.<br />
-g, -G, --acgpo VISA. generate AC from GPO.<br />
-w, -W, --wired Send data via contact (iso7816) interface. Contactless interface set by default.<br />
<br />
Usage:<br />
emv exec -sat -> select card, execute MSD transaction, show APDU and TLV<br />
emv exec -satc -> select card, execute CDA transaction, show APDU and TLV<br />
<br />
== Used Hardware ==<br />
<br />
[[Proxmark3 RDV4 Kit]]<br />
<br />
== References ==<br />
<br />
* https://en.wikipedia.org/wiki/EMV<br />
<br />
[[Category:Documentation]]</div>Silviehttps://wiki.elvis.science/index.php?title=Proxmark3_RDV4&diff=6583Proxmark3 RDV42021-03-19T15:05:09Z<p>Silvie: Protected "Proxmark3 RDV4" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))</p>
<hr />
<div>== Summary == <br />
<br />
[[File:Prox no case size.jpg|thumb|500px|Proxmark3 RDV4]]<br />
<br />
The Proxmark is an RFID swiss-army tool, allowing for both high and low-level interactions with the vast majority of RFID/NFC tags and systems worldwide (proxmark.com).<br />
<br />
The Proxmark3 Dev Kit 4 (RDV4) is more compact and portable than the older versions and brings various improvements to the open-source design. Antennas are highly customizable and there is a new multifunction multiplexing interface to support additional components such as external battery, external active high powered antenna, Bluetooth interfaces and SIM/Smart card reader (hackerwarehouse.com).<br />
<br />
This write-up concentrates on the improvements of the RDV4 over the RDV2 and will not cover the basic operations. For more, please visit [[Proxmark3: Useful commands]] or [[Proxmark3: FH-Campus Card NFC Security Valuation]]<br />
<br />
== Requirements ==<br />
<br />
* Proxmark3 RDV4<br />
<br />
To use the Bluetooth module & for new features of the RDV4 use the new [https://github.com/RfidResearchGroup/proxmark3.git new repository]<br />
<br />
Setting-up & compiling are explained in the [https://github.com/RfidResearchGroup/proxmark3/blob/master/doc/md/Installation_Instructions/Linux-Installation-Instructions.md original documentation]<br />
<br />
For a quick introduction to the default commands please visit: [[Proxmark3: Useful commands]]<br />
<br />
== Smart Card ==<br />
<br />
Hidden under the lid of the Proxmark RDV4 you can find a smart card reader. You can directly insert a smartcard directly into to the slot or insert it into the optional smartcard extender, which allows for card size formats. <br />
<br />
[[File:Prox smartcard.jpg|800px|Proxmark with the smartcard extender]]<br />
<br />
For more information on reading and writing to smartcards please visit the follow-up post [[Proxmark3 RDV4: SmartCard]]<br />
<br />
== Bluetooth Module ==<br />
<br />
With the Blue-Shark Module it is now possible to wirelessly communicate with the Proxmark RDV4!<br />
<br />
=== Installation ===<br />
<br />
<div><ul> <br />
<li style="display: inline-block;"> [[File:Prox open case.jpg|thumb|none|x300px|1. Remove the antenna cover and use the plastic prying tool to open the case.]] </li><br />
<li style="display: inline-block;"> [[File:Prox remove antenna.jpg|thumb|none|x300px|2. Remove the six screws of the antenna.]] </li><br />
<li style="display: inline-block;"> [[File:Prox bt cable.jpg|thumb|none|x300px|3. Connect the Bluetooth cable to the Proxmark by first opening the black hinge of the ribbon cable.]] </li><br />
<li style="display: inline-block;"> [[File:Prox bt cable2.jpg|thumb|none|x300px|4. Insert the ribbon cable into the connector and close the hinge again.]] </li><br />
<li style="display: inline-block;"> [[File:Prox bt.jpg|thumb|none|x300px|5. Remove the blue tape on the Bluetooth module.]] </li><br />
<li style="display: inline-block;"> [[File:Prox bt2.jpg|thumb|none|x300px|6. Push the module onto the Proxmark.]] </li><br />
<li style="display: inline-block;"> [[File:Prox bt3.jpg|thumb|none|x300px|7. Connect the antenna to the Proxmark and add the cover of the antenna.]]</li><br />
</ul></div><br />
<br />
To enable this feature you need to install the newest RfidResearchGroup/proxmark3 repo and enable the Bluetooth setting in the makefile: the instructions are based on [https://github.com/RfidResearchGroup/proxmark3/blob/master/doc/bt_manual_v10.md Blue Shark Installation]<br />
<br />
=== Linux installation === <br />
<br />
; Preperation<br />
* Update system:<br />
: <code>sudo apt-get update</code><br />
* Install requirements:<br />
: <code>sudo apt-get install --no-install-recommends git ca-certificates build-essential pkg-config libreadline-dev gcc-arm-none-eabi libnewlib-dev qtbase5-dev</code><br />
* On Linux you have to make shure you remove of disable the ModemManager (this is usally pre-installed to interact with (2G,3G,4G) devices.<br />
* Remove ModemManager<br />
: <code>sudo apt remove modemmanager</code><br />
* Download repostiory:<br />
: <code>git clone https://github.com/RfidResearchGroup/proxmark3.git</code><br />
* cd into repo<br />
: <code>cd proxmark3</code><br />
* Or update to the newest version:<br />
: <code>git pull</code><br />
; Compile source code<br />
* Enable Bluetooth module<br />
: <code>cp Makefile.platform.sample Makefile.platform</code><br />
: <code>nano Makefile.platform</code><br />
: And uncomment the line <code>#PLATFORM_EXTRAS=BTADDON</code> by removing the <code>#</code> & save changes by pressing <code>ctrl+x</code><br />
* Compile source code<br />
: <code>make clean; make -j8</code><br />
: <code>sudo make install</code><br />
* Add access rights<br />
: <code>make accessrights</code><br />
: Now log off and log on again.<br />
* Connect the Proxmark3 to the computer<br />
* Flash the firmware<br />
: <code>./pm3-flash-bootrom</code><br />
: <code>./pm3-flash-all</code><br />
; Connect wirelessly to the Proxmark<br />
* Turn on the Bluetooth module (both switches to on)<br />
* Find MAC address<br />
sudo hcitool scan<br />
Scanning ...<br />
aa:bb:cc:dd:ee:ff PM3_RDV4.0<br />
* Bind your BT add-on MAC address to a serial port<br />
: <code>sudo rfcomm bind rfcomm0 aa:bb:cc:dd:ee:ff</code><br />
* If connecting the first time:<br />
bluetoothctl<br />
[bluetooth]# pairable on<br />
[bluetooth]# scan on<br />
Discovery started<br />
...<br />
[CHG] Device aa:bb:cc:dd:ee:ff Name: PM3_RDV4.0<br />
[bluetooth]# trust aa:bb:cc:dd:ee:ff<br />
[bluetooth]# pair aa:bb:cc:dd:ee:ff<br />
[agent] Enter PIN code: 1234<br />
[bluetooth]# quit<br />
* Else, open the Proxmark client<br />
: <code>proxmark3 /dev/rfcomm0</code><br />
: Now the Proxmark LED should stop blinking and turn solid blue. THe Proxmark client should show the default interface.<br />
<br />
== Antennas ==<br />
<br />
The Proxmark3 RDV4 optionally ships with high-frequency (hf) and low-frequency (lf) antenna kits. They include a medium and long-range antenna. The following will show the differences between them.<br />
<br />
=== High-Frequecy Antenna Kit ===<br />
<br />
The hf-antenna kit comes with two antennas that are advertised as medium- and long-range antennas. The store [https://lab401.com/products/proxmark-3-rdv4-long-range-hf-antenna-1 lab401] says the range of the default antenna is about 40-85mm, medium-range antenna about 90mm, and the long-range has a reach of 100-120mm. A small test of mine concludes that this statement is only partially true. <br />
<br />
<div><ul> <br />
<li style="display: inline-block;"> [[File:Prox hf normal.jpg|thumb|none|x300px|Default HF-Antenna]] </li><br />
<li style="display: inline-block;"> [[File:Prox hf med.jpg|thumb|none|x300px|Medium-Range HF-Antenna]] </li><br />
<li style="display: inline-block;"> [[File:Prox hf long.jpg|thumb|none|x300px|Long-Range HF-Antenna]] </li><br />
</ul></div><br />
<br />
I tested the range of 4 different cards:<br />
<br />
* Card 1: HF-Card shipped with the RDV4: NXP MIFARE CLASSIC 1k Gen1A S50<br />
* Card 2: Student-Card: NXP MIFARE DESFire 4k <br />
* Card 3: Portugal, Proto MetroCard: Ultralight EV1 48bytes (MF0UL1101)<br />
* Card 4: SkiData Card: EM-Marin SA (Skidata); EM4233<br />
<br />
(!) denotes that the readings were inconsistent:<br />
The card only got recognized from time to time<br />
(!!) denotes that the readings were '''very''' inconsistent:<br />
Only if lucky the card got recognized<br />
/ denotes that the card got not read at all<br />
<br />
{| class="wikitable"<br />
|-<br />
! scope="col" | Card<br />
! scope="col" | Default-Antenna<br />
! scope="col" | Medium-Range Antenna<br />
! scope="col" | Long-Range Antenna<br />
|-<br />
! scope="row" | Shipped HF-Card<br />
| 8 cm<br />
| (!!) 0 cm<br />
| (!!) 2 cm<br />
|-<br />
! scope="row" | Student-Card<br />
| 5 cm <br />
| (!) 0 cm <br />
| (!) 7 cm<br />
|-<br />
! scope="row" | Metro-Card<br />
| 8 cm <br />
| /<br />
| (!) 11 cm<br />
|-<br />
! scope="row" | SkiData-Card<br />
| 7 cm <br />
| 7 cm <br />
| 11 cm<br />
|}<br />
<br />
The results show that the antenna reach depends heavily on the card trying to read. The most consistent results came from the default-antenna that ships with the RDV4. As shown, the optional antennas did cope with the NXP Mifare cards very poorly but show improvements for the SkiData card.<br />
<br />
=== Low-Frequency Antenna Kit ===<br />
<br />
Sadly I do not have any lf-cards on hand and could not test the range of the given antennas.<br />
<br />
The lf-antenna kit comes with two antennas that are advertised as medium- and long-range antennas. The store [https://lab401.com/products/proxmark-3-rdv4-01-long-range-lf-antenna-pack lab401] says the range of the default antenna is about 66 - 72mm, medium-range antenna about 90mm, and the long-range has a reach of 110 - 133mm. But as shown above, for the hf-antenna this depends heavily on the lf-card itself.<br />
<br />
<div><ul> <br />
<li style="display: inline-block;"> [[File:Prox lf med.jpg|thumb|none|x300px|Medium-Range LF-Antenna]] </li><br />
<li style="display: inline-block;"> [[File:Prox lf long.jpg|thumb|none|x300px|Long-Range LF-Antenna]] </li><br />
<li style="display: inline-block;"> [[File:Prox lf switch.jpg|thumb|none|300px|LF-Antenna Switch]] </li><br />
</ul></div><br />
<br />
The optional antennas come with 2 switches: (source: [https://lab401.com/products/proxmark-3-rdv4-01-long-range-lf-antenna-pack lab401])<br />
<br />
; Q-Switch<br />
: The Q-Switch has two settings: 14 (Extended Range) and 7 (Extended Accuracy).<br />
:: Q-Switch setting of 14 will give up to 30% further read range (on lf search / lf hid read etc commands).<br />
:: Q-Switch setting of 7 will give better writing performance on T55XX and EM410XX tags.<br />
<br />
; Frequency Switch<br />
: The frequency switch allows for tuning to specific tag types: 125KHz or 134KHz.<br />
<br />
== Used Hardware ==<br />
<br />
[[Proxmark3 RDV4 Kit]]<br />
<br />
[[Proxmark3 RDV4.0 BT & Battery Addon Blue Shark]]<br />
<br />
[[Proxmark3 RDV4.0 HF Antennas]]<br />
<br />
[[Proxmark3 RDV4.0 LF Antennas]]<br />
<br />
== References ==<br />
<br />
* https://www.proxmark.com<br />
* https://www.hackerwarehouse.com<br />
* https://www.lab401.com<br />
* https://github.com/RfidResearchGroup/proxmark3<br />
<br />
[[Category:Documentation]]</div>Silviehttps://wiki.elvis.science/index.php?title=Template:Documentation&diff=6043Template:Documentation2021-02-24T17:07:56Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
Description what this documentation is about.<br />
<br />
== Requirements ==<br />
<br />
* Operating system: Ubuntu 18.04 bionic amd64<br />
* Packages: git emacs<br />
<br />
In order to complete these steps, you must have followed [[Some Other Documentation]] before.<br />
<br />
== Description ==<br />
<br />
=== Step 1 ===<br />
<br />
Enter these commands in the shell<br />
<br />
echo foo<br />
echo bar<br />
<br />
=== Step 2 ===<br />
<br />
Make sure to read<br />
<br />
* War and Peace<br />
* Lord of the Rings<br />
* The Baroque Cycle<br />
<br />
== Used Hardware ==<br />
<br />
[[Device to be used with this documentation]]<br />
[[Maybe another device to be used with this documentation]]<br />
<br />
== Courses ==<br />
<br />
* [[A course where this documentation was used]] (2017, 2018)<br />
* [[Another one]] (2018)<br />
<br />
== References ==<br />
<br />
* https://wikipedia.org<br />
* https://google.com<br />
<br />
[[Category:Documentation]]</div>Silviehttps://wiki.elvis.science/index.php?title=Password_Security&diff=3300Password Security2020-03-02T17:24:13Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
This documentation provides advice about secure passowrds. It covers known problems with passwords and elaborates various solutions for secure password creation and usage. The issue "bad passwords" is the number 1 vulnerability in the Internet-of-Things (IoT)[1].<br />
<br />
== Problems with Passwords ==<br />
<br />
There are several more or less widely known bad habits regarding passwords.<br />
<br />
=== The Password Quality ===<br />
<br />
'''Personal information''' is used to create passwords which is a polpular target for social engineering (names, dates, etc.). Often '''standard passwords''' like "123456" or "passowrd" are used. Actually, "123456" is the most used password for the last years [2]. The re-use of passwords is one of the main topics: many users use the '''same password for various accounts'''. It is obvious that it is not a good idea to use the same password for online banking and for Adobe account. <br />
<br />
== Good Passwords ==<br />
<br />
There are 3 general aspects for good passwords: the length plays a main role, the pwassword must not be trivial, and the password must be easily memorized. Leet speak is not a good idea because meanwhile all password crackers know leet speak.<br />
<br />
=== Good Password Checklist ===<br />
<br />
* Minimum length of 12 characters<br />
* Contains lower & upper case letters, digits, and special characters<br />
* As random as possible<br />
* Easy to remember<br />
<br />
=== How to Create a Good Password ===<br />
<br />
* Think about your favorite lines of a song, poem, or movie, etc. Take the first letters and special characters to create your password. <br />
<br />
Here's an example:<br />
Are you lonesome tonight? <br />
Do you miss me tonight?<br />
Are you sorry we drifted apart?<br />
<br />
The resulting password might be: Ayl2n?Dymm2n?Ayswda?<br />
<br />
* Think about approx. 4 different words which make sense for you but in general, the combination does not make any sense at all. Meaningful sentences are no good passwords.<br />
<br />
Here's an example:<br />
Concrete<br />
Ocean<br />
Mouse<br />
Egg<br />
<br />
You'll have to add a special character and a digit. The resulting password might be: ConcreteOcean4MouseEgg! <br />
<br />
== Further Advice for a Secure Password Usage ==<br />
<br />
=== Password Manager ===<br />
<br />
The use of a password manager solves the problem to remember numerous different passwords for various accounts. You have on file containing all your passwords which is secured by one good password. Our recommended password managers are open source, free of charge, and platform-independant.<br />
<br />
Recommended password managers:<br />
<br />
* KeePass XC - https://keepassxc.org/<br />
* KeePass - https://keepass.info/<br />
<br />
=== Two-Factor Authentication ===<br />
<br />
Two-Factor Authentication requires a second authentication method besides the password, e.g. Google Authenticator [3] which provides a 6-digit code for each login. A second authentication factor might also be a biometric factor (e.g. fingerprint). You also might use a crypto token (e.g. a Yubico key [4]). <br />
<br />
== Courses ==<br />
<br />
* [[Workshops]] (2017, 2018, 2019, 2020)<br />
<br />
== References ==<br />
<br />
* [1] https://www.owasp.org/images/1/1c/OWASP-IoT-Top-10-2018-final.pdf<br />
* [2] https://metro.co.uk/2019/12/19/10-worst-passwords-2019-revealed-nothing-changed-11932281/<br />
* [3] https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=de_AT<br />
* [4] https://www.yubico.com/authentication-standards/fido-u2f/<br />
<br />
<br />
<br />
<br />
[[Category:Basic]]</div>Silviehttps://wiki.elvis.science/index.php?title=Password_Security&diff=3299Password Security2020-03-02T17:23:50Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
This documentation provides advice about secure passowrds. It covers known problems with passwords and elaborates various solutions for secure password creation and usage. The issue "bad passwords" is the number 1 vulnerability in the Internet-of-Things (IoT)[1].<br />
<br />
== Problems with Passwords ==<br />
<br />
There are several more or less widely known bad habits regarding passwords.<br />
<br />
=== The Password Quality ===<br />
<br />
'''Personal information''' is used to create passwords which is a polpular target for social engineering (names, dates, etc.). Often '''standard passwords''' like "123456" or "passowrd" are used. Actually, "123456" is the most used password for the last years [2]. The re-use of passwords is one of the main topics: many users use the '''same password for various accounts'''. It is obvious that it is not a good idea to use the same password for online banking and for Adobe account. <br />
<br />
== Good Passwords ==<br />
<br />
There are 3 general aspects for good passwords: the length plays a main role, the pwassword must not be trivial, and the password must be easily memorized. Leet speak is not a good idea because meanwhile all password crackers know leet speak.<br />
<br />
=== Good Password Checklist ===<br />
<br />
* Minimum length of 12 characters<br />
* Contains lower & upper case letters, digits, and special characters<br />
* As random as possible<br />
* Easy to remember<br />
<br />
=== How to Create a Good Password ===<br />
<br />
* Think about your favorite lines of a song, poem, or movie, etc. Take the first letters and special characters to create your password. <br />
<br />
Here's an example:<br />
Are you lonesome tonight? <br />
Do you miss me tonight?<br />
Are you sorry we drifted apart?<br />
<br />
The resulting password might be: Ayl2n?Dymm2n?Ayswda?<br />
<br />
* Think about approx. 4 different words which make sense for you but in general, the combination does not make any sense at all. Meaningful sentences are no good passwords.<br />
<br />
Here's an example:<br />
Concrete<br />
Ocean<br />
Mouse<br />
Egg<br />
<br />
You'll have to add a special character and a digit. The resulting password might be: ConcreteOcean4MouseEgg! <br />
<br />
== Further Advice for a Secure Password Usage ==<br />
<br />
=== Password Manager ===<br />
<br />
The use of a password manager solves the problem to remember numerous different passwords for various accounts. You have on file containing all your passwords which is secured by one good password. Our recommended password managers are open source, free of charge, and platform-independant.<br />
<br />
Recommended password managers:<br />
<br />
* KeePass XC - https://keepassxc.org/<br />
* KeePass - https://keepass.info/<br />
<br />
=== Two-Factor Authentication ===<br />
<br />
Two-Factor Authentication requires a second authentication method besides the password, e.g. Google Authenticator [3] which provides a 6-digit code for each login. A second authentication factor might also be a biometric factor (e.g. fingerprint). You also might use a crypto token (e.g. a Yubico key [4]). <br />
<br />
<br />
<br />
<br />
== Courses ==<br />
<br />
* [[Workshops]] (2017, 2018, 2019, 2020)<br />
<br />
== References ==<br />
<br />
* [1] https://www.owasp.org/images/1/1c/OWASP-IoT-Top-10-2018-final.pdf<br />
* [2] https://metro.co.uk/2019/12/19/10-worst-passwords-2019-revealed-nothing-changed-11932281/<br />
* [3] https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=de_AT<br />
* [4] https://www.yubico.com/authentication-standards/fido-u2f/<br />
<br />
<br />
<br />
<br />
[[Category:Basic]]</div>Silviehttps://wiki.elvis.science/index.php?title=Password_Security&diff=3298Password Security2020-03-02T17:16:09Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
This documentation provides advice about secure passowrds. It covers known problems with passwords and elaborates various solutions for secure password creation and usage. The issue "bad passwords" is the number 1 vulnerability in the Internet-of-Things (IoT)[1].<br />
<br />
== Problems with Passwords ==<br />
<br />
There are several more or less widely known bad habits regarding passwords.<br />
<br />
=== The Password Quality ===<br />
<br />
'''Personal information''' is used to create passwords which is a polpular target for social engineering (names, dates, etc.). Often '''standard passwords''' like "123456" or "passowrd" are used. Actually, "123456" is the most used password for the last years [2]. The re-use of passwords is one of the main topics: many users use the '''same password for various accounts'''. It is obvious that it is not a good idea to use the same password for online banking and for Adobe account. <br />
<br />
== Good Passwords ==<br />
<br />
There are 3 general aspects for good passwords: the length plays a main role, the pwassword must not be trivial, and the password must be easily memorized. Leet speak is not a good idea because meanwhile all password crackers know leet speak.<br />
<br />
=== Good Password Checklist ===<br />
<br />
* Minimum length of 12 characters<br />
* Contains lower & upper case letters, digits, and special characters<br />
* As random as possible<br />
* Easy to remember<br />
<br />
=== How to Create a Good Password ===<br />
<br />
* Think about your favorite lines of a song, poem, or movie, etc. Take the first letters and special characters to create your password. <br />
<br />
Here's an example:<br />
Are you lonesome tonight? <br />
Do you miss me tonight?<br />
Are you sorry we drifted apart?<br />
<br />
The resulting password might be: Ayl2n?Dymm2n?Ayswda?<br />
<br />
* Think about approx. 4 different words which make sense for you but in general, the combination does not make any sense at all. Meaningful sentences are no good passwords.<br />
<br />
Here's an example:<br />
Concrete<br />
Ocean<br />
Mouse<br />
Egg<br />
<br />
You'll have to add a special character and a digit. The resulting password might be: ConcreteOcean4MouseEgg! <br />
<br />
== Further Advice for a Secure Password Usage ==<br />
<br />
=== Password Manager ===<br />
<br />
The use of a password manager solves the problem to remember numerous different passwords for various accounts. You have on file containing all your passwords which is secured by one good password. Our recommended password managers are open source, free of charge, and platform-independant.<br />
<br />
Recommended password managers:<br />
<br />
* https://keepassxc.org/<br />
* https://keepass.info/<br />
<br />
=== Two-Factor Authentication ===<br />
<br />
<br />
<br />
<br />
== Requirements ==<br />
<br />
none - so far...<br />
<br />
In order to complete these steps, you must have followed [[Some Other Documentation]] before.<br />
<br />
== Description ==<br />
<br />
=== Step 1 ===<br />
<br />
Enter these commands in the shell<br />
<br />
echo foo<br />
echo bar<br />
<br />
=== Step 2 ===<br />
<br />
Make sure to read<br />
<br />
* War and Peace<br />
* Lord of the Rings<br />
* The Baroque Cycle<br />
<br />
== Used Hardware ==<br />
<br />
[[Device to be used with this documentation]]<br />
[[Maybe another device to be used with this documentation]]<br />
<br />
== Courses ==<br />
<br />
* [[A course where this documentation was used]] (2017, 2018)<br />
* [[Another one]] (2018)<br />
<br />
== References ==<br />
<br />
* [1] https://www.owasp.org/images/1/1c/OWASP-IoT-Top-10-2018-final.pdf<br />
* [2] https://metro.co.uk/2019/12/19/10-worst-passwords-2019-revealed-nothing-changed-11932281/<br />
<br />
<br />
[[Category:Basic]]</div>Silviehttps://wiki.elvis.science/index.php?title=Password_Security&diff=3297Password Security2020-03-02T16:29:53Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
This documentation provides advice about secure passowrds. It covers known problems with passwords and elaborates various solutions for secure password creation and usage. The issue "bad passwords" is the number 1 vulnerability in the Internet-of-Things (IoT)[1].<br />
<br />
== Problems with Passwords ==<br />
<br />
There are several more or less widely known bad habits regarding passwords.<br />
<br />
=== The Password Quality ===<br />
<br />
'''Personal information''' is used to create passwords which is a polpular target for social engineering (names, dates, etc.). Often '''standard passwords''' like "123456" or "passowrd" are used. Actually, "123456" is the most used password for the last years [2]. The re-use of passwords is one of the main topics: many users use the '''same password for various accounts'''. It is obvious that it is not a good idea to use the same password for online banking and for Adobe account. <br />
<br />
== Good Passwords ==<br />
<br />
There are 3 general aspects for good passwords: the length plays a main role, the pwassword must not be trivial, and the password must be easily memorized. Leet speak is not a good idea because meanwhile all password crackers know leet speak.<br />
<br />
=== Good Password Checklist ===<br />
<br />
* Minimum length of 12 characters<br />
* Contains lower & upper case letters, digits, and special characters<br />
* As random as possible<br />
* Easy to remember<br />
<br />
=== How to Create a Good Password ===<br />
<br />
* Think about your favorite lines of a song, poem, or movie, etc. Take the first letters and special characters to create your password. <br />
<br />
Here's an example:<br />
Are you lonesome tonight? <br />
Do you miss me tonight?<br />
Are you sorry we drifted apart?<br />
<br />
The resulting password might be: Ayl2n?Dymm2n?Ayswda?<br />
<br />
* Think about approx. 4 different words which make sense for you but in general, the combination does not make any sense at all. Meaningful sentences are no good passwords.<br />
<br />
Here's an example:<br />
Concrete<br />
Ocean<br />
Mouse<br />
Egg<br />
<br />
You'll have to add a special character and a digit. The resulting password might be: ConcreteOcean4MouseEgg! <br />
<br />
== Further Advice for a Secure Password Usage ==<br />
<br />
=== Password Manager ===<br />
<br />
The use of a password manager solves the problem to remember numerous different passwords for various accounts. <br />
<br />
=== Two-Factor Authentication ===<br />
<br />
<br />
<br />
<br />
== Requirements ==<br />
<br />
none - so far...<br />
<br />
In order to complete these steps, you must have followed [[Some Other Documentation]] before.<br />
<br />
== Description ==<br />
<br />
=== Step 1 ===<br />
<br />
Enter these commands in the shell<br />
<br />
echo foo<br />
echo bar<br />
<br />
=== Step 2 ===<br />
<br />
Make sure to read<br />
<br />
* War and Peace<br />
* Lord of the Rings<br />
* The Baroque Cycle<br />
<br />
== Used Hardware ==<br />
<br />
[[Device to be used with this documentation]]<br />
[[Maybe another device to be used with this documentation]]<br />
<br />
== Courses ==<br />
<br />
* [[A course where this documentation was used]] (2017, 2018)<br />
* [[Another one]] (2018)<br />
<br />
== References ==<br />
<br />
* [1] https://www.owasp.org/images/1/1c/OWASP-IoT-Top-10-2018-final.pdf<br />
* [2] https://metro.co.uk/2019/12/19/10-worst-passwords-2019-revealed-nothing-changed-11932281/<br />
<br />
<br />
[[Category:Basic]]</div>Silviehttps://wiki.elvis.science/index.php?title=Password_Security&diff=3296Password Security2020-03-02T16:29:02Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
This documentation provides advice about secure passowrds. It covers known problems with passwords and elaborates various solutions for secure password creation and usage. The issue "bad passwords" is the number 1 vulnerability in the Internet-of-Things (IoT)[1].<br />
<br />
== Problems with Passwords ==<br />
<br />
There are several more or less widely known bad habits regarding passwords.<br />
<br />
=== The Password Quality ===<br />
<br />
'''Personal information''' is used to create passwords which is a polpular target for social engineering (names, dates, etc.). Often '''standard passwords''' like "123456" or "passowrd" are used. Actually, "123456" is the most used password for the last years [2]. The re-use of passwords is one of the main topics: many users use the '''same password for various accounts'''. It is obvious that it is not a good idea to use the same password for online banking and for Adobe account. <br />
<br />
== Good Passwords ==<br />
<br />
There are 3 general aspects for good passwords: the length plays a main role, the pwassword must not be trivial, and the password must be easily memorized. Leet speak is not a good idea because meanwhile all password crackers know leet speak.<br />
<br />
=== Good Password Checklist ===<br />
<br />
* Minimum length of 12 characters<br />
* Contains lower & upper case letters, digits, and special characters<br />
* As random as possible<br />
* Easy to remember<br />
<br />
=== How to Create a Good Password ===<br />
<br />
* Think about your favorite lines of a song, poem, or movie, etc. Take the first letters and special characters to create your password. <br />
<br />
Here's an example:<br />
Are you lonesome tonight? <br />
Do you miss me tonight?<br />
Are you sorry we drifted apart?<br />
<br />
The resulting password might be: Ayl2n?Dymm2n?Ayswda?<br />
<br />
* Think about approx. 4 different words which make sense for you but in general, the combination does not make any sense at all. Meaningful sentences are no good passwords.<br />
<br />
Here's an example:<br />
Concrete<br />
Ocean<br />
Mouse<br />
Egg<br />
<br />
You'll have to add a special character and a digit. The resulting password might be: ConcreteOcean4MouseEgg! <br />
<br />
== Further Advice for Password Usage ==<br />
<br />
=== Password Manager ===<br />
<br />
The use of a password manager solves the problem to remember numerous different passwords for various accounts. <br />
<br />
=== Two-Factor Authentication ===<br />
<br />
<br />
<br />
<br />
== Requirements ==<br />
<br />
none - so far...<br />
<br />
In order to complete these steps, you must have followed [[Some Other Documentation]] before.<br />
<br />
== Description ==<br />
<br />
=== Step 1 ===<br />
<br />
Enter these commands in the shell<br />
<br />
echo foo<br />
echo bar<br />
<br />
=== Step 2 ===<br />
<br />
Make sure to read<br />
<br />
* War and Peace<br />
* Lord of the Rings<br />
* The Baroque Cycle<br />
<br />
== Used Hardware ==<br />
<br />
[[Device to be used with this documentation]]<br />
[[Maybe another device to be used with this documentation]]<br />
<br />
== Courses ==<br />
<br />
* [[A course where this documentation was used]] (2017, 2018)<br />
* [[Another one]] (2018)<br />
<br />
== References ==<br />
<br />
* [1] https://www.owasp.org/images/1/1c/OWASP-IoT-Top-10-2018-final.pdf<br />
* [2] https://metro.co.uk/2019/12/19/10-worst-passwords-2019-revealed-nothing-changed-11932281/<br />
<br />
<br />
[[Category:Basic]]</div>Silviehttps://wiki.elvis.science/index.php?title=Password_Security&diff=3295Password Security2020-03-02T15:35:56Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
This documentation provides advice about secure passowrds. It covers known problems with passwords and elaborates various solutions for secure password creation and usage. The issue "bad passwords" is the number 1 vulnerability in the Internet-of-Things (IoT)[1].<br />
<br />
== Problems with Passwords ==<br />
<br />
There are several more or less widely known bad habits regarding passwords.<br />
<br />
=== The Password Quality ===<br />
<br />
'''Personal information''' is used to create passwords which is a polpular target for social engineering (names, dates, etc.). Often '''standard passwords''' like "123456" or "passowrd" are used. Actually, "123456" is the most used password for the last years [2]. The re-use of passwords is one of the main topics: many users use the '''same password for various accounts'''. It is obvious that it is not a good idea to use the same password for online banking and for Adobe account. <br />
<br />
== Good Passwords ==<br />
<br />
There are 3 general aspects for good passwords: the length plays a main role, the pwassword must not be trivial, and the password must be easily memorized. Leet speak is not a good idea because meanwhile all password crackers know leet speak.<br />
<br />
=== Good Password Checklist ===<br />
<br />
* Minimum length of 12 characters<br />
* Contains lower & upper case letters, digits, and special characters<br />
* As random as possible<br />
* Easy to remember<br />
<br />
=== How to Create a Good Password ===<br />
<br />
* Think about your favorite lines of a song, poem, or movie, etc. Take the first letters and special characters to create your password. <br />
<br />
Here's an example:<br />
Are you lonesome tonight? <br />
Do you miss me tonight?<br />
Are you sorry we drifted apart?<br />
<br />
The resulting password might be: Ayl2n?Dymm2n?Ayswda?<br />
<br />
* Think about approx. 4 different words which make sense for you but in general, the combination does not make any sense at all. Meaningful sentences are no good passwords.<br />
<br />
Here's an example:<br />
Concrete<br />
Ocean<br />
Mouse<br />
Egg<br />
<br />
You'll have to add a special character and a digit. The resulting password might be: ConcreteOcean4MouseEgg! <br />
<br />
== Further Advice for Password Usage ==<br />
<br />
PWD manager<br />
U2F<br />
<br />
<br />
== Requirements ==<br />
<br />
none - so far...<br />
<br />
In order to complete these steps, you must have followed [[Some Other Documentation]] before.<br />
<br />
== Description ==<br />
<br />
=== Step 1 ===<br />
<br />
Enter these commands in the shell<br />
<br />
echo foo<br />
echo bar<br />
<br />
=== Step 2 ===<br />
<br />
Make sure to read<br />
<br />
* War and Peace<br />
* Lord of the Rings<br />
* The Baroque Cycle<br />
<br />
== Used Hardware ==<br />
<br />
[[Device to be used with this documentation]]<br />
[[Maybe another device to be used with this documentation]]<br />
<br />
== Courses ==<br />
<br />
* [[A course where this documentation was used]] (2017, 2018)<br />
* [[Another one]] (2018)<br />
<br />
== References ==<br />
<br />
* [1] https://www.owasp.org/images/1/1c/OWASP-IoT-Top-10-2018-final.pdf<br />
* [2] https://metro.co.uk/2019/12/19/10-worst-passwords-2019-revealed-nothing-changed-11932281/<br />
<br />
<br />
[[Category:Basic]]</div>Silviehttps://wiki.elvis.science/index.php?title=Password_Security&diff=3294Password Security2020-03-02T15:28:24Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
This documentation provides advice about secure passowrds. It covers known problems with passwords and elaborates various solutions for secure password creation and usage. The issue "bad passwords" is the number 1 vulnerability in the Internet-of-Things (IoT)[1].<br />
<br />
== Problems with Passwords ==<br />
<br />
There are several more or less widely known bad habits regarding passwords.<br />
<br />
=== The Password Quality ===<br />
<br />
'''Personal information''' is used to create passwords which is a polpular target for social engineering (names, dates, etc.). Often '''standard passwords''' like "123456" or "passowrd" are used. Actually, "123456" is the most used password for the last years [2]. The re-use of passwords is one of the main topics: many users use the '''same password for various accounts'''. It is obvious that it is not a good idea to use the same password for online banking and for Adobe account. <br />
<br />
== Good Passwords ==<br />
<br />
There are 3 general aspects for good passwords: the length plays a main role, the pwassword must not be trivial, and the password must be easily memorized. Leet speak is not a good idea because meanwhile all password crackers know leet speak.<br />
<br />
=== Good Password Checklist ===<br />
<br />
* Minimum length of 12 characters<br />
* Contains lower & upper case letters, digits, and special characters<br />
* As random as possible<br />
* Easy to remember<br />
<br />
=== How to Create a Good Password ===<br />
<br />
* Think about your favorite lines of a song, poem, or movie, etc. Take the first letters and special characters to create your password. <br />
<br />
Here's an example:<br />
Are you lonesome tonight? <br />
Do you miss me tonight?<br />
Are you sorry we drifted apart?<br />
<br />
The resulting password might be: Ayl2n?Dymm2n?Ayswda?<br />
<br />
* Think about approx. 4 different words which make sense for you but in general, the combination does not make any sense at all. Meaningful sentences are no good passwords.<br />
<br />
Here's an example:<br />
Concrete<br />
Ocean<br />
Mouse<br />
Egg<br />
<br />
You'll have to add a special character and a digit. The resulting password might be: ConcreteOcean4MouseEgg! <br />
<br />
<br />
<br />
== Requirements ==<br />
<br />
none - so far...<br />
<br />
In order to complete these steps, you must have followed [[Some Other Documentation]] before.<br />
<br />
== Description ==<br />
<br />
=== Step 1 ===<br />
<br />
Enter these commands in the shell<br />
<br />
echo foo<br />
echo bar<br />
<br />
=== Step 2 ===<br />
<br />
Make sure to read<br />
<br />
* War and Peace<br />
* Lord of the Rings<br />
* The Baroque Cycle<br />
<br />
== Used Hardware ==<br />
<br />
[[Device to be used with this documentation]]<br />
[[Maybe another device to be used with this documentation]]<br />
<br />
== Courses ==<br />
<br />
* [[A course where this documentation was used]] (2017, 2018)<br />
* [[Another one]] (2018)<br />
<br />
== References ==<br />
<br />
* [1] https://www.owasp.org/images/1/1c/OWASP-IoT-Top-10-2018-final.pdf<br />
* [2] https://metro.co.uk/2019/12/19/10-worst-passwords-2019-revealed-nothing-changed-11932281/<br />
<br />
<br />
[[Category:Basic]]</div>Silviehttps://wiki.elvis.science/index.php?title=Password_Security&diff=3293Password Security2020-03-02T15:17:04Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
This documentation provides advice about secure passowrds. It covers known problems with passwords and elaborates various solutions for secure password creation and usage. The issue "bad passwords" is the number 1 vulnerability in the Internet-of-Things (IoT)[1].<br />
<br />
== Problems with Passwords ==<br />
<br />
There are several more or less widely known bad habits regarding passwords.<br />
<br />
=== The Password Quality ===<br />
<br />
'''Personal information''' is used to create passwords which is a polpular target for social engineering. Often '''standard passwords''' like "123456" or "passowrd" are used. Actually, "123456" is the most used password for the last years [2]. The re-use of passwords is one of the main topics: many users use the '''same password for various accounts'''. It is obvious that it is not a good idea to use the same password for online banking and for Adobe account. <br />
<br />
== Good Passwords ==<br />
<br />
There are 3 general aspects for good passwords: the length plays a main role, the pwassword must not be trivial, and the password must be easily memorized. Leet speak is not a good idea because meanwhile all password crackers know leet speak.<br />
<br />
=== Good Password Checklist ===<br />
<br />
* Minimum length of 12 characters<br />
* Contains lower & upper case letters, digits, and special characters<br />
* As random as possible<br />
* Easy to remember<br />
<br />
=== How to Create a Good Password ===<br />
<br />
* Think about your favorite lines of a song, poem, or movie, etc. Take the first letters and special characters to create your password. <br />
<br />
Here's an example:<br />
Are you lonesome tonight? <br />
Do you miss me tonight?<br />
Are you sorry we drifted apart?<br />
<br />
Resulting password: Ayl2n?Dymm2n?Ayswda?<br />
<br />
<br />
== Requirements ==<br />
<br />
none - so far...<br />
<br />
In order to complete these steps, you must have followed [[Some Other Documentation]] before.<br />
<br />
== Description ==<br />
<br />
=== Step 1 ===<br />
<br />
Enter these commands in the shell<br />
<br />
echo foo<br />
echo bar<br />
<br />
=== Step 2 ===<br />
<br />
Make sure to read<br />
<br />
* War and Peace<br />
* Lord of the Rings<br />
* The Baroque Cycle<br />
<br />
== Used Hardware ==<br />
<br />
[[Device to be used with this documentation]]<br />
[[Maybe another device to be used with this documentation]]<br />
<br />
== Courses ==<br />
<br />
* [[A course where this documentation was used]] (2017, 2018)<br />
* [[Another one]] (2018)<br />
<br />
== References ==<br />
<br />
* [1] https://www.owasp.org/images/1/1c/OWASP-IoT-Top-10-2018-final.pdf<br />
* [2] https://metro.co.uk/2019/12/19/10-worst-passwords-2019-revealed-nothing-changed-11932281/<br />
<br />
<br />
[[Category:Basic]]</div>Silviehttps://wiki.elvis.science/index.php?title=Password_Security&diff=3292Password Security2020-03-02T15:08:32Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
This documentation provides advice about secure passowrds. It covers known problems with passwords and elaborates various solutions for secure password creation and usage. The issue "bad passwords" is the number 1 vulnerability in the Internet-of-Things (IoT)[1].<br />
<br />
== Problems with Passwords ==<br />
<br />
There are several more or less widely known bad habits regarding passwords.<br />
<br />
=== The Password Quality ===<br />
<br />
'''Personal information''' is used to create passwords which is a polpular target for social engineering. Often '''standard passwords''' like "123456" or "passowrd" are used. Actually, "123456" is the most used password for the last years [2]. The re-use of passwords is one of the main topics: many users use the '''same password for various accounts'''. It is obvious that it is not a good idea to use the same password for online banking and for Adobe account. <br />
<br />
== Good Passwords ==<br />
<br />
There are 3 general aspects for good passwords: the length plays a main role, the pwassword must not be trivial, and the password must be easily memorized.<br />
<br />
=== Good Password Checklist ===<br />
<br />
* Minimum length of 12 characters<br />
* Contains lower & upper case letters, digits, and special characters<br />
* As random as possible<br />
* Easy to remember<br />
<br />
== How to Create a Good Password ==<br />
<br />
<br />
<br />
<br />
== Requirements ==<br />
<br />
none - so far...<br />
<br />
In order to complete these steps, you must have followed [[Some Other Documentation]] before.<br />
<br />
== Description ==<br />
<br />
=== Step 1 ===<br />
<br />
Enter these commands in the shell<br />
<br />
echo foo<br />
echo bar<br />
<br />
=== Step 2 ===<br />
<br />
Make sure to read<br />
<br />
* War and Peace<br />
* Lord of the Rings<br />
* The Baroque Cycle<br />
<br />
== Used Hardware ==<br />
<br />
[[Device to be used with this documentation]]<br />
[[Maybe another device to be used with this documentation]]<br />
<br />
== Courses ==<br />
<br />
* [[A course where this documentation was used]] (2017, 2018)<br />
* [[Another one]] (2018)<br />
<br />
== References ==<br />
<br />
* [1] https://www.owasp.org/images/1/1c/OWASP-IoT-Top-10-2018-final.pdf<br />
* [2] https://metro.co.uk/2019/12/19/10-worst-passwords-2019-revealed-nothing-changed-11932281/<br />
<br />
<br />
[[Category:Basic]]</div>Silviehttps://wiki.elvis.science/index.php?title=Password_Security&diff=3291Password Security2020-03-02T15:04:48Z<p>Silvie: </p>
<hr />
<div>== Summary == <br />
<br />
This documentation provides advice about secure passowrds. It covers known problems with passwords and elaborates various solutions for secure password creation and usage. The issue "bad passwords" is the number 1 vulnerability in the Internet-of-Things (IoT)[1].<br />
<br />
== Problems with Passwords ==<br />
<br />
There are several more or less widely known bad habits regarding passwords.<br />
<br />
=== The Password Quality ===<br />
<br />
'''Personal information''' is used to create passwords which is a polpular target for social engineering. Often '''standard passwords''' like "123456" or "passowrd" are used. Actually, "123456" is the most used password for the last years [2]. The re-use of passwords is one of the main topics: many users use the '''same password for various accounts'''. It is obvious that it is not a good idea to use the same password for online banking and for Adobe account. <br />
<br />
=== Good Passwords ===<br />
<br />
There are 3 general aspects for good passwords: the length plays a main role, the pwassword must not be trivial, and the password must be easily memorized.<br />
<br />
Good password '''checklist''':<br />
<br />
* Minimum length of 12 characters<br />
* Contains lower & upper case letters, digits, and special characters<br />
* As random as possible<br />
* Easy to remember<br />
<br />
<br />
== Requirements ==<br />
<br />
none - so far...<br />
<br />
In order to complete these steps, you must have followed [[Some Other Documentation]] before.<br />
<br />
== Description ==<br />
<br />
=== Step 1 ===<br />
<br />
Enter these commands in the shell<br />
<br />
echo foo<br />
echo bar<br />
<br />
=== Step 2 ===<br />
<br />
Make sure to read<br />
<br />
* War and Peace<br />
* Lord of the Rings<br />
* The Baroque Cycle<br />
<br />
== Used Hardware ==<br />
<br />
[[Device to be used with this documentation]]<br />
[[Maybe another device to be used with this documentation]]<br />
<br />
== Courses ==<br />
<br />
* [[A course where this documentation was used]] (2017, 2018)<br />
* [[Another one]] (2018)<br />
<br />
== References ==<br />
<br />
* [1] https://www.owasp.org/images/1/1c/OWASP-IoT-Top-10-2018-final.pdf<br />
* [2] https://metro.co.uk/2019/12/19/10-worst-passwords-2019-revealed-nothing-changed-11932281/<br />
<br />
<br />
[[Category:Basic]]</div>Silvie