Results 1 to 4 of 4

Thread: Analysis of ASProtect Keygeneration scheme

  1. #1
    foxthree
    Guest

    Analysis of ASProtect Keygeneration scheme

    Hi Folks:

    I present below some of my analysis of the ASProtect's keygeneration scheme. I may be entirely off but like I said it is just my analysis that I wanted to share with fellow RCEs...

    Okey. I recently acquired a ASProtect Key

    Just by looking at it one can see that it is Base64 encoded. So, let's decode...

    Decoding gives us 129 bytes of data..

    hmmm.... this reminds me of ....... yes "PK Signatures"

    In PK cryptography, you can sign arbitrary amounts of data and some algorithms generate 128 bytes of output signature.... (sometimes it is 128-bits also....)

    So, my analysis is this is what probably Alexey does in his labs

    (A) Get the userinformation (like name, email)
    (B) Frame a string and end it will null (explains the last 129th byte)
    (C) Uses his "Private key" to sign the data and
    (D) Base 64 encode this

    Distribute this as key...

    On the application side, each app has the public key! So decrypt, check few bytes in the header to see if decryption is sucessful. If yes, say registered else run as unregistered app.

    What do you guys think?

    Signed,
    -- FoxThree
    I promise that I have read the FAQ and tried to use the Search to answer my question.

  2. #2
    הבּרוּ נשׂאי כּלי יהוה mike's Avatar
    Join Date
    Mar 2001
    Posts
    491

    PK stuff in ASPR

    I haven't looked at it, so I can't say. MD5 has 128-bit output, so he may hash the information before signing it. Most PK stuff will use at least 512 bits, because 128-bit numbers are almost trivial to factor.

    Modular exponentiation happens in a loop over the exponent bits where you'll have a squaring and a conditional multiply (if the exponent bit is one) followed by a modular reduction. Chances are he'll use some kind of bignum code if he's doing PK stuff. Have you seen any code similar to that?

  3. #3
    According to Asprotect v1.1 keygen info,
    Protection =RipeMD 160 , MD5, RSA-1024 and offcourse base64 encoding
    "There is only one road to human greatness: through the school of hard knocks." Albert Einstein

  4. #4
    הבּרוּ נשׂאי כּלי יהוה mike's Avatar
    Join Date
    Mar 2001
    Posts
    491
    RSA-1024
    Yeah, that makes sense: 128 bytes = 1024 bits

    Is the decryption key checksummed? If not, then you can replace it with your own.

Similar Threads

  1. A nasty id/pass scheme
    By Bitman in forum Advanced Reversing and Programming
    Replies: 12
    Last Post: June 5th, 2007, 19:55
  2. The new MS protection scheme
    By Goat in forum Advanced Reversing and Programming
    Replies: 14
    Last Post: August 31st, 2001, 05:06
  3. microsoft's registration scheme
    By disavowed (restored) in forum Advanced Reversing and Programming
    Replies: 3
    Last Post: May 20th, 2001, 10:51
  4. Attention -> Possible new asprotect 1.2 scheme to reach the oep
    By tsehp in forum Advanced Reversing and Programming
    Replies: 3
    Last Post: March 2nd, 2001, 02:45
  5. microsoft's new anti-piracy scheme for whistler
    By disavowed in forum Advanced Reversing and Programming
    Replies: 5
    Last Post: January 21st, 2001, 01:13

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •