You didn't answer my question. I am beginning to doubt what you are selling. You claim to have a method to generate microsoft keys and
this method will provide you valid keys of several types.
I don't think you know what is contained in a valid key. A Product key like BBBBB-CCCCC-DDDDD-FFFFF-GGGGG is base-24 encoding of a hexadecimal number that has the key at the beginning and a signature at the end similar to bitcoin signed message. The signature is verified by windows using a public key hardcoded in Windows and a private key stored in secure microsoft servers, one key pair for each edition.
You should know that even if you manage to generate a microsoft key, they check their servers whether the key hasn't been sold or not, and they will block you if you activate with an unsold key. This is why some people successfully bought and used product keys from other sellers here since they bought them from microsoft beforehand. This is also why you don't see people using keygens to activate windows because it will just phone home to check whether the key had been sold
https://security.stackexchange.com/a/13680You should also read this, product key generation hasn't changed since Windows XP.
>>>> Product Key
The Raw Product Key is buried inside the Product Key that is printed
on the sticker distributed with each Windows XP CD. It consists of
five alphanumeric strings separated by '-' characters, where each
string is composed of five characters, as in
FFFFF-GGGGG-HHHHH-JJJJJ-KKKKK
Each character is one of the following 24 letters and digits:
B C D F G H J K M P Q R T V W X Y 2 3 4 6 7 8 9
Very similar to the decimal encoding of the Installation ID the 25
characters of the Product Key form a base-24 encoding of the binary
representation of the Product Key. Decoding the Product Key yields a
multi-precision integer of roughly 115 bits, which is stored - again
in little endian byte order - in an array of 15 bytes. Decoding the
above Product Key results in the following byte sequence.
0x6F 0xFA 0x95 0x45 0xFC 0x75 0xB5 0x52
0xBB 0xEF 0xB1 0x17 0xDA 0xCD 0x00
Of these 15 bytes the least significant four bytes contain the Raw
Product Key in little endian byte order. The least significant bit is
removed by shifting this 32-bit value (0x4595FA6F - remember the
little endian byte order) to the left by one bit position, resulting
in a Raw Product Key of 0x22CAFD37, or
583728439
in decimal notation.
The eleven remaining bytes form a digital signature, allowing
verification of the authenticity of the Product Key by means of a
hard-coded public key.
Having said all that, there are two possibilities what your service is:
- You either hacked Microsoft for the private keys and you have a working "unlimited method", using the private key to create signatures, or
- You are pulling a scam.
Pick one. There is no way to mimic the signature part of the product key without the private key. I will wait for your answer.
