SafeNet USB SuperPro/UltraPro

[engonaplane]

Noted. Thanks Git

[burhanuddinmna]

Thanks Git, i tooo wait for this, thank you

[kjms]

engonaplane use this reg unlimited days (65535) with all options (Expect module 6)

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\multikey\Dumps\AA2D0000]
"DongleType"=dword:00000003
"Copyright"="kjms"
"Created"="Wed Nov 23 17:45:59.657 2011"
"Name"="AA2D Sentinel SuperPro Dump"
"Type"=dword:00000000
"CellType"=hex:\ 
    01,01,03,03,03,03,03,03,\ 
    03,03,03,03,03,03,03,03,\ 
    03,03,03,03,03,03,03,03,\ 
    03,03,03,03,03,03,03,03,\ 
    03,03,03,03,03,03,03,03,\ 
    03,03,03,03,03,03,03,03,\ 
    00,00,00,00,01,01,00,00,\ 
    00,00,00,00,00,00,00,02
"sntMemory"=hex:\ 
    03,3B,2D,AA,00,00,00,00,00,00,00,00,A0,04,00,00,\ 
    47,7F,8C,F8,04,2F,65,DB,72,06,D1,F0,AF,34,C3,F8,\ 
    06,76,94,C7,2D,4C,FB,FC,49,6B,FE,C9,CB,B3,FD,C2,\ 
    AE,54,E5,F8,FF,06,44,D4,25,78,7B,D5,00,00,00,00,\ 
    00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 
    00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 
    00,00,00,00,00,00,00,00,00,0A,FF,FF,FF,FF,88,7B,\ 
    01,00,F1,FF,00,00,00,00,00,00,00,00,00,00,FF,FF

[engonaplane]

@kjms

hi. that reg did not work at all. License not found error.

[Git]

Which version of MultiKey are you using, still 18.0.3?. You may need :

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\multikey\Dumps\0000AA2D]

Git

[engonaplane]

yes MK 18.0.3.

Same problem even with the suggested change

 Error: Verify License Failed!
The product type is not correct.

I doubt that it is the cause as the kjms's header is same as the original reg i posted

By changing the last 12 cells of the original reg to follow kjms's reg, the validity period of the dongle looks change but it won't start due the last activated time.

To start it I changed cells 57 and 58 to match the current time and date - 2011-12-04 03:00:00 = 3993300

Lock ID: 3B03  
Latest Opening Time : 2011-12-04 03:00:00 
Current System Time : 2011-12-04 03:02:44  

Maintenance days: 65535  
Time authorization:  2011-05-05 - 2183-10-05.  Available within 62761 Days!

just another note, the dongle should already have modules 0 to 9 enabled. Not to concern with getting other functions, but to get the dongle working for more than 30mins.

currently testing whether the license dies after the time difference increases (the original issue)

[Git]

Did you notice what I said earlier, i.e I am not sure if that very early version of MultiKey willwrite to the registry and to the reg file. You should update. Another thing that comes to mind is the possibility of a checksum of hash in the data. If I was storing expiry dates in plain binary I would certainly protect it with CRC32, MD5, SHA1 etc. Sounds like it's time to disassemble the target.

Git

[engonaplane]

Hi Git can you suggest a multikey version for me to attempt?

@kjms

interesting screenshot as your Probe is not complaining altho the current system time is a lot different than the latest opening time.

I do however understand why your reg file did not work for me. The software I am trying to get working is Analyzer and not Probe

Can you share your multikey version?

My license just died again

 Error: Verify License Failed!
Verify license failed due to system time changing.
Please correct system later than the Latest Opening Time.

[Git]

Try version 19.whatever. it will write to the registry even if you don't know the WP.

What is special about 1st May 2004 ?

Git

[engonaplane]

that is something the 12 cells kjms changed did

my original date (from the original reg file) was

Maintenance days: 365  
Time authorization:  2011-03-20 - 2012-03-22.  Available within 108 Days!

-------------------

sorry misunderstood your statement.

In my software, if the system date has more than 15 minutes difference with latest opening date, the software will fail to start. Once started, once the difference is more than 15 mins, the software will self-close due to license verification fail.

In kjms' screenshot, the difference is already more than that but he does not seem to have that issue

---

for mk 19.X license, my dongle password should be 03,3B,2D,AA right?