-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maybe just wrong display infos #1
Comments
Try to Start this way: kelloq.exe 0x11223344 0x55667788 0x99aabbcc So you have to enter 3 hopping Codes that are captured in sequence. |
It's exactly what I'm doing: KeeLoq.exe 0xDC3BD2C9 0x3F21F56A 0xE92A6DE3 But the output is: Hoppingcodes: 0x00000000 0x00000000 0x00000000 |
Oh. Will take a Look tomorrow... It is Just a proof of concept. Never got a Key this way. I use this now for cracking seed Codes for secure learning in keeloq algorithm. |
ok, but...can it be a problem the fact that i'm not using a cuda system? (i know it could take days...i don't have a cuda system right now) |
Without a cuda card it wont work. This is why you get 0x00000000... The Software does copy the hopping Codes into cuda RAM and back to Display on Screen. If you dont have any cuda card, this wont work. An other bruteforcer doesnt make sense, because of the huge keyspace of 64bit. Which System Do you try to brute force? |
My FAAC garage door, recorded with my flipper zero the keys and trying with your utility. |
Can you provide a serial number, so i can check, if i have the manufacturer Key already... |
Great code! Would it be 32 faster using the bit-slicing approach from Giovanni Agosta? He an his team use bit-slicing and work at the same time in 32 Registers. |
My cuda Code works on 8192 independend keys in parallel, so i dont know if bitslicing would make it any faster. |
When I launch with the correct parameters it shows
Hoppingcodes: 0x00000000 0x00000000 0x00000000
Startkey: 0xc01108f4dc2baaf
Is it normal that it shows "Hoppingcodes: 0x00000000 0x00000000 0x00000000" ?
The text was updated successfully, but these errors were encountered: