Need of assistant, it works almost

[capebyrun]

Salut,

I need your help at all,

the function of my software with the key USB make (normal)
and The Soft TORO Monitor 2.01 do that :...........

[cghots]

KeyType=7 -> ULP USB
:confused:

[pivasik]

ULP - UltraPro

[capebyrun]

Thank you for the answers

"usb keys indentification tool " found usb key............

[SonofabiT]

@capebyrun
I have a new SafeNet SuperPro dongle (Black-USB). I have used SSD 7.5 and get log from sentmon v2.01b. The log show me my Sentinel dongle is KeyType=7 -> ULP USB meanwhile my dongle is Super Pro one. I think sentmon v2.01b is geting old and old right know.

Better you show us the dongle photo or spro_RNBO.....dump file.

[Git]

Probably both SDHK in SSP mode.

Git

[capebyrun]

it is.............

[SonofabiT]

Out:> GetKeyType -> Status=0x0
KeyType=7 -> ULP USB
@capebyrun
Let us find out about your sentinel type. Is it realy Ultrapro, SuperPro XM, SuperPro (64 cell), or SDHK in SSP mode ? :confused:

Edit your old reg. See below :
Old reg:
"sntMemory"=hex:\
6A,52,xx,xx,00,00,00,00,08,00,00,00,2B,F8,00,00,\
New reg :
"sntMemory"=hex:\
..,..,xx,xx,00,00,00,00,F9,DC,00,00,2B,F8,00,00,\

Emulate your dongle and run your s/w. If it works then i conclude that your dongle type is Sentinel SUPER PRO. If it doesn't work then it is probably another sentinel type.

Also, it is probably SuperPro (64 cell) type but multikey ver. 0.16.0.1 - 0.18.1.0 could not yet emulate it. Read a useful hint in here ;) http://reteam.org/board/showpost.php?p=15047&postcount=9

[gus]

sonobafit , Please explain the change

we know that change of 08,00 -> F9,DC is WP, is that correct?

but the change of 0B,C8 -> 0E,C8,, Why?

thanks

[SonofabiT]

@gus - In my p.m, capebyrun tell me that his original dongle has not devid=0xc80b. :D

[gus]

lol,
:eek: :D :D
of course , hahahaha i no read "logs"

thanks

[capebyrun]

thanks a lot !.......

[GNIREENIGNE]

Why does your reg file include x/y?:


"sntMemory"=hex:\
yy,yy,xx,xx,00,00,00,00,00,00,00,00,2B,F8,00,00,\

-G

[SonofabiT]

Out:> GetKeyType -> Status=0x0
KeyType=7 -> ULP USB

Out:> GetKeyType -> Status=0x0
Memory Size=64
@capebyrun - I think it's right that Toro sentmon32 v 2.01b getting old and old right now. I wonder your dongle is Sentinel Super Pro and r-elite's multikey should able to emulate it. But strange...., different dumper and different solver give us different ssp and reg (multikey and vusbbus emul) file. ;)

Se carefully the content of cell1A and cell36 in the each reg. From your actual sentinel dongle, the two cells value of these regs are differs. ;)

I found somethings interest with your dumped-file generated by PVA 3.3. Check your P.M ... ;)

[crab]

@capebyrun hehe, I know the DevID and WP that SonofabiT show us ;)
I have the same software ... and same problem
Probably we can work in with

@all
Git is right it's SDHK in SPP mode
Emulation with mullikey is possible for old release of the software
But not after the switch of Sentinel Driver from 7.4 to 7.5

BR

[capebyrun]

@crab i think it's all right (what you write)
but i try to understand why........

[capebyrun]

01:55 AM
@SonofabiT
YEP
the last version "33" of the soft (with 7.5) don't still work........

[SonofabiT]

@capebyrun - I don't have the installer of your s/w and i don't understand the impact of s/w version if we modify the reg. I send the regs and you test them by your self. Now, try to set/change the following value on your reg.

