Why not use the MFOC fork from vk496 that implements the hardnested attack and is faster in performing it? I have not encountered a scenario when I could find no solution either. Could the hardnested attack implementation make it into miLazyCracker?
Actually, miLazyCracker and this fork of MFOC seem redundant to me at this point, with miLazyCracker being slower, but there must be an explanation. What are the advantadges of the implementation as seen in miLazyCracker? I guess less resources needed?
On an ARM architecture (Raspberry Pi 3 with Raspbian 32 bits or Kali 64 bits), miLazyCracker is the only tool that will work for me to perform the hardnested attack, as the MFOC fork won't compile, and the Proxmark3 hardnested attack needs more memory than the Raspberry Pi 3 can allocate, so miLazyCracker is still pretty useful.
I just thought it might be improved with a different implementation of the attack?
Hello, I am new to GitHub.
Why not use the MFOC fork from vk496 that implements the hardnested attack and is faster in performing it? I have not encountered a scenario when I could find no solution either. Could the hardnested attack implementation make it into miLazyCracker?
https://github.com/vk496/mfoc
Actually, miLazyCracker and this fork of MFOC seem redundant to me at this point, with miLazyCracker being slower, but there must be an explanation. What are the advantadges of the implementation as seen in miLazyCracker? I guess less resources needed?
On an ARM architecture (Raspberry Pi 3 with Raspbian 32 bits or Kali 64 bits), miLazyCracker is the only tool that will work for me to perform the hardnested attack, as the MFOC fork won't compile, and the Proxmark3 hardnested attack needs more memory than the Raspberry Pi 3 can allocate, so miLazyCracker is still pretty useful.
I just thought it might be improved with a different implementation of the attack?
Thank you, Regards!