the problem lies not with the generation of keys and getting the installer to accept them that is the easy part. The hard part comes in when you need to validate those keys. Same thing with the WinXP keygen, it was fine until WGA came out, now it is useless because the keys are marked as non-genuine as soon as you go online to grab something. The thing someone would want to make is something that takes the installation ID and spits out the activation key for use with the -atp switch.
I'm not so sure about the first sentence, since public keys for Vista/Win7 keys are so much longer than BINKs for WinXP/Server2003, is it really possible to "break" them? And yes validation is another problem, but we don't need to generate retail or volume or oem-nonslp keys (cause almost always it would be a trouble to activate them on-line)... but ability to generate OEM SLP keys for Win7 Enterprise or E or N versions of other editions would be more than a nice opportunity...
As said, Enterprise is not possible, E is dead, so it would leave only N Would it be worth the hustle? SLP key will eventually appear anyway sebus
Why would you think so? Not only there IS a keyrange for "Windows 7 Enterprise OEM:SLP" inside pkeyconfig.xrm-ms, but also there are corresponding to oem:slp "skus" system licenses, located in system32\spp\tokens\skus\ folder of installed Win7 Enterprise... to me it means that if there were any oem slp keys for this edition, generated by MS or keygen, they'd be accepted by Enterprise edition just fine. Of course now it's not worth any big efforts, but i don't know how big they'd be for those who already know what to do? Probably "just" to break some public key to recreate a corresponding private one. May be much more if MS made more changes to the whole key generation/validation process after XP.
Either i totally misunderstood what you were trying to say or you are totally wrong: Win7 SLPs: Vista SLPs: As you can see, double-, triple- and even quadruple-pairs are really common, and sometimes they even exist within the same segment. But regardless, the bottomline still is: No Algo - No Keygen
Strange, Enterprise version is not intended for OEM-PCs Maybe all m$ guys use Enterprise and activate it with there own "geek"-key
Key Gen for Win 7 Thank you all for the input and suggestions it is a learning experience for me so thanks for your patience with a novice!
@ vlad, LOL !!!! @ stolen, He means a facility with many Computers Networked together. They are sometimes used in place of a mainframe or supercomputer.
@vlad: How many computers? I'll try to give some numbers. Suppose Microsoft uses 160-bit ECC over prime field (GF(p)), it means using Pollard's rho algorithm you'll probably need to test up to the order of 10^24 points. Estimates have been done, and for solving for a 160-bit private key with a Pentium M 735 running @ 1.70 GHz* would require in the order of 10^11 years. Or, in other words, you would need in the order of 10^11 chips similar to the aforementioned Pentium M to find it in one year. That "1" followed by eleven zeros, or one hundred billions. By comparison, Jaguar, the world's current fastest supercomputer, has 224,256 AMD Opteron computing cores in its XT5 partition (or 2.24x10^5). Now, if you were able to replace *each* core of Jaguar by a whole Jaguar supercomputer itself, then maybe it could be done in a few years. (*benchmarked @ ~3000 VAX MIPS using Dhrystone 2.1; by comparison, latest Core i7 with TurboBoost can reach 10000 VAX MIPS, so that's a negligible improvement) Now, I don't know the bit length of the ECC they use, and even then, I'm not sure what "flavor" of ECC Microsoft uses, but it seems they use squared Weil and Tate pairings on elliptic curves, maybe even on hyperelliptic curves (people @ MSR published a paper in 2004, about a year before the algorithm for Windows Vista's product key was adopted) Bottom line: either it'll cost you too much (upwards of $100 billion*years; better off buying out Microsoft...), or it'll still cost you too much and by the time you find it another version of Windows will be out.
Key Generator Thank You for the explanation it does help me to learn the different ways out there! my original thinking was to use c plus to view the cd files and find the keys, unfortunately on the upgrade disk the keys listed are default keys that expire after so many days! Now on a dell recovery disk it does give one key for the home edition so I believe whith c plus you can see the manufacture key for that disk but on Microsoft Original Hologram disk there is no key found on the home premium upgrade disk that I have but using your advise I have upgraded the disk to ultimate and added the bios changer and key activator which works great for any computer so Thanks!!!
This thread is going to drag on just like the one for vista keygen and ended up absolultley no where as for finding key you will only find working one's on OEM SLP cd or dvd's and they will only activate with oembios files or bios mods or loaders.
If there was a person capable to take and reproduce keys validation algorithm from pidgenx.dll, the developing of effective brute-force keygen would become possible. I studied keys validation algorithm for Windows XP. Unfortunately, it isn't usable for Windows 7/Vista. The finding of any law of formation of PID from a key (for example, ChannelID) could allow effective search even on single PC. I am convinced of it.