test3.reg
cell36=0x0132 ; for version 32
The reason behind the above suggestion is because i had used another tch2000's solver and i saw the content of cell36 is 0x0132.

test4.reg
cell36=0x0133 ; for version 33.
The reason behind this suggestion is because i wonder if we replace the content of cell36 from 0x0132 to 0x0133, then we hope your reg will work on version "33" (with 7.5). :D

It's very important that the two byte are stored in reverse value in the reg file. Test the test3.reg and test4.reg to emulate both version (32 and 33) of your s/w.

There are also different value of cell0B and cell36. Check your P.M to see the content of the whole reg. :)

[crab]

I use same software, and same SDHK in SPP mode
I want to share a stange thing

My Tools :
PVA3.3 Dumper
Dmp2mKey 2.3
Mkey 1.8.1.0

Manipulation :
Create a reg in version 35 of the soft
apply version 36 patch
create a new reg

I notice that the two reg between a sohtware update are different
(cells 26, 27, 53, 55, 56)

[SonofabiT]

Manipulation :
Create a reg in version 35 of the soft
apply version 36 patch
create a new reg
Did you mean, for the same actual dongle (devid and sn),... Does the different version of your s/w ONLY will work with the specific version of Sentinel System Driver ?
I notice that the two reg between a sohtware update are different
(cells 26, 27, 53, 55, 56)
Did you mean..if you dump your dongle with SSD 7.0.4 and 7.0.5, both regs are differs, aren't they ?

btw, how did you sure that the dongle is SDHK in SPP mode ?

[crab]

Not exactly...
Same dongle, same SSD (7.5.0), same dumper, same solver only sw version upgrade but different cells 26, 27, 53, 55, 56 in reg file

btw, how did you sure that the dongle is SDHK in SPP mode

capebyrun post a picture -> SHK

USBDSearch.exe -> Rainbow/Sentinel dongle; SafeNet USB SuperPro/UltraPro

Identifier.exe -> Found USB Key Safenet Sentinel SuperPro/UltraPro

SHKDumper -> ! Error: ShkLib::ShkDevice::Open:: DeviceIoControl (). Code: 0x00000017

BR

[capebyrun]

it's good works.....

[crab]

no! no !
this error is other thing ! sure !
:cool:

I just want to show that this SHK is not in SHK mode ...

[capebyrun]

I just want to show that this SHK is not in SHK mode ...


ok ............:D

[SonofabiT]

Not exactly...
Same dongle, same SSD (7.5.0), same dumper, same solver only sw version upgrade but different cells 26, 27, 53, 55, 56 in reg file
@crab - Before and after you have been applied the patch, did you dump and solve these dump in one day ?

I mean if you get the the dump file on Novembre 9, 2009 (before apply the patch) then you should apply the patch and redump your actual dongle on Novembre 9, 2009 too.

After all, compare the reg and report to us here. :)

SHKDumper -> ! Error: ShkLib::ShkDevice::Open:: DeviceIoControl (). Code: 0x00000017
@ crab - On your previous post, you wondered that the dongle is SDHK in SSP mode.
Why you use SHK dumper ? :confused:

capebyrun post a picture -> SHK

USBDSearch.exe -> Rainbow/Sentinel dongle; SafeNet USB SuperPro/UltraPro

Identifier.exe -> Found USB Key Safenet Sentinel SuperPro/UltraPro
@ All
Could anyone please inform to us, what are the USBDSearch.exe and Identifier.exe outputs of sentinel SHK and SDHK dongle ? :confused:

[crab]

There is 3 days between Dumps...
Will test it the same day


Why you use SHK dumper ? :confused:

to prove it is not an SHK in SHK mode :rolleyes:

[SonofabiT]

@crab
After you update your s/w, Must you update your activation code/license file of your dongle ? :rolleyes:
If yes it must, then try to use it's new dongle activation code/licence file.

[crab]

@SonofabiT
Not sure to understand you
There is no specific file to apply on dongle
But the update patch is doing something cause the dump is different after sw update

[SonofabiT]

