Proxmark3 community
Research, development and trades concerning the powerful Proxmark3 device.
Remember; sharing is caring. Bring something back to the community.
"Learn the tools of the trade the hard way." +Fravia
You are not logged in.
Announcement
Time changes and with it the technology
Proxmark3 @ discord
Users of this forum, please be aware that information stored on this site is not private.
Pages: 1
#1 2019-12-13 10:12:57
- Mashid0
- Contributor
- Registered: 2019-12-02
- Posts: 28
hf mf hardnested // textual
[usb] pm3 --> hf mf hardnested 0 A FFFFFFFFFFFF 4 A w
As I understand this case FFFFFFFFFFFF must be [known target key (12 hex symbols)] as mentioned in help command
[usb] pm3 --> hf mf hardnested h
Usage:
hf mf hardnested <block number> <key A|B> <key (12 hex symbols)>
<target block number> <target key A|B> [known target key (12 hex symbols)] [w] [s]
or hf mf hardnested r [known target key]But on running command we will read known target key: 0x000000000000 (not set)
It it correct?
--target block no: 4, target key type:A, known target key: 0x000000000000 (not set), file action: write, Slow: No, Tests: 0
[+] Using AVX2 SIMD core.
time | #nonces | Activity | expected to brute force
| | | #states | time
------------------------------------------------------------------------------------------------------
0 | 0 | Start using 8 threads and AVX2 SIMD core | |
0 | 0 | Brute force benchmark: 1252 million (2^30.2) keys/s | 140737488355328 | 31h
1 | 0 | Using 235 precalculated bitflip state tables | 140737488355328 | 31h
4 | 0 | Writing acquired nonces to binary file hf-mf-7985DF4D-nonces.bin | 140737488355328 | 31h
4 | 1 | Apply bit flip properties | 140737488355328 | 31h
5 | 1 | Apply bit flip properties | 140737488355328 | 31h
6 | 1 | Apply bit flip properties | 140737488355328 | 31h
7 | 1 | Apply bit flip properties | 140737488355328 | 31h
7 | 1 | Apply bit flip properties | 140737488355328 | 31h
8 | 1 | Apply bit flip properties | 140737488355328 | 31h
Also small design issue with lent of one of the rows
1 | 0 | Using 235 precalculated bitflip state tables | 140737488355328 | 31h
4 | 0 | Writing acquired nonces to binary file hf-mf-7985DF4D-nonces.bin | 140737488355328 | 31h
4 | 1 | Apply bit flip properties | 140737488355328 | 31h it always be longer than expected for the table column
may be just skip one word from the phrase?
This case it will looks like:
1 | 0 | Using 235 precalculated bitflip state tables | 140737488355328 | 31h
4 | 0 | Writing nonces to binary file hf-mf-7985DF4D-nonces.bin | 140737488355328 | 31h
4 | 1 | Apply bit flip properties | 140737488355328 | 31h Offline
#2 2019-12-13 17:33:56
- iceman
- Administrator
- Registered: 2013-04-25
- Posts: 9,537
- Website
Re: hf mf hardnested // textual
I tend to not favor the mixed output of different log messages in such column fashion. Others do.
Offline
#3 2019-12-13 19:15:59
- Mashid0
- Contributor
- Registered: 2019-12-02
- Posts: 28
Re: hf mf hardnested // textual
I agree with you.
This case better to form empty file and output message before the table
or at list At the first or second row of a table
time | #nonces | Activity | expected to brute force
| | | #states | time
------------------------------------------------------------------------------------------------------
0 | 0 | Writing nonces to binary file hf-mf-7985DF4D-nonces.bin | |
0 | 0 | Start using 8 threads and AVX2 SIMD core | |
0 | 0 | Brute force benchmark: 1252 million (2^30.2) keys/s | 140737488355328 | 31h
1 | 0 | Using 235 precalculated bitflip state tables | 140737488355328 | 31h
4 | 1 | Apply bit flip properties | 140737488355328 | 31h any case it's clear 
Offline
Pages: 1