Microdog dongle question
 

I am dealing with microdog, which is dongle of Rainbow corp.

But I think it's different from sentinel series.

The problem is it's hard to get the point of communication with dongle.

Is there any useful breakpoint or some trademark command?

thanx in advance.

(I researched this forum and there is one post about microdog, but I couldn't download the attacment)

you need download 3.x and 4.x SDK(sdk different),
unpack both SDK (manual at rce forum) and found all info in unpacked libraries.

native chinese program used microdog, but in many case this program with chinese language ;)

sorry but I don't understand the reason to download sdk.

Why do I need sdk if microdog has not a license manager ability?

The sdk is used to clean obfuscated code?

Could give me some detail info. ?

regards

SDK can't download freely.
Current release SDK is v4.0 build 15 as i known.
Code chipered, executable have obfuscation.

WBR

solved by dumping at oep and import reconstrucion with dongle.

actually the sdk was not useful for my case, coz I didn't know the correct dog key. ;)

thanxs to carver and FoxB.

I have use this kind of dog for a long time, it is made by a Chinese Company, so it is quite different from RB dog. You should use IDA to analysis the DOG API entry

i saw SDK on the FTP server (exetools)
/ftp/pub/programming components/hardware/MicroDog.SDK.v3.4.b0013 by FoxB/

SDK V4.0 Build 0015
http://cn.safenet-inc.com/download/dog/microdog/MicroDogV4.0build15.zip

4ALL: This is chipered SDK.

I have a quick question ;)

1. Is the SDK needed if I have a dongle? I cracked the target with dongle by unpacking and without SDK.

2. Is microdog could be cracked with only SDK? I installed SDK by using some patches. But I didn't find anything to crack the dongle since we don't know the correct dongle key(in manual, the key is generated by the software developer and unique). So I am a little confused how to take advantage of SDK.

@FoxB
:check ur PM plz

Microdog dongle crack see this struct

'typedef struct _MH_DLL_PARA
'{
' WORD Command;
' WORD Cascade;
' WORD DogAddr;
' WORD DogBytes;
' DWORD DogPassword;
' DWORD DogResult;
' DWORD NewPassword
' BYTE DogData[200];
'} MH_DLL_PARA;
'
' Command is command code
'DogCheck 1
'ReadDog 2
'WriteDog 3
'DogConvert 4
'GetCurrentNo 5
'EnableShare 6
'DisableShare 7
'SetDogCascade 8
'SetNewPassword 9

1. Microdog can use Cloning Chip for Copy.
2. using Crack.
1) find entry point for Microdog OBJ or DLL Lib.
2) can find para. and command . like Cracker xmt said.
3) look handbook for MH dog. so can understand command meaning.
4) Bomb it.

not, i think it is not fine to crack the program with the microdog's envelop.
but we may clone it. look, my frined, we can read all info as a file(a.cfg) by SDK, after the PWD of dongle is found out. and write the file(a.cfg) to a new dongle,lastly replace the old PWD with your new dongle's PWD in all files protected.
how 2 find out the PWD? ;) pls study it 4 some time, i think u can ...
after find out the PWD, go without saying, replacing is not a problem

I have this kind of microdog dongle, anyone guide me to dump this dongle and make emulator, Thank's in Advance.

[Port1] : MicroDog USB Device


Is Port User Connectable: yes
Is Port Debug Capable: no
Companion Port Number: 0
Companion Hub Symbolic Link Name:
Protocols Supported:
USB 1.1: yes
USB 2.0: yes
USB 3.0: no

Device Power State: PowerDeviceD0

---===>Device Information<===---
English product name: "UMI V3"

ConnectionStatus:
Current Config Value: 0x01 -> Device Bus Speed: Low
Device Address: 0x03
Open Pipes: 0
*!*ERROR: No open pipes!

===>Device Descriptor<===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0110
bDeviceClass: 0xFF -> This is a Vendor Specific Device
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 = (8) Bytes
idVendor: 0x08E2 = SafeNet China Ltd.
idProduct: 0x0002
bcdDevice: 0x0000
iManufacturer: 0x01
English (United States) "SafeNet Inc."
iProduct: 0x02
English (United States) "UMI V3"
iSerialNumber: 0x00
bNumConfigurations: 0x01

---===>Full Configuration Descriptor<===---

===>Configuration Descriptor<===
bLength: 0x09
bDescriptorType: 0x02
wTotalLength: 0x0012 -> Validated
bNumInterfaces: 0x01
bConfigurationValue: 0x01
iConfiguration: 0x00
bmAttributes: 0x80 -> Bus Powered
MaxPower: 0x32 = 100 mA

===>Interface Descriptor<===
bLength: 0x09
bDescriptorType: 0x04
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x00
bInterfaceClass: 0xFF -> Interface Class Unknown to USBView
bInterfaceSubClass: 0x00
bInterfaceProtocol: 0x00
iInterface: 0x00

your software use dll or api-linked method for acceess to the dongle?