Wednesday, January 28, 2009
The road ahead
I started reading the book "The Road Ahead" written by the master mind of Microsoft Bill.H.Gates. I wanted to read this since a long time
Thursday, January 8, 2009
Is 'Genuine Windows Validation' a Good Thing?
Windows Illegal Ediion Microsoft is planning what could end up being quite a shock for the Windows XP warez world, and what currently looks to be one of the most amazing moves made by Microsoft since Windows Product Activation was introduced.
Recently, Microsoft completely rewrote the algorithm for the way Windows XP Corporate keys are generated, and has rewritten the code for Windows XP to recognize this new algorithm. This new code was an added 'feature' of Service Pack 2 released last year.
At the present moment, everyone who upgraded to Windows XP SP2 from Windows XP with no SP1 installation, will not have any problems or errors about an invalid CD-Key on a corporate version of Windows XP. This is because the new algorithm feature has been switched off in SP2 upgrades. To get to see this new feature, you would have had to slipstream+ SP2 into the Windows XP installation media and setup Windows. Once you've reached the CD-key, no current Corporate Windows XP key (none of the 75 that were tried) will work, as they are all invalid. Even if a corporate key is managed to be found, the chances of it working after the SP2 has been installed are slim to none, as Microsoft is rumored to 'still be working on the algorithm for SP2 for Corporate customers'. When Microsoft 'decides' to 'turn the feature on', computers with non-valid keys will be out of luck.
So why is Microsoft keeping this a secret? To put it mildly, they are a bit perturbed that warezers have been able to exploit the corporate edition of Windows XP to completely bypass WPA. They were planning all along to keep it a complete surprise until SP2 final had been released and shut down as many warez users from using Windows XP as possible. They know if it's made widely known what they are planning, nobody would have upgraded to SP2 until an appropriate patch has been made.
And as far as patches go, as far as I can guess right now the only patch that is going to work will be the ever popular "Reset" patch. And you still will not be able to download the security fixes. If you slipstream a corporate version of Windows XP as you're supposed to do, it will upgrade the algorithm. Note that the slipstream patches the DLL files which generate the CD keys, it doesn't replace them. This is why you cannot slipstream a non corporate version of Windows XP and drop the corporate files in and expect the installation to work properly. Windows also checks for the DLL files version numbers and if they don't match, errors will be created during install. It could be possible to find these DLL's, replace the version numbers with those of SP2, and put them back into the installation media, but you'd also have to find a way to replicate the Microsoft signature on the DLL's as well as the CAB files for setup to actually copy the files to the hard drive.
The first thing that comes to mind when thinking about this is that the current Corporate users of Windows XP are going to have to get a new CD-key reissued for their versions of Windows with SP2. Microsoft has decided that the cost of current corporate customers having to get a new CD-key is less that what they are losing in the market of Windows XP being distributed as a corporate installation amongst warez users. Microsoft is also planning to warn those with corporate editions of Windows XP to not let the CD-keys slip into the mainstream. The EULA is going to be rewritten to fit a new type of 'Corporate release' and it's been rumored that if a customers key is to get into the market, Microsoft may take legal action against those consumers.
Another rumor that is running rounds at Redmond is that Microsoft may actually included a type of 'Phone home' feature in the corporate versions of Windows XP SP2 only. This feature would connect to a Microsoft server upon connection and deliver the IP address of the connected computer and what the Installation ID is. Before privacy advocates begin screaming, realize that if Microsoft was to want to do this, they could very easily make provisions in the EULA that they (Microsoft) have included a feature that makes sure the Corporate edition of Windows XP is not installed on more computers than it's contract is made out for, and the computers IP address and the Installation ID may be transmitted to a local Microsoft server thought 128-bit encryption. No more information would be transmitted to the servers, and for more information, see the Microsoft Privacy Statement. It's a possibility, as corporate versions of Windows aren't exactly tailored for use by home and everyday users, so the EULA could very well be expanded to include such a feature.
+For those of you unfamiliar with the slipstream technique, a slipstream installation contains the original release of the OS (i.e., Windows XP, Win2K) updated with the current service pack, plus any hotfixes you deem necessary for your site. A slipstream installation saves time when you're deploying many new workstations, and you want the system image to be fixed in time and consistent across the enterprise. If your images are well defined, you might want to distribute a new image every quarter instead of distributing 20 to 30 hotfixes per month to affected systems.
So.. get out there and spend the $300 for a legal copy... before it's too late and you are left with a large paperweight, suitable for re-formatting.
Recently, Microsoft completely rewrote the algorithm for the way Windows XP Corporate keys are generated, and has rewritten the code for Windows XP to recognize this new algorithm. This new code was an added 'feature' of Service Pack 2 released last year.
At the present moment, everyone who upgraded to Windows XP SP2 from Windows XP with no SP1 installation, will not have any problems or errors about an invalid CD-Key on a corporate version of Windows XP. This is because the new algorithm feature has been switched off in SP2 upgrades. To get to see this new feature, you would have had to slipstream+ SP2 into the Windows XP installation media and setup Windows. Once you've reached the CD-key, no current Corporate Windows XP key (none of the 75 that were tried) will work, as they are all invalid. Even if a corporate key is managed to be found, the chances of it working after the SP2 has been installed are slim to none, as Microsoft is rumored to 'still be working on the algorithm for SP2 for Corporate customers'. When Microsoft 'decides' to 'turn the feature on', computers with non-valid keys will be out of luck.
So why is Microsoft keeping this a secret? To put it mildly, they are a bit perturbed that warezers have been able to exploit the corporate edition of Windows XP to completely bypass WPA. They were planning all along to keep it a complete surprise until SP2 final had been released and shut down as many warez users from using Windows XP as possible. They know if it's made widely known what they are planning, nobody would have upgraded to SP2 until an appropriate patch has been made.
And as far as patches go, as far as I can guess right now the only patch that is going to work will be the ever popular "Reset" patch. And you still will not be able to download the security fixes. If you slipstream a corporate version of Windows XP as you're supposed to do, it will upgrade the algorithm. Note that the slipstream patches the DLL files which generate the CD keys, it doesn't replace them. This is why you cannot slipstream a non corporate version of Windows XP and drop the corporate files in and expect the installation to work properly. Windows also checks for the DLL files version numbers and if they don't match, errors will be created during install. It could be possible to find these DLL's, replace the version numbers with those of SP2, and put them back into the installation media, but you'd also have to find a way to replicate the Microsoft signature on the DLL's as well as the CAB files for setup to actually copy the files to the hard drive.
The first thing that comes to mind when thinking about this is that the current Corporate users of Windows XP are going to have to get a new CD-key reissued for their versions of Windows with SP2. Microsoft has decided that the cost of current corporate customers having to get a new CD-key is less that what they are losing in the market of Windows XP being distributed as a corporate installation amongst warez users. Microsoft is also planning to warn those with corporate editions of Windows XP to not let the CD-keys slip into the mainstream. The EULA is going to be rewritten to fit a new type of 'Corporate release' and it's been rumored that if a customers key is to get into the market, Microsoft may take legal action against those consumers.
Another rumor that is running rounds at Redmond is that Microsoft may actually included a type of 'Phone home' feature in the corporate versions of Windows XP SP2 only. This feature would connect to a Microsoft server upon connection and deliver the IP address of the connected computer and what the Installation ID is. Before privacy advocates begin screaming, realize that if Microsoft was to want to do this, they could very easily make provisions in the EULA that they (Microsoft) have included a feature that makes sure the Corporate edition of Windows XP is not installed on more computers than it's contract is made out for, and the computers IP address and the Installation ID may be transmitted to a local Microsoft server thought 128-bit encryption. No more information would be transmitted to the servers, and for more information, see the Microsoft Privacy Statement. It's a possibility, as corporate versions of Windows aren't exactly tailored for use by home and everyday users, so the EULA could very well be expanded to include such a feature.
+For those of you unfamiliar with the slipstream technique, a slipstream installation contains the original release of the OS (i.e., Windows XP, Win2K) updated with the current service pack, plus any hotfixes you deem necessary for your site. A slipstream installation saves time when you're deploying many new workstations, and you want the system image to be fixed in time and consistent across the enterprise. If your images are well defined, you might want to distribute a new image every quarter instead of distributing 20 to 30 hotfixes per month to affected systems.
So.. get out there and spend the $300 for a legal copy... before it's too late and you are left with a large paperweight, suitable for re-formatting.
Saturday, January 3, 2009
I seldom chose what tv channel is on and most of my time wasting blogging and web surfing is stealing time from my employer, not my family.
Although I've been fiscally irresponsible in the past, my main financial vice lately has been lunch and coffee out every day at work.
I try to share my thoughts, dreams, aspirations, and feelings with Kate. I knowPoor thing ;-)
Little Johnny was filling in a hole in his back garden when his neighbour spotted him.
"What are you doing Johnny?" she asked,
"Burying my Goldfish, it died today" he replied,
"Oh dear, sorry to hear that but isn't that an awfully big hole for a Goldfish?" she laughed,
"Well it is inside your fucking cat!"
Although I've been fiscally irresponsible in the past, my main financial vice lately has been lunch and coffee out every day at work.
I try to share my thoughts, dreams, aspirations, and feelings with Kate. I knowPoor thing ;-)
Little Johnny was filling in a hole in his back garden when his neighbour spotted him.
"What are you doing Johnny?" she asked,
"Burying my Goldfish, it died today" he replied,
"Oh dear, sorry to hear that but isn't that an awfully big hole for a Goldfish?" she laughed,
"Well it is inside your fucking cat!"
Subscribe to:
Posts (Atom)