Closed willem640 closed 1 year ago
Don't mind the commits, but I found another file where this was happening so I made the function visible in a header and included it
Love your effort @willem640 ! Just FYI this branch caused a segfault for me during an attempt to crack a Mifare Classic 4K card.
That happened to me too, but also on the main branch. I'll run valgrind on it though before it should be merged
This is embarrassing - please ignore my previous comment. The build I was running was from the main branch, not @willem640 's.
I was able to collect a further 8 or so keys with a build from this branch before it once again got stuck in the same loop of seemingly finding the same key over and over again (like with the main branch, only later this time). No segfaults.
I spoke too soon once again, just experienced a segfault.
Huh, that's interesting. I just got a few cards in the mail so I'll have to test it some more :P
For reference, this was an OV-Chipkaart (Dutch public transport)
Final update: after leaving it running overnight "just in case" the remaining keys were retrieved. Segfault issue seems unpredictable ¯_(ツ)_/¯
Thanks @willem640 !
I can't get it to segfault anymore, but considering it also happens on the main branch (and the nature of the thing I edited), I don't think any of the code that was changed in this PR is segfaulting
...and as I see software can't to write dumps
I’m not sure what you mean, could you try rephrasing?
Well, buddy I successfully managed to open the S070 4K card which was stumbling while reading sector 33. So you did a great job! One thing - the code does not have a dump write function. Can you add write 4k dumps?
Ah, in that case I recommend opening a separate issue on the project. You’re currently commenting on an unrelated (and closed) pull request
This piece of code didn't use the sector_to_block function and as such the hardnested attack was broken for 4k cards, because those have larger sectors at the end of the card.