This commit is contained in:
Philippe Teuwen 2021-04-16 00:21:22 +02:00
parent f63125386b
commit 741cdfc383
3 changed files with 4 additions and 4 deletions

View file

@ -1897,7 +1897,7 @@ void ReaderHitag(hitag_function htf, hitag_data *htd) {
LogTrace(rx, nbytes(rxlen), response_start, response_start + response_duration, NULL, false);
// TODO when using cumulative time for command_start, pm3 doesn't reply anymore, e.g. on lf hitag read 23 4F4E4D494B52
// TODO when using cumulative time for command_start, pm3 doesn't reply anymore, e.g. on lf hitag reader --23 -k 4F4E4D494B52
// Use delta time?
// command_start = response_start + response_duration;
command_start = 0;

View file

@ -79,4 +79,4 @@ lf t55xx sniff -1
It uses the existing `lf sniff` command to collect the data, so setting that first as per normal sniffing is recommended. Once you have a sniff, you can "re-sniff" from the stored sniffed data and try different settings, if you think the data is not clean.
As normal, the cloner may write data past the end of the 40K sample buffer. So using the `lf config s <x bytes>` then re-run the sniff to see if there is more data.
As normal, the cloner may write data past the end of the 40K sample buffer. So using the `lf config -s <x bytes>` then re-run the sniff to see if there is more data.

View file

@ -167,7 +167,7 @@ response pairs for the same tag UID.
**TODO** will be ht2 sim or sniff with actual tag ?
```
pm3 --> lf hitag sniff l
pm3 --> lf hitag sniff
```
It creates a file `Hitag2_<UID>_<nR>_<aR>_collection.txt`.
@ -184,7 +184,7 @@ Attack 4 requires the same information as attack 3, but only 16-32 encrypted
nonce and challenge response pairs are required.
```
pm3 --> lf hitag sniff l
pm3 --> lf hitag sniff
```
It creates a file `Hitag2_<UID>_<nR>_<aR>_collection.txt`.