![]() |
new KeyGenMe
1 Attachment(s)
hi all members
I made a KeyGenMe for you language : asm not packing , size : 18KB |
1 Attachment(s)
Name: giv
Serial: 39483950 No time for a keygen. ASM keygening is not my strong point. :) |
I had a little free time today, so I created a quick keygen in Delphi:
Code:
procedure TForm1.Button1Click(Sender: TObject); |
Nice share Mr. chessgod101
Thank You |
Nice work.Not strong there myself.
|
Because is not to easy to implement the sha256 to VB .NET here is the algo:
1. Get the name and make a sha256 from it. 2. Make a function that: Declare a counter ECX = 0 Declare result EAX = 0 Move in a variable (EBX) every byte of the array. EBX = EBX*ECX EBX = EBX*EBX EBX = EBX + 50h EAX = EAX+EBX ECX = ECX+1 Loop until the bytes in the array ends. The result will be xorred with 12345678h |
@GIV SHA256 difficult in VB.NET?
Quote:
|
Quote:
But i have one small question: From Keygener Assistant 2.1.0 the output from string: Quote:
Quote:
Quote:
Here is the code i have implemented: Quote:
|
@giv If you use Windows XP for SHA256 in any .NET language it appear issues.
|
So is kinda useless for me to start keygening this under XP in VB .NET
Unfortunate i have only XP. |
giv, the problem is that the string is being encoded as unicode. In order to get the correct hash, you need to encode the string using ASCIIEncoding instead of UnicodeEncoding.
When the string is encoded as unicode, these are the bytes that get hashed: Code:
67 00 69 00 76 00Code:
67 69 76 |
Quote:
Maybe L.C. is right. I must change XP |
@giv, try using Encoding.Default in C#. This should fix the issue because I have encountered such issues before while Keygenning and Encoding.Default Solved the Problem.
|
I will try tomorrow at work (on work PC is the sourcecode) and post the result.
|
Hello Brother's.
I think keygen me and reverse me's for New reverser's. You may post that in easyly downloadable. (because still I don't have download permission :D ) |
1 Attachment(s)
At least here is my keygen in VB 2010.
The SHA function must be modified as chessgog101 says. Quote:
|
@giv, by modified, do you mean that you modified the 4 uint values used in the creation of the hash?
As far as i know, the Sha-256 hashing is embedded in the .NET framework and it does not give room for modifying the uint values except you implemented the whole crypto procedure from the scratch. I have seen such implementation for md5 before but not for sha-256. Could you share your implementation please? |
edit:
Could Not Edit The Previous Post. @giv, Your Hash Does Not Seem To Be Modified Since The Magic Byte In Your Keygen are The Same With The Original SHA-256 Implementation. Here Are The Bytes. 0x6a09e667; 0xbb67ae85; 0x3c6ef372; 0xa54ff53a; 0x510e527f; 0x9b05688c; 0x1f83d9ab; 0x5be0cd19; |
Look at uEncode in the SHA function.
|
| All times are GMT +8. The time now is 16:41. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2026, vBulletin Solutions, Inc.
Always Your Best Friend: Aaron, JMI, ahmadmansoor, ZeNiX