So far I have pulled some logs (with USBTrace / USBPcap+Wireshark / Procmon (hooked on the lic.checking file for logging requests))

Sadly, I lack some skills in this particular area. But I'm not ready to give up just yet. Maybe with some help...

I was however a bit surprised when checking the logs, since I was expecting a bit more data than I was getting.

I then checked the "iLok compartment" on the DS9490B - and it was empty.

Can someone tell me how the protection is achieved with just the 1-wire device, and no iLok in the dongle? Could it be that it simply just checks whether the dongle is present or not?

Any ideas as where to go from here?

Thanks,
--C

Woodmann

May 1st, 2013, 21:31

I bet my dollars on the Ilok is broken.
They are/were total pieces of shit.

Woodmann

cosse

May 5th, 2013, 06:44

Not sure I'm following you there, sir.

My dongle works just fine, and there is no need for an iLok-device.

After a bit more research, I'm now pretty sure that what the SW does, is that it request a piece of data from the DS2490.
That data is seen in the license software utility as "USB ROM DATA". This is always the same, and is found in wireshark under "URB_BULK IN" as "LEFTOVER CAPTURE DATA".

My issue now, is how to alter the current driver to skip the usb-request, and just have it report the "leftover capture data" to the software...

Anyone that can help a "newbie" in this area with some guidance as what to read up on? I am looking into doing this myself, but would need some help to get started..

And yes, I am consulting my friend google as well

Thanks

Edit: The "string" is actually the "64-bit unique serial number" of the USB-Dongle, as seen in the "OneWireViewer