Password protection for purchasing standalone applications


    Dec 07 2006 | 11:33 pm
    Hello all,
    In the event that I actually make a patch that people want to buy (heh) does anyone have any ideas or suggestions for how to manage a key-access or password system for paid customers?
    I know it would be relatively simple to have a hidden route object that takes in a code entered into a text box, which would then unlock the program. Of course, that same executeable would be unlockable with that same code, unless it "locked itself down" after the first access. I imagine there's much better ways of doing this, plus it would be nice (though not essential) to not have to make a change to each and every patch sold...
    Any way of using a unique machine ID number? Or something with the system time?
    Thanks for any ideas! -CJ

    • Dec 08 2006 | 4:53 am
      [gestalt] or mxj net.local to tie to the mac address are pretty straightforward, but can be defeated.
      On Dec 7, 2006, at 6:33 PM, Seejay James wrote:
      > > Hello all, > > In the event that I actually make a patch that people want to buy > (heh) does anyone have any ideas or suggestions for how to manage a > key-access or password system for paid customers? > > I know it would be relatively simple to have a hidden route object > that takes in a code entered into a text box, which would then > unlock the program. Of course, that same executeable would be > unlockable with that same code, unless it "locked itself down" > after the first access. I imagine there's much better ways of doing > this, plus it would be nice (though not essential) to not have to > make a change to each and every patch sold... > > Any way of using a unique machine ID number? Or something with the > system time? > > Thanks for any ideas! > -CJ >
      v a d e //
      www.vade.info abstrakt.vade.info
    • Dec 14 2006 | 6:59 pm
    • Dec 14 2006 | 11:07 pm
      Uh ... given this is a public forum/list, and the forum is google-indexed, I'd suggest you don't undertake too much discussion of copy-protection or registration mechanisms here.
    • Dec 15 2006 | 12:33 am
    • Dec 15 2006 | 1:35 am
      Er, thats like saying not to discuss encryption technologies on an email list - ridiculous - if you do it properly, the fact that its open doesnt make the system less secure - as a matter of fact, discussing it, is what will make it more secure, as other - more knowledgeable people can point out insecurities.
      i'll take open source/open designed security over security by obscurity any day of the week -
      On Dec 14, 2006, at 6:07 PM, John Pitcairn wrote:
      > > Uh ... given this is a public forum/list, and the forum is google- > indexed, I'd suggest you don't undertake too much discussion of > copy-protection or registration mechanisms here.
      v a d e //
      www.vade.info abstrakt.vade.info
    • Dec 15 2006 | 5:17 am
      That's what I was hoping for, that someone on here might know a reasonably secure way to do a paid serial/other system for Max applications that people might want to buy. If it's a good enough system it really shouldn't matter that we're discussing it... of course, them hackers (crackers?) are pretty darn savvy.
      Open source----yeah! That's the way to go. I hope something through such open channels can provide with a means for making a little money on applications that are in fact worth the price. I'm only talking like 30 bucks anyways....
      --CJ
    • Dec 15 2006 | 9:16 pm
      Thanks Peter, that was very helpful. I had forgotten about Pace, that does seem to be the way to go for a serious app. Here's to withing I (and anyone else!) get there someday...
      It would be awhile if anything were to come up, but I'll keep your message and information in mind.
      Thanks again. --CJ
    • Aug 18 2010 | 12:43 pm
      hello 3 years ago, why the blank posts? thought we had got rid of these.
    • Aug 18 2010 | 12:46 pm
      peter was using a chinese keyboard layout in these days.
    • Aug 19 2010 | 12:00 am
      man, that guy must have a huge brain to understand all those characters...