• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Update on Windows Product Activation.

IdahoB

Senior member
I include below the full text from the article on The Register. Draw your own conclusions - I want to read the background article before I do.

"WinXP Product Activation decoded and analysed"
By John Lettice
Posted: 10/07/2001 at 12:36 GMT


German techies Fully Licensed GmbH claim - convincingly - to have unravelled the Windows Product Activation (WPA) system used in the latest versions of Microsoft software, including Office XP and Windows XP. The bottom line, according to the company, is that WPA is not particularly intrusive, does not invade anybody's privacy, and is a lot more forgiving of hardware changes than has been speculated.

That speculation is, as Fully Licensed points out, entirely Microsoft's fault, as the company has been intentionally vague about the precise nature of the sending and checking carried out. As Fully Licensed says: "The current public discussion of Windows Product Activation (WPA) is characterized by uncertainty and speculation. In this paper we supply the technical details of WPA - as implemented in Windows XP - that Microsoft should have published long ago."

Fully Licensed, incidentally, supports WPA. Says managing director and CTO Thomas Lopatic: "Software piracy is still a major problem for all software companies. And we think that [Microsoft's] interest in raising the bar for software pirates is absolutely justified."

The company analysed WPA as shipped in WinXP RC1, and found that ten hardware components are used to generate the "individual" hardware ID for the machine XP is installed on. "However, due to the method employed to generate the hardware ID, it is very likely that many hardware configurations result in the same ID. Consequently, determining the actual hardware configuration corresponding to a given hardware ID is an infeasible task. In addition to the hardware ID only information derived from the product key - a kind of serial number accompanying each distributed copy of Windows XP - is transmitted."

So Microsoft does not have any mechanism for finding out what hardware you're running. From the WPA process, anyway. The hardware checked is as follows: Serial number of system volume; NIC MAC address; CDROM; graphics adapter; CPU; hard drive; SCSI adapter; IDE controller; processor model; RAM size. There's also a check to see if the hardware is dockable or not. The company reckons that there's likely to be duplication in the components (i.e. different products might produce the same ID), and that the system is pretty forgiving.

You're only likely to have to repeat the activation process and get a new unlock key if you change more than three of these components, and if you're using a portable in conjunction with a docking station, it's effectively a lot more flexible than that.

