github/RRG-Proxmark3
1
0
Fork 0
mirror of https://github.com/RfidResearchGroup/proxmark3.git synced 2025-08-14 10:37:23 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

text

Browse source
This commit is contained in:
Philippe Teuwen 2021-01-14 11:33:29 +01:00
commit 4af9777af6
2 changed files with 13 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

14
tools/hitag2crack/README.md
View file

@ -5,7 +5,7 @@ Authors:
* Attacks 1, 2, 3, 4 : Kevin Sheldrake <kev@headhacking.com>
* Attacks 5, 5gpu : anonymous, based on https://github.com/factoritbv/hitag2hell by FactorIT B.V.
* Attacks 5, 5opencl : Gabriele Gristina <gabriele.gristina@gmail.com>, based on 5gpu
* Attack 5opencl : Gabriele Gristina <gabriele.gristina@gmail.com>, based on 5gpu
Introduction
------------
@ -108,6 +108,12 @@ Attack 5gpu
Attack 5gpu is identical to attack 5, simply the code has been ported to OpenCL
to run on GPUs and is therefore much faster than attack 5.
Attack 5opencl
--------------
Attack 5opencl is an optimized OpenCL version based on 5gpu.
It runs on multi GPUs/CPUs and is faster than 5gpu.
Usage details: Attack 1
-----------------------
@ -209,7 +215,7 @@ $ ./ht2crack5 <UID> <nR1> <aR1> <nR2> <aR2>
Usage details: Attack 5gpu/5opencl
----------------------------------
Attack 5gpu requires two encrypted nonce and challenge
Attacks 5gpu and 5opencl require two encrypted nonce and challenge
response value pairs (nR, aR) for the tag's UID.
```
@ -221,13 +227,13 @@ Stop once you got two pairs.
$ ./ht2crack5gpu <UID> <nR1> <aR1> <nR2> <aR2>
```
Attack 5opencl requires the same of 5gpu version.
or
```
$ ./ht2crack5opencl <UID> <nR1> <aR1> <nR2> <aR2>
```
More details in crack5opencl/README.md
5opencl supports a number of additional parameters, see crack5opencl/README.md for details.
Usage details: Next steps
-------------------------

6
tools/hitag2crack/crack5opencl/README.md
View file

@ -26,10 +26,10 @@ encrypted nonces and challenge response values. They should be in hex.
UID is the UID of the tag that you used to gather the nR aR values.
Following the help:
Usage:
```
$ ./ht2crack5opencl
$ ./ht2crack5opencl
./ht2crack5opencl [options] {UID} {nR1} {aR1} {nR2} {aR2}
Options:
@ -50,7 +50,7 @@ Example, select devices 1, 2 and 3 using platform 1 and 2, with random queue eng
./ht2crack5opencl -D 2 -Q 2 -p 1,2 -d 1,2,3 2ab12bf2 4B71E49D 6A606453 D79BD94B 16A2255B
```
You can found the correct OpenCL Platform ID's (-p) and Device ID's (-d) by:
You can find the correct OpenCL Platform ID (-p) and Device ID (-d) with:
```
./ht2crack5opencl -s