![]() ![]() ![]() The immediate problem I see with this approach is that some product keys randomly generated by rogue key generators will coincidentally be the same as legitimate keys issued by Microsoft. To me the most obvious thing that should be done is to check all product activation requests against a database of serial numbers which are issued by Microsoft. Of course it still alienates users when it's in something like windows, but the users can't do a *censored* thing about it. MS can afford to add all sorts of things to windows- you won't, however, find sophisticated activation and "genuine validation" with some dinky shareware program- it's simply not worth the effort and serves to alienate users. This is not counting weaknesses in the Random Number Generator that can be exploited.Īnyway, when it comes to protecting software, it's simply a matter of trade-offs. Same applies to the newer methods- it would just take several years to crack. now the standard DES can be cracked in less then an hour with a modern machine. For example DES used to be the standard encryption for governments. has nothing to do with windows.Īnd WGA is far from "bulletproof" you cannot have a security method that is "bulletproof" it's impossible.Įven encryption is not "bulletproof" it's just an intractable computation to crack at this point. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |