HASP HL Time
 

recently i get a program fully emulated with multikey version 0.18.0.2, i tested and it works well, but after 45 days the program says "Security device is timed out", the partial solution is change the date and it works again. but i think i could change something in the registry to set the date 2 years ahead.

My question is where and in what format i must put the date???

This is the begining of the file:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\MultiKey\Dumps\608D2C50]
"Name"="Deco Studio"
"Copyright"="2008"
"SN"=dword:4f93c6d7
"DongleType"=dword:00000001
"Type"=dword:000000fa <== Is there a manual to know this values??
"Memory"=dword:00000020
"NetMemory"=hex:00,00,00,00,00,00,00,00,00,00,fd,ff
"HaspTimeMemory"=hex: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,d7,c6,93,4f,00,00,00,00,ff,ff,ff,ff,\
ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff <=== I suppossed here is the date
"TimeShift"=hex:00,00,00,00,00,00,00,00
"SecTable"=hex:6c,ae,93,93,a2,a2,93,93
"ColumnMask"=dword:000000eb
"CryptInitVect"=dword:0000001c
"AesKey"=hex:01,02,03,04,05,06,07,08,09,0a,0b,0c,0d,0e,0f,10

My friend if u like I can make a look at ur program if u like ...
just upload it and PM me ...
I will try to make it work .

HASP3 Time : 0x12
HASP4 M1 : 0x0A
HASP4 Time : 0x1A
HASP HL : 0xEA
HASP HL Time : 0xDA

Also, look at last but one byte of NetMemory[]
0xFF : local
0xFE : Net
0xFD : Time

Your HaspTimeMemory structure values make no sense. The current time and current date fields are all zeros and the ID field is the same as your serial number. If you want to experiment, the first 3 bytes are the time in BCD secs, mins, hours, and the next 4 bytes are the date in BCD date, month, dow, year. As you guessed, expiry dates are more often stored in the last 16 bytes.

TimeShift is a 64bit integer and is the difference between current time and the actual time written to HaspTimeMemory in the units of 100nS and may be worth experimentation.

Git

Thanks, i will experiment!!

Can i use the tool timeset for any hasp4 emulator by sataron 2006, to change this values??? because i dont understand very well the Binary Coded Decimal conversion.

another thing, the type FA is for HASP HL Time or should be HASP SRM???

My friend : I have finish it-but I have to decide which way I will use .
I think I will make unpack for it ....or I will make a loader for it and I will send it to u .
the check for the Time came form the main program ( I mean by the programmer -he who make the check for time not by the code dongle it self ) .

note : there are 11 file packed ..at least

Ans all 11 (or 1111) files will unpack fine when the emulator file is correct. Easiest way to unpack HL shell is to let the emulator do it. Once you unpack it there's a very good chance the dongle is still used anyway, so why reinvent the wheel?

Git

hehehe no :D...I will just unpack the main file (.exe) which contain the check not else :p . then patch it
and I say I can make a loader for it and finish every thing ...
but i like to make it finished

Better would be to tell us the format that the expiry is stored in in the HaspTimeMemory struct. Or, if you have just bypassed it, send me unpacked main exe (not patched) and IDA file and I will carry on work.

Git

hehe as u wish my friend ...I will

@backdoor_b

I had another program with the same problem.
Only thing I needed to be changed was inside the

"HaspTimeMemory"=hex: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,d7,c6,93,4f,00,00,00,00,ff,ff,ff,ff,\
ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

replace d7,c6,93,4f with 01,02,03,04 and if the rest of the dump is correct already work. Otherwise there could be a byte check inside the datablock which needs to be removed.

@ahmadmansoor: hope u could make a tutor of how to unpack it. =)

@DCA i will try it !!

You don't need a tut, it unpacks itself!. Just get that emulator working and you can forget all about ugly patches and unpacking.

Git

@Git

Unpacking makes your application run quicker.
Then use emulator.

Depending on hasp protection most simple patch consist of only two patches. No emul needed anymore forever :)

Until the first service pack or update...

Git