Jump to content


Reverse-Engineering Microsoft/Windows Update


4 replies to this topic

#1 TheArkive

    Member

  • Members
  • PipPip
  • 14 posts
  • Gender:Male
  • Location:The Construct

Posted 01 May 2012 - 01:02 AM

I've been messing around with WireShark (packet capturing software), and mIRC socket scripting to gain a better perspective on how Windows Update works. I know that is what you guys have basically already done, but I'm wondering if I have stumbled onto something that might help.

I've managed to isolate one of the transactions between one of my PC's and MS's update sites. The file I uploaded is a record of the traffic when I opened Windows Update in Win7 x64 and clicked "Check for Updates".

I have found the point at which the SSL certificate is transferred, and the point at which the application data is transferred (encrypted of course). I think I can capture the binary data with mIRC socket scripting, as well as the certificate. Is there any way to run the SSL cert and the binary data through some kind of program to decode the contents of the binary data? I figure that binary data is an actual full list of updates straight from MS's servers.

With mIRC I can also do SSL connections. I haven't tested it yet, to see if I can actually get a list of updates for my instance of Win7 x64 (and decode it) but that is next on my list.

I noticed that clicking update once started about 4 different connections to MS servers. I figure that this can also include a full list of updates for MS Office as well, including the Help files that show up on windows update, but not on AutoPatcher (as of the last time I checked that is).

Would any of this be useful to you guys? Or am I re-inventing what you guys have already done?

I don't know C++. I'm not a programmer, but I am a scripter. I've done some VB (very limited). I've also done lots of batch scripting for windows. My most familiar language is mIRC scripting. I've used it to do a lot of data scraping scripts, as well as intercepting web traffic and doing my own custom processing of the intercepted traffic. Hopefully this will be of some use to you guys.

Attached Files



#2 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,159 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 01 May 2012 - 01:35 AM

Deciphering the SSL is illegal as far as I know. Its breaking an encryption that is not meant for us to view. The current way we generate a list is by reading the new MS bulletins released each first Tuesday. Each bulletin tells us what updates to add. Someone is currently generating a new Windows XP x64 script using a list of updates from another site.

#3 TheArkive

    Member

  • Members
  • PipPip
  • 14 posts
  • Gender:Male
  • Location:The Construct

Posted 01 May 2012 - 10:20 AM

Woah... thanks for the info. I was unaware of that. Too bad.

EDIT: For what it's worth, I wasn't actually trying to "break" SSL. Just trying to replicate the traffic using elements that already exist so that I can have another method of obtaining a backup copy of all the necessary updates. Or at least a complete list of the backups. Not just for windows, but for Office as well.

Is Microsoft really against that??

Edited by TheArkive, 01 May 2012 - 10:24 AM.


#4 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,159 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 01 May 2012 - 11:58 AM

Will im not sure. What I am sure of is that Microsoft has already threatened this site in the past with legal force due to storing there updates on this server. They didn't like that one bit. So im sure we are not forgotten. One misstep may prove fatal. We must make all efforts to stay well within the legal lines.

#5 TheArkive

    Member

  • Members
  • PipPip
  • 14 posts
  • Gender:Male
  • Location:The Construct

Posted 01 May 2012 - 09:16 PM

Understood. Thanks for your patience.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users