1. AFAIK other source codes may not refer to the values as n and k but they will be in there otherwise you cant produce a key. 2. setupp.ini determines what type of key will be accepted during installation. The pidgen.dll files for retail and volume are not the same. check the hash value of Windows XP Pro Retail vs Windows XP Pro Volume.....they are different! Retail and OEM use the same pidgen.dll because there are 2 sets of BINK parameters in every pidgen.dll file. The BINKID that is even is used for retail keys. The BINKID that is odd is used for OEM keys.
hi, sorry may be i am wrong but what you talking about ? K, N, KN etc have afaik nothing to do with the key System, this is only a spetial kind Installationsmedium for the Main Produkt (and the activation process)
No Im not talking about the windows versions “K”, “N” and “KN”. This is something completely different. The use of K and N is merely coincidental.
There's a whole book on Elliptic Curves I'd recommend for better understanding in general. It goes deep into the nitty-gritty of the entire subject. As a new forum member, I cannot post links, so here's how the book's called: Rational Points on Elliptic Curves by Joseph H. Silverman BINK resource fields are greatly helpful!
How can we extract BINK from a pidgen.dll? Namely for other than already available editions like Home or x64 Pro
Okay here is the latest version I have, but its been a while since I have tinkered with it so I can't remember if there are any changes from the file Carlos posted. Code: File: EllipticCurveTool.7z CRC-32: 3d0c6c4b MD4: 63b5d39c7f351780700fc527d7284856 MD5: 267f5f771c863d9cc97db0568370b777 SHA-1: 89bca7d0facdf80cdd3c3d9fc3e479f9babf6afa File: EllipticCurveTool.exe CRC-32: ab00d8dd MD4: 3f521c80d2425415b00d11ae9a2bf1b2 MD5: 97fdfe2b381f7cbe38ca4bd2c5a4aa0f SHA-1: dd862e1fc055b2f59d8b9da7d6111ce1a92834d8
Use the "Import from file" button and choose a "pidgen.dll" file. The program will search the file for BINK resources. If it finds any it will save them in a keyset (ks2) file. *WARNING* its probably best to tick "Prompt" option otherwise the program will overwrite existing keyset files without warning.
What's the password? The previous one doesn't work, you can use a same simple password, no need for complex ones For Windows XP Home x86, it puts two files BINK ID2A.ks2 BINK ID2B.ks2 in the Keysets\Baseline folder but there are no options on the dropdown menu after or if I reopen the program Also if on the path there are unicode characters it can't import the file, e.g. the default "C:\Documents and Settings\user\Επιφάνεια εργασίας\pidgen.dll" for the Greek XP version I'm using, on a simpler "C:\tools\pidgen.dll" it works
To see the baseline keysets you need to tick "Base Line" option. the program is not build for unicode. sorry.
yeah you can calculate the value of n using sagemath or ecctool. and you can calculate k using ecdlpsolver.