View Full Version : Keylok II dongle [edit]

October 14th, 2012, 01:28

I've the capture data of keylok II dongle by using USBtrace SysNucleus. Can I remove the keylok II dongle protection by using the information on this save log file? Is that enough for me to capture all my dongle information?

Thanks in advance.

Best Regards,

October 14th, 2012, 08:01
> Can I remove ...

> enough for ...
yes, for this release of the target software

October 14th, 2012, 09:54
Thanks FoxB,

I'm really happy once you said that so. I've learned from zero about dongle protection since 2 months ago. Now, I knew that my effort on the right direction to solve this problem.But, still knew that a lots of things need to be discovered and also need supervision.

Can you tell me how to know this KeyLok priority data? There are 2655 sequence total data was captured during full program executed. The first program executed start 1-2424 sequence and second executed consists of 2425-2655 sequence. I try to understand the data captured in buffer snippet which is in hex form.But, I got headache since there are a lots of sequence data captured. What is the URB that should I select in order to filter unnecessary data? Perhaps,can you show me what's a next steps that should I do with this data?

October 14th, 2012, 10:23
try to understand two way aka packet cipher/decipher:

first: program api interface->keylock system driver->dongle

second: dongle->keylock system driver->program api interface

it is done =)

October 14th, 2012, 15:46
Indeed, all you have to do is give the program what it wants to see and viola, the protection is defeated.

Of course, the data might change on each run, with time, etc. So you have a lot more analysis work to do yet.

Yes, its not easy, but if it was, dongle creators would be out of a job very quickly!

October 15th, 2012, 06:49
Thanks FoxB,

Wow,It seems like forward & reverse steps to measure. And it's very though to know this. Perhaps,can I use Ollydbg tools to do this steps that you mention?

October 15th, 2012, 07:06
Ollydbg is user mode debugger, you may need something that can debug the lower rings where device drivers live, like Windbg.

October 15th, 2012, 08:07
Thanks squidge for this info

Ermm..WinDdbg? It sounds new to me. Do you have any preferences website to learn this things? By the way, I'll try goggle this stuff. Hopefully, there are a lots of tutorial outside there.

Best Regards,