The information transmitted, the company says, is "completely innocuous", consisting solely of the hardware ID (which can't be used to identify specific hardware) and the product key that comes with XP. Of itself the system is therefore no threat. WPA does however take us closer to Microsoft's goal of chaining a particular piece of software to a particular piece of hardware, making it easier for the company to claim the Microsoft tax every time you buy a new machine. Fully Licensed doesn't cover that part of the deal, but obviously if you install, say, Office XP on one machine then you want to use it on an entirely new machine when you upgrade, you're going to have to call up Microsoft and get permission. The Register reckons it's therefore still objectionable from that point of view.

Nor does Fully Licensed cover other aspects of 'generation XP' that have the effect of garnering information about you and your hardware. There is, for example, a deal of checking of the local configuration already present in Windows Update, and the automated bug-reporting in XP potentially gives Microsoft far more information than you'd conceive of being sent via WPA. This latter system kicks in when your machine has a problem, but only sometimes, frequently not when you had a big problem you're personally well aware of, rather more frequently when you didn't even notice a problem at all.

The intention of this system is positive - Microsoft reckons that if people can send fully detailed bug reports just by clicking OK, it'll be able analyse them in volume, to zero in on major problems with its software a lot faster than in the past, and be far more effective in prioritising fixes. But although you get the option of not sending this and of inspecting what's going to be sent, it's practically impossible to understand what's being sent - quite a bit of information about local configuration, however, will certainly be in it, so it's likely a lot of people will click on no.

But Fully Licensed set out solely to analyse the WPA process, and it seems to have done a fairly thorough job of this. In addition to the analysis of the hardware identifier, it's also done a deconstruct of the product key itself, explaining how the important part is buried inside the printed product key, and which components are likely to be checks (to allow for the call centre operative typing it in wrong, for example). It's not clear whether or not this information will be of any help to people who might have a need to generate product keys (no, we don't know why they'd want to do that either). But Fully Licensed probably would not have published the info if this was the case.

In addition to the results of its analysis, the company has also made XPDec, a command line utility that can be used to verify the information, available for download along with the source code for XPDec. It notes that "we have removed an important cryptographic key from the XPDec source [so] recompiling the source code will fail to produce a working executable."


Fully Licensed's Inside Windows Product Activation Paper
 
I have a problem with this part of the article:


<< However, due to the method employed to generate the hardware ID, it is very likely that many hardware configurations result in the same ID. >>


But yet when you read the white paper it states&quot;


<< If msoobe.exe is invoked more than once, it provides a different Installation ID each time. >>


Other than that it seems to verify what has been said about activation all along. How can they state it's &quot;very likely&quot; to result in the same ID and then when the activation program itself is run over and over get a different ID???
 
Yeah, I stumbled accross the licenturion.com site last night and linked to it in the big WPA thread, but nobody seemed to have any comments on it there either, they are all having too much fun over there wildly speculating.
 
Hmm... good point Psycho - I've had a bit of a think about this, and I think I've sussed it.

The hardware ID is NOT specifically linked to any one set of hardware - as we've said all along, it's fairly random. The same ID could refer to several different configs.

Therefore it's not so much that the hardware ID is specifically linked to any specific config, rather it is a personal installation code, as such. Only on changing hardware will you need to register a new code.

This would both ensure you have to activate again after a major hardware change, and also protect your personal config.

I realise this doesn't read well, but I think you'll get the idea.
 
I noticed it mobly99, I also noticed no one from the &quot;opposition&quot; addressed it. It's funny how that works.

I agree IdahoB that was pretty much my take on it.
 


<< I have a problem with this part of the article:


<< However, due to the method employed to generate the hardware ID, it is very likely that many hardware configurations result in the same ID. >>


But yet when you read the white paper it states&quot;


<< If msoobe.exe is invoked more than once, it provides a different Installation ID each time. >>


Other than that it seems to verify what has been said about activation all along. How can they state it's &quot;very likely&quot; to result in the same ID and then when the activation program itself is run over and over get a different ID???
>>



I didn't read everything in detail yet, but is it possible that the &quot;Installation ID&quot; and the &quot;hardware ID&quot; possibly different things entirely?
 
I think it's bascially checking as to whether or not you have installed that one licensed copy on multiple computers in your home. By using the MAC address of your NIC, it is systematically checking for this arrangement based on the fact that you cannot typically have two NICS with the same MAC address in the same network.
 


<<
Other than that it seems to verify what has been said about activation all along. How can they state it's &quot;very likely&quot; to result in the same ID and then when the activation program itself is run over and over get a different ID???
>>



This is entirely possible. Talking hypothetically for a moment, if I were to generate a random number on one machine, and run it again and again I would generally get a different number each time. If the number is limited in scope, then it is also limited in permutations. Now say I have two machines generating random numbers. The likelyhood that I will generate identical numbers has just increased. Now randomly generate numbers on 1 million computers.

In addition, the method used to generate the &quot;random&quot; number can determine how random it really is. It is common in programming to generate a random number off the computer clock; however, it is also common knowledge that certain repeating patterns can occur when you do this.

Back to the WPA, it's obviously more complicated than a simple random number generated off the system clock, but nevertheless it is still appears possible that it could generate the same number more than once.

I'm not a mathemetician, nor an encryption specialist, but the above is just common logic applied while skimming the Fully Licensed article.



I am not in any way paranoid about my privacy being invaded by the WPA, but it is important to note that the Fully Licensed article only pertains to the generated code number for a phone activation. It is entirely possible that an internet-based activation could send data in addition to the generated code. I don't think it will, but it is technically possible.

Also, I would like to say that even though I do not fear the WPA on privacy, I DO object to it. I object to it because it restricts the legal uses of the software. According to the EULA, it is perfectly legal for me to install the software on a second machine, so long as I completely remove it from the first machine. But the WPA will not let me do this without contacting MS, in effect restricting my legal use of the software. When calling MS to re-activate the OS for the new hardware it is entirely possible that MS will accuse me of pirating and not allow me to use my legally purchased (licensed) copy of the OS. This HAS happened with current products, and it WILL happen with XP.

The WPA WILL also create a chilling effect on homebuilders and hardware upgraders. I had to reinstall Windows eight times in the process of building my new system over the course of two months. The WPA will make this nearly impossible, and will likely get me designated as a software pirate, EVEN THOUGH I WAS USING A LEGAL LICENSE ON A SINGLE COMPUTER!.
 
It's a weak anti-piracing system anyway. I bet more than 50% of anyone who uses XP will have a cracked copy just to save them the trouble of getting a new ID after nearly every upgrade or modification.
 
I have Office XP that I got from work. I guess the bossman bought a multiple liscensing agreement because I had zero problems activating the product. I hope that it doesn't give me problems in the future though if I ever change the hardware.

It doesn't ask for much information. About all that they could get from me was my IP address which changes anyway because I'm on a DHCP server. I just don't understand how they would be able to keep track of the information. It seems to me that it would be in the product itself and not anything that's stored on MS database.

If I ever do have any problems with it, I will just uninstall it and use my copy of Office 2000 instead. There really is not much of a difference other than UI. It's about like the difference between Win98 and WinME IMO: Nothing that matters.

Sal
 
Now I am not sure if this is true, but you can already defeat the WPA. This is word that I got from a friend who is in hong kong. Now if they are telling the truth, I do not know...but according to him they have figured out a way around the WPA.

Now about microsoft being good about this whole Privacy thing, I don't trust Microsoft. I don't trust Bill, Microsoft, or anything about them. Bill didn't get to be worth 60 billion by letting things slide. He would do everything possible to keep his money coming in.
 
Kgraeme,

&quot;The WPA WILL also create a chilling effect on homebuilders and hardware upgraders. I had to reinstall Windows eight times in the process of building my new system over the course of two months. The WPA will make this nearly impossible, and will likely get me designated as a software pirate, EVEN THOUGH I WAS USING A LEGAL LICENSE ON A SINGLE COMPUTER!&quot;

The stored code generated by your hardware will be retained on your disk unless you're talking about a clean format install, and surely you didn't need to clean install 8 times in two months. That kind of formatting shouldn't be required for XP - but I can understand your concern.
 
Yes, I did need to do eight clean installs. It was a very problematic project. It would very probably have happened with XP as well. It had to do with a mish-mash of registry errors, bad drives, bad ram, etc... The cause was hardware, the victim was Windows. And with WPA, it would have been impossible for me to solve. Heck, I actually had to clean install 4 of the times in two days.

 
&quot;The WPA WILL also create a chilling effect on homebuilders&quot;
---

I don't see how this could affect the construction industry. >)
 
ACCORDING to that whitepaper...

HERE IS WHAT MICRSOFT IS TRACKING ABOUT YOU: (ahem...at least for today that is).

quote:
--------------------------------------------------------------------------------
For this purpose, the double words are divided into twelve bit-fields. The relationship between the computer hardware and the bit-fields is given in the following table.
double word | offset | length | bit-field value based on
H1 | 0 | 10 | volume serial number string of system volume
H1 | 10 | 10 | network adapter MAC address string
H1 | 20 | 7 | CD-ROM drive hardware identification string
H1 | 27 | 5 | graphics adapter hardware identification string
H2 | 0 | 3 | unused, set to 001
H2 | 3 | 6 | CPU serial number string
H2 | 9 | 7 | harddrive hardware identification string
H2 | 16 | 5 | SCSI host adapter hardware identification string
H2 | 21 | 4 | IDE controller hardware identification string
H2 | 25 | 3 | processor model string
H2 | 28 | 3 | RAM size
H2 | 31 | 1 | 1 = dockable 0 = not dockable
--------------------------------------------------------------------------------
Still seems kinda scary to me....they will probably be able to track alot of stuff with this, like say....tracking what web purchases you make, or using it as that secret identifier in Office documents etc..


Also, I thought I would see what Microsoft has to say about this stuff and here is what I found:

FROM THE BOTTOM OF THIS FAQ ON MICROSOFTS WEB SITE:
http://www.microsoft.com/piracy/basics/activation/mpafaq.asp



<< Won?t Product Activation be easy to crack? I?ve heard on the Internet that it will be cracked before the product is released. I also heard you can buy Office XP final product on the street in Asia. Doesn?t this mean the code has been cracked? >>





<< Product Activation has yet to be cracked. The so-called &quot;crack&quot; now being passed around the Internet contains a set of instructions for setting a registry key that disables activation. Microsoft made the existence of this registry key public to its technical beta testers in early February and included it as a testing tool, telling them where it was and how to set it to disable activation. That said, the intellectual property protection arena is a cat-and-mouse game. All IP protection technologies will be cracked at some point; it is just a matter of time. The measure of success is not completely stopping software piracy. Success is more likely measured in increased awareness of the terms of the license agreement and increased license compliance. >>

 


<< But although you get the option of not sending this and of inspecting what's going to be sent, it's practically impossible to understand what's being sent - quite a bit of information about local configuration, however, will certainly be in it, so it's likely a lot of people will click on no.
>>



I think Microsoft should make this information public so people know exactly what's being sent. I don't think it would compromise their activation security, so why not?
 
Back
Top