NET programs, I could inspect the registers and memory locations to see what my input is compared against (like what it said in the very first web link). I hope if I could find a tool which actually debugs. Originally I wanted to use OllyDbg to dubug the program, not decompile. I started thinking the entire flow again. (I couldn't find IL Disassembler from M$ btw) Should you have any tools to view/disassemble/decompile DLLs, your contribution will be highly appreciated! Trust me I have inspected this DLL for million times, and I had no luck. We only know the way to go further forward should be XXGetUserkey.dll. It is an external method and we couldn't browse its source. Public static extern bool XxGetUserID( ref string userID) Īnother hurdle came up. Simply, pbcUserKey is the UserKey we input, and what is it going to be compared against? It is passed into the methed modCommon.XxGetUserID(): This.createUserKey = modCommon.XxGetUserID(ref this.pbcUserKey)
This.pbcUserKey = Strings.LSet(Strings.Trim(this.pbcUserKey), 16) This.pbcUserKey = Strings.Trim( + + this.txtUserKe圓.Text + ) I finally could inspect the btnOK_Click method: private void btnOK_Click(object sender, EventArgs e) Then I moved on to other free alternatives, such as ILSpy (free) and. And more, I don't have confident that it is guaranteed to get the UserKey after purchasing the. NET decompiler (wtf) as it isn't a freeware, and it costs 399 USD (not less for me).
Sadly, the method content is masked by // trial in. After my first inspection into the source code, I located the critical method btnOK_Click() which is the point for checking the UserKey. In order to find the program that will help ya.įirst, I came upon.
Olly isn't the answer here, because its a. However, I found it is a Microsoft Visual C# / Basic.
I started with this site teaching How to get the serial number of a program with OllyDbg. I did a few researches, and a lot more google searches. After I copied that KEY (and with some programming knowledge), it works like magic. I couldn't locate it because it wasn't under the path of the software name. In short, there is really a KEY in the registry. I have just did it (or better say hacked it :-) Thanks all the guys who have been trying to help.