See this article.. evidently some smart cracker out there got the info M$ uses to generate your activation code and all but posted the information on the internet..
http://www.vnunet.com/Analysis/1126488
M$ is dedicated to security alright.
Printable View
See this article.. evidently some smart cracker out there got the info M$ uses to generate your activation code and all but posted the information on the internet..
http://www.vnunet.com/Analysis/1126488
M$ is dedicated to security alright.
I think this deserves more attention than it's getting.
Sorry if think it doesn't.
Agreed - of course, most of us were probably assuming that someone would be able to eventually break Microsoft's new activation scheme, it was just a matter of time. It will be nice to know what exactly inside your machine Microsoft is looking at. I've got to check this out in more detail when I get a little more time.Quote:
Originally posted by KorpDeath
I think this deserves more attention than it's getting.
Sorry if think it doesn't.
But what gets me is that Microsoft can't fix a buffer overflow, the focus of the first part of the article. As many problems that have arisen because of buffer overflows, yet time after time, that exploit keeps popping up. I know buffer overflows have been discussed in some detail here before so we won't get into now - maybe Microsoft was waiting till February to start their new found focus on security. :)
Quote:
Originally posted by Maverick811
Agreed - of course, most of us were probably assuming that someone would be able to eventually break Microsoft's new activation scheme, it was just a matter of time. It will be nice to know what exactly inside your machine Microsoft is looking at. I've got to check this out in more detail when I get a little more time.
But what gets me is that Microsoft can't fix a buffer overflow, the focus of the first part of the article. As many problems that have arisen because of buffer overflows, yet time after time, that exploit keeps popping up. I know buffer overflows have been discussed in some detail here before so we won't get into now - maybe Microsoft was waiting till February to start their new found focus on security. :)
Microsoft employs weak coders. On the whole they are lazy and uninspired.
But there are, what, 20,000 of them. So the more the merrier............... :ubergun:
Sadly enough, buffer overflows are also a major problem in Linux. You'd think that by now they'd have patched all those up.Quote:
Originally posted by Maverick811
But what gets me is that Microsoft can't fix a buffer overflow, the focus of the first part of the article. As many problems that have arisen because of buffer overflows, yet time after time, that exploit keeps popping up. I know buffer overflows have been discussed in some detail here before so we won't get into now - maybe Microsoft was waiting till February to start their new found focus on security. :)
sorry if this a n00b question but do you know where I can find the KeyGen at? Right now I do have XP Pro but would like to load it on multiple computers, any links would be helpful. I did read the article though... obviously it's not there. :D
ArmyOfOne, your kidding right ?? :D
"Did you know that by replacing 11 files on a retail Windows XP CD for an existing corporate edition CD, you can turn it into an unactivated corporate version? This has been tested and it does successfully work! It is important to note that this does NOT hack Windows XP in any way, it merely bypasses WPA. You do, however, need a valid 25-character PLK. It will be interesting to see if Microsoft fixes this loophole in the first service pack release. I have not monitored my traffic logs through our checkpoint firewall to see what was communicated yet... I really am surprised Microsoft would leave such an obvious and easily exploitable method to get around WPA. The files you need to replace are:
i386\dpcdll.dl_
i386\eula.txt *** cosmetic only
i386\nt5inf.ca_
i386\oembios.bi_
i386\oembios.ca_
i386\oembios.da_
i386\oembios.si_
i386\pidgen.dll
i386\setupp.ini
i386\setupreg.hiv
i386\win9xupg\win95upg.inf
End quote.
LEGAL NOTICE - This is what my lawyers made me say [grin]. Do not try this at home, and do not violate any existing license agreements you have with any of your software vendors.
you say I need to replace those files... but with what?
http://ditoa.freeshell.org/winxp/index.htmQuote:
Originally posted by ArmyOfOne
you say I need to replace those files... but with what?