Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. if my apps trial period expired

if my apps trial period expired

Scheduled Pinned Locked Moved C / C++ / MFC
question
5 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    BaldwinMartin
    wrote on last edited by
    #1

    When the trial period of my app has expired (jtodaysdate - jinstalldate) plus some other things I better not mention here. Should I? Write to the executable a bunch of 01010101010101 or set a GUID mutex atom to a instance of the os? Best Wishes and Happy Holiday's, ez_way

    A B 2 Replies Last reply
    0
    • B BaldwinMartin

      When the trial period of my app has expired (jtodaysdate - jinstalldate) plus some other things I better not mention here. Should I? Write to the executable a bunch of 01010101010101 or set a GUID mutex atom to a instance of the os? Best Wishes and Happy Holiday's, ez_way

      A Offline
      A Offline
      Antti Keskinen
      wrote on last edited by
      #2

      The best way to implement a trial period schema is to use some method that modifies the application executable itself. This way, a peep who'd want to hack your trial protection would need to have solid understanding of assembly and reverse-engineering. Of course, the securest method would be a combination of executable modification, registry keys and INI/DLL-files. -Antti Keskinen ---------------------------------------------- The definition of impossible is strictly dependant on what we think is possible.

      B 1 Reply Last reply
      0
      • A Antti Keskinen

        The best way to implement a trial period schema is to use some method that modifies the application executable itself. This way, a peep who'd want to hack your trial protection would need to have solid understanding of assembly and reverse-engineering. Of course, the securest method would be a combination of executable modification, registry keys and INI/DLL-files. -Antti Keskinen ---------------------------------------------- The definition of impossible is strictly dependant on what we think is possible.

        B Offline
        B Offline
        BaldwinMartin
        wrote on last edited by
        #3

        OK Great, I have lost faith in folks ability to be honest. I posted my static ip on codeproject by accident in a response and have gotton 82 hack attempts so far, none got through. Anyway I thank you and understand the reference to dll and ini and have implemented them. I guess I will write 0's 1's to the executable also. If I set the GUID of the mutex to the guid of the os and only allowed 1 instance that would be cool, also! Great answer thank you!:) Best Wishes and Happy Holiday's, ez_way

        1 Reply Last reply
        0
        • B BaldwinMartin

          When the trial period of my app has expired (jtodaysdate - jinstalldate) plus some other things I better not mention here. Should I? Write to the executable a bunch of 01010101010101 or set a GUID mutex atom to a instance of the os? Best Wishes and Happy Holiday's, ez_way

          B Offline
          B Offline
          Brian Shifrin
          wrote on last edited by
          #4

          Neither, I would think you want to show nice dialog: "Trial period expired", visit website to purchase licenses and get free upgrades. Writing over executable with "0101" is childish and not productive. On the day X user could have clicked on your executable by mistake and closed app. Next thing he/she knows application exits w/o warning... Is it broken? Messed up? Would writing over executable stop even novice hacker? I doubt that. All it takes to nop area "call WriteFile[A]"... Brian

          B 1 Reply Last reply
          0
          • B Brian Shifrin

            Neither, I would think you want to show nice dialog: "Trial period expired", visit website to purchase licenses and get free upgrades. Writing over executable with "0101" is childish and not productive. On the day X user could have clicked on your executable by mistake and closed app. Next thing he/she knows application exits w/o warning... Is it broken? Messed up? Would writing over executable stop even novice hacker? I doubt that. All it takes to nop area "call WriteFile[A]"... Brian

            B Offline
            B Offline
            BaldwinMartin
            wrote on last edited by
            #5

            Yes sure and I can go around a dlgbox in half a minute, so can you I guess, but I think I will stick with an original plan. Look at the cracks available on the web for what you are advocating.:rose: Thank you for the response. Best Wishes and Happy Holiday's, ez_way

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • World
            • Users
            • Groups