Hello,
I am kind of new at this so I would appreciate if you didn't rush me. I began the other days to study for making a crack for a soft that uses Sentinel Ultra Pro Dongle. I'm trying to change the exe file in order to remove the need of the dongle. What I have done so far is to dump the content of the dongle and I have disassembled the exe file with IDA Pro. I tried to look in the code for places where a cmp is done with the values from the cells of the dongle and I am trying to patch the jumps.
Any sugestions are welcomed as I have seen that some of you are gurus in cracking the "gay" dongle.

Later that evening....Edit:

After a closer look at the code I observed that the functions related to the dongle can be found in sx32w.dll. So the first idea of the post goes right to hell (and i'm sorry for the spam).
Has anyone of you tried and succeeded in patching that library (i guess it contains the API functions from sentinel) and make a software running only with that or one has to go deeper. By deeper I mean to patch somehow the sentinel driver
Thanks again for the understanding.

Access to the dongle over sx32w.dll ?
May be it SuperPro?

In fact on the dongle it is written "Rainbow SuperPro" , but when I pluged it in the usb for the first time Windows said "Sentinel UltraPro".
Any way is it possible to patch only the DLL (only the used functions form it) or I have to look inside the drivers too ?

I have no experience with the ULTRA Pro, but a long time ago I was working on a target that was just a sentinel pro. (The program sends it a string of characters, and it returns a 16-bit value). The target that I was working on was written in a high level language, so all the calls to the routines looked the same. (Byte wise). So, I searched the app, found all the instances of their calls, and the subsequent "CMP ax,GoodGuy" instructions, and made a table.

I then gutted the routine that talked to the dongle inside the .dll, and wrote a simple table lookup function that would search the table for the string, and return the proper bytes.


It might be that you could do the same thing here once you understand what the functions in the .dll do. Good luck!

Hi there,

You need not patch the drivers. Not necessary.

You need to check the *sproread and *sproquery functions and the _strcmp that they do. The _strcmp function is a home brewn routine, not the standard C one, the name is for easy identification.

Over and above these two functions which need to be emulated, the others are pretty much patch jumps and return 0 in eax variety.

Have Phun

thanks a lot for your valuable information.
I need to get the know-how now.

hi 2 all
hi big bro i have faced same problem early have any solution?

hi,
it is a super pro...my mistake
any way there are people on this forum who are willing to sell you a solution..not very expensive. it is not my case because i'm trying to either do it myself or to find someone who is willing to help me for free.

Howdy,

You send me a PM if there are people on MY forums trying to sell you shit.

Woodmann

Bravo, Woodmann...

Again and always, you have my deepest and utmost respect.
jb

Woodmann,

I recommend waterboarding followed by battery cables to the private parts - give me some time to think I'll come up with a few original ideas of my own.

SiGiNT

Thanks ,
I appreciate it.....NOOOOOOT

Marko,

Not intended for you only intended for anybody trying to sell "cracks" on this board, highly unethical and strictly against the rules.

SiGiNT

I am not trying to sell. I wish I had the solution but I don't.

Done
I have the sx32w.dll file and it works fine with my software.
What I want to do next is to disassemble both dlls and search for differences.
My purpose is to learn. I have read here somewhere that there is a little software that does this comparison for me..I'll search it.
Thank you for the ones that really tried to help and shame on those who tried to sell their solution.

http://research.eeye.com/html/tools/RT20060801-1.html

But if an executable is simply binary patched (contrary to patched in the source and then recompiled), you normally don't need these big guns, simply binary-compare the two files with any decent hex editor and then look at the found offsets in a disassembler.

this is the kind of tool I was looking for. Thanks. I have no clue how it works but I will rtfm. I will let you know of my progress.

Ok guys,
i changed my computer and now I have one that runs vista. I installed a virtual machine with usb support so that I will be able to follow this.
Big delay ...i know

The ida signature of sentinel ultropro, can help

hello,
As many of you know there is a general solution if one has the sentinel super pro dongle. There is a commercial emulator on the loose .
This thread ends here I guess.

thanks to PAPI