Dead Silence

Anachostic · 03-12-2008, 11:28 AM

Is there anyone out there that can help me tackle the Zune API?

All the objects seem to be there but I can't get them to populate.

ZuneDbAPI.DeviceList - Always empty. If I can get theis to populate, the rest is a piece of cake.

It leads to objects like ZuneDbAPI.Device and the StartSync/StopSync/ReverseSync methods. Some other related objects like ZuneDbAPI.InteropNotifications and ZuneUI.SyncControls had promise, but never seem to do anything.

The InteropNotifications seems to be similar to the code that's used by the MS sync test application, but it doesn't seem to gather the same information.

Get Reflector and see for yourself by disassembling the ZuneShell and ZuneDbAPI DLLs.

berdon · 03-14-2008, 09:04 PM

I hit that point and got stuck at the same wall. There's a whole lot of methods available to us but we can't use them without the device. :/

Anachostic · 03-15-2008, 04:25 AM

I was thinking yesterday that there is probably a check in the Zune USB driver (ZuneUSBTransport.dll or ZuneMTPZ.dll or ZuneUSBConnection.dll) to see if the application registering for the DeviceAdded event has a Microsoft Digital signature. If it doesn't, it supresses the notification. That means the events never get fired and the DeviceList object never gets populated.

Does anyone know anyone in the cracking community? These people know how to patch binaries to NOP out certain checks. I'm pretty sure they would be able to figure out how to patch the DLL to not check for the digital signature. Then the events would be raised and we'd have a device list to work with.

If no one knows any crackers directly, does anyone know where they hang out?

berdon · 08-12-2008, 07:11 PM

No, I think the zune.exe program is doing more behind the scenes then we are by simply referencing the appropriate .dll's and instantiating things, such as the zune app itself. I say think because the zune libraries handle a number of parameters that are passed in; however, it doesn't handle the /device parameter which is what gets sent to zune.exe from zunelauncher.exe.

I don't think it has anything to do with signatures, I think it has to do with registering with the Zune service provider. My best guess, of which I haven't had time to try, is to create my own service provider for the device and then continuously swap service providers while stepping through each thing that happens to begin crafting it to mimic the actual service provider. At that point, I should be able to instantiate the zune software through the appropriate libraries; however, use my service provider which would then send me the notifications of the device as opposed to the real one.

Reaper0294 · 09-26-2008, 07:02 PM

Quote:

Originally Posted by Anachostic

I was thinking yesterday that there is probably a check in the Zune USB driver (ZuneUSBTransport.dll or ZuneMTPZ.dll or ZuneUSBConnection.dll) to see if the application registering for the DeviceAdded event has a Microsoft Digital signature. If it doesn't, it supresses the notification. That means the events never get fired and the DeviceList object never gets populated.

Does anyone know anyone in the cracking community? These people know how to patch binaries to NOP out certain checks. I'm pretty sure they would be able to figure out how to patch the DLL to not check for the digital signature. Then the events would be raised and we'd have a device list to work with.

If no one knows any crackers directly, does anyone know where they hang out?

I know many in the hacking/cracking community.

Do i recommend meeting 90% of them? Absolutely not. I'll do some checking around to see if any1 would want to help with this project however.

random667 · 10-14-2008, 12:09 PM

I just got the newest .net reflector and tried it on the 3.0 Zune.exe and other zune dlls and exes and I get this error:
"Module 'C:\Program Files\Zune\Zune.exe' does not contain a CLI header."

Has Microsoft obfuscated the new version so it cant be read by .net reflector?

03-12-2008, 11:28 AM	#1 (permalink)
Anachostic Jr. Member Join Date: Jun 2007 Posts: 407 Reputation: 77	Dead Silence Is there anyone out there that can help me tackle the Zune API? All the objects seem to be there but I can't get them to populate. ZuneDbAPI.DeviceList - Always empty. If I can get theis to populate, the rest is a piece of cake. It leads to objects like ZuneDbAPI.Device and the StartSync/StopSync/ReverseSync methods. Some other related objects like ZuneDbAPI.InteropNotifications and ZuneUI.SyncControls had promise, but never seem to do anything. The InteropNotifications seems to be similar to the code that's used by the MS sync test application, but it doesn't seem to gather the same information. Get Reflector and see for yourself by disassembling the ZuneShell and ZuneDbAPI DLLs.

03-14-2008, 09:04 PM	#2 (permalink)
berdon zB Programmer Jr. Member Join Date: Nov 2006 Posts: 311 Reputation: 50	I hit that point and got stuck at the same wall. There's a whole lot of methods available to us but we can't use them without the device. :/ __________________ To view links or images in signatures your post count must be 0 or greater. You currently have 0 posts.

08-12-2008, 07:11 PM	#4 (permalink)
berdon zB Programmer Jr. Member Join Date: Nov 2006 Posts: 311 Reputation: 50	No, I think the zune.exe program is doing more behind the scenes then we are by simply referencing the appropriate .dll's and instantiating things, such as the zune app itself. I say think because the zune libraries handle a number of parameters that are passed in; however, it doesn't handle the /device parameter which is what gets sent to zune.exe from zunelauncher.exe. I don't think it has anything to do with signatures, I think it has to do with registering with the Zune service provider. My best guess, of which I haven't had time to try, is to create my own service provider for the device and then continuously swap service providers while stepping through each thing that happens to begin crafting it to mimic the actual service provider. At that point, I should be able to instantiate the zune software through the appropriate libraries; however, use my service provider which would then send me the notifications of the device as opposed to the real one. __________________ To view links or images in signatures your post count must be 0 or greater. You currently have 0 posts.

03-15-2008, 04:25 AM	#3 (permalink)
Anachostic Jr. Member Join Date: Jun 2007 Posts: 407 Reputation: 77	I was thinking yesterday that there is probably a check in the Zune USB driver (ZuneUSBTransport.dll or ZuneMTPZ.dll or ZuneUSBConnection.dll) to see if the application registering for the DeviceAdded event has a Microsoft Digital signature. If it doesn't, it supresses the notification. That means the events never get fired and the DeviceList object never gets populated. Does anyone know anyone in the cracking community? These people know how to patch binaries to NOP out certain checks. I'm pretty sure they would be able to figure out how to patch the DLL to not check for the digital signature. Then the events would be raised and we'd have a device list to work with. If no one knows any crackers directly, does anyone know where they hang out?

10-14-2008, 12:09 PM	#6 (permalink)
random667 Experienced Zuner Join Date: Feb 2008 Posts: 102 Reputation: 32	I just got the newest .net reflector and tried it on the 3.0 Zune.exe and other zune dlls and exes and I get this error: "Module 'C:\Program Files\Zune\Zune.exe' does not contain a CLI header." Has Microsoft obfuscated the new version so it cant be read by .net reflector?

Advertisement