@SonofabiT
Not sure to understand you
There is no specific file to apply on dongle
I mean... except the dongle protection scheme, Does your software need a license file such as .lic, .dat etc ?
But the update patch is doing something cause the dump is different after sw update
We are waiting for your report when you finish dump your dongle in the same day (the same Windows system date).

[crab]

Multikey 18.2 defeat this SDHK :D
Total respect to Elite


Dump with SSUMD
Solve with Dum2mkey
Fill missing cell in the reg created by SSUMD (WP and Algo)



We are waiting for your report when you finish dump your dongle in the same day (the same Windows system date).
Confirmed, some cells are different between a software update
But emulation working fine with older dump
I'm still trying to understand :confused:

Thanks to capebyrun and SonofabiT for cooperation
Thanks to Master Git for analyze this key and sharing mk18.2

Best Regards

[kiki]

Multikey 18.2 defeat this SDHK :D
Total respect to Elite


Dump with SSUMD
Solve with Dum2mkey
Fill missing cell in the reg created by SSUMD (WP and Algo)



Confirmed, some cells are different between a software update
But emulation working fine with older dump
I'm still trying to understand :confused:

Thanks to capebyrun and SonofabiT for cooperation
Thanks to Master Git for analyze this key and sharing mk18.2

Best Regards

good news! thanks for your info.
so the step is to add dump with PVA dumper to use GIT's dump2mkey tool

[SonofabiT]

Also, sporaw's dumper and tch2000's f1___spor.exe is the good solution. ;)

[crab]

so the step is to add dump with PVA dumper to use GIT's dump2mkey tool
No need of PVA dumper
SSUMD create a sspro_0000XXXX.dmp file witch can be solved by dmp2mkey and f1_nodongle
This give missing algo cells

I have no standard algo so dmp2mkey can't calculate WP :mad:
I have brute force the WP on an older key (classic SSP) witch working with an older version of the soft...

Any hint on the way to find the WP in this case ?

BR

[capebyrun]

YEP.......... sonofabit ;)

[SonofabiT]

@capebyrun - Well done, i am glad to hear about it. Say "SPASIBA" to the following people : :)
1. Chingachguk & Denger2K who provide vusbbus source code.
2. tch2000(tch2k) who provide f1_xxxx solver series.
3. r-Elite & SP who released multikey's emulator and all people who have contribution on the multikey-emulator project.

Actualy, These people who helped you. :) .

You and Me only use their tools and take benefits from all topic archive that available in this forum and another forum.

No need of PVA dumper
...
Any hint on the way to find the WP in this case ?
...
@crab - PVA dumper is not only the one. ;) Then, Open your eyes to find another dumper and another solution by tch2000's solver (f1_xxx series ). :D

[Git]

> Open your eyes to find another dumper and another solution by tch2000's solver (f1_xxx series ).

Why ?. As I said before, these things do not work by magic, they work by indefatiguable logic. They either work or don't work. One persons dumper/solver doesn't work "a little bit better" than another persons.

If somebody cannot find a solution with modern tools and so gives up and uses old tools and then succeeds, what does this tell us, factually?

More to the point, if you think there is a demostratable repeatable problem with a specific tool, then surely the correct thing to do is to report the details of that problem on a forum where the author is active?. That way, things get fixed IF there is a problem.

Git

[SonofabiT]

Why ?
Honestly, i don't know exactly what kind of dongle is it. In my experience, the solution is come from the following tools :
1. r-Elite's sspro/ulpro dumper which give me cellx07 value.
2. dong4emu's dumper and tch2000's f1___spor.exe which give me cell0x04 and cell0x08-cell3F.
3. y8y8y8y's ssp2reg.exe which convert the reg.
4. Notepad which provide me to edit cell "CellType" 5 and 7 and change the registry patch for multikey emulator.
5. r-Elite's Multikey ver 0.18.2.0 which emulate this kind of dongle.

That all my experience. I don't know who to write a logic answer because my RE level is extremly bad. :(