How to enable all function with superpro dongle emulator

[bybyby]

Dear all:
I have managed to emulate a superpro dongle, the software name is Midas Civil,but I can't use the Push Over function with the emulator, but the real hard usb dongle can use. I dump the dongle wiht PVA3.3 and not choosed the WP option,and the emulator is vsubs emulator. Does anybody have idear to enable all fuctions of the dongle with the emulator or have managed emulate all funcitons of this software? Thank you.

[foffa]

@bybyby

is just the cells non active but have data

or cells have no data and not active

you need WP OWP1 & OWP2

and using sproeval you can activate cells or write it

but there is must be more work about that

[SonofabiT]

I dump the dongle wiht PVA3.3 and not choosed the WP option,and the emulator is vsubs emulator.
You should enable brute force WP on the PVA 3.3 dumper because your sentinel type is superpro.

Does anybody have idear to enable all fuctions of the dongle with the emulator or have managed emulate all funcitons of this software?
Are there any addition protection scheme such as a license file or any serial number ?

[Git]

You should enable brute force WP on the PVA 3.3 dumper because your sentinel type is superpro.

Whoa!. Careful!. No!. You can no longer make that assumption. Use the latest sentinel drivers, issue a GetKeyInfoEx() and look carefully at the info that returns. Only bt careful analysis of this dongle data can you now assume it is safe to brute the WP. The latest superpro will be locked out just as easily as ultrapros.

I *think* all purple superpro are safe, but I would still be careful.

Git

[SonofabiT]

Did you mean like a XM type of Superpro dongle which had 256 cells ?

[foffa]

@sonofabit
there is many types know of sentinel keys
also new types could be locked easily according to developer choice
good user to be safe should uncheck BWP

ALSO 256 CELLS DOES NOT MEAN 100% XM :)

[Git]

nothing to do with XM. XM only means 256 cells instead of 64 cells and has no bearing on if you can bruteforce the WP or not. You have to query the device capabilities with GetKeyInfoEx(). Use a code snippet like this skeleton :


// ...
#include "spromeps.h"
// ...
NSPRO_MONITOR_INFO_EX info;
// open dongle in normal way with API functions
RNBOsproGetKeyInfoEx(lpApiPkt, 0, 0, 0, &info, sizeof(NSPRO_MONITOR_INFO_EX));
if(info.sproKeyMonitorInfo.capabilities & SP_CAPS_PASSWORD_COUNTER)
{
printf(" *******!!!! DO NOT BRUTEFORCE WP !!!!*******\n");
}


It is possible to find the actual value of the password counters, but only if you have the Developer Code which is encrypted into a *.dev file by safenet and only given to owner of the dongle DevID. There is 1 counter for WP and a second for OWP1 and OWP2. Both normally have a value of 15. Each time a wrong password is supplied, the counter is decremented by 1. If a correct password is supplied, the counter is reset to 15. If the counter reaches 0 the dongle is disabled. If the Developer Code is passed incorrect, or the dongle does not have the password counter facility the counter will return 255 as an error.

Git


Git

[bybyby]

@bybyby

you need WP OWP1 & OWP2

and using sproeval you can activate cells or write it

but there is must be more work about that

Dear guys:
I have found the reason because the original superpro dongle didn't have the pushover fuction. I emulated another superpro dongle which have the pushover function use pva and dmp2mkey and the emulator have the pushover funtion. So it is a mistake. I am sorry to confuse all of you.:p

[Git]

What is the pushover function ?

Git

[bybyby]

It is a function of this software. Nothing to do with the superpro dongle. The software company sale the software with different module by the different price.

[Git]

OK, thanks for the answer. By the way, can you please NOT quote the entire message you are replying to. We can all see the original message so it is a complete waste of time and space and makes the thread more difficult to read.

Git

[yogi_saw]

If a correct password is supplied, the counter is reset to 15. If the counter reaches 0 the dongle is disabled.
Git
does ne one know what it actually does to destroy itself does it fill all cells with 0 or what else
can we restore it to working condition by any trick

[Git]

It simply stops responding as a dongle. Only solution is to send it back to the distributor.

Git

[yogi_saw]

but wat changes exactly it will change so that the dongle will be disabled

[Git]

It is internally disabled by itself. There is nothing you can do to recover it, it has to be reprogrammed as a dongle by a distributor with custom hardware and software.

Git

[CARLOS ALBERTO PESTANA]

I have a dongle emulator for superpro dongle that's work fine (pva/dmp2mkey/multikey).
I have a problem, for each version of my software I need a new key number. I enter key number/license authentication (16 characters) in a dialog box. When I click in new file or open a file my software read dongle and cells/algo and check if key number entered is correct.

Anyone can give me some suggestions of tools and advice to study how to find this key number.
Thanks

[BfoX]

@CARLOS ALBERTO PESTANA: remove a protection shell from files and search inside...

[CARLOS ALBERTO PESTANA]

@BfoX,
I am a newbie and I am studying.

remove a protection shell from files: could you suggest tools to use?

Search inside: it does it mean to use debuggers? I tried ollydbg without sucess. Have I use others debuggers ?

Thanks a lot.