topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • July 17, 2018, 12:21 PM
  • Proudly celebrating 13 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Last post Author Topic: crack tracker  (Read 15838 times)

Tbank

  • Participant
  • Joined in 2010
  • *
  • default avatar
  • Posts: 1
    • View Profile
    • Donate to Member
Re: crack tracker
« Reply #25 on: October 20, 2010, 08:14 AM »
Hi gurus, Pls can u help me 2 crack macromedia fireworks software&send me d hint thanks

tomos

  • Charter Member
  • Joined in 2006
  • ***
  • Posts: 11,263
    • View Profile
    • Donate to Member
Re: crack tracker
« Reply #26 on: October 20, 2010, 09:19 AM »
Hi gurus, Pls can u help me 2 crack macromedia fireworks software&send me d hint thanks

Hi Tbank,
have a closer look at the first post
Many people here are selling their software for a living. For all you authors suffering from cracks and keygens, this tool I made will make things a bit easier. It searches for illegal downloads of your software and presents them in a list, so you can file a DMCA complaint with rapidshare and similar hosting companies, so that your illegal downloads are removed
[...]

i.e. no warez here
Tom

f0dder

  • Charter Honorary Member
  • Joined in 2005
  • ***
  • Posts: 9,112
  • [Well, THAT escalated quickly!]
    • View Profile
    • f0dder's place
    • Read more about this member.
    • Donate to Member
Re: crack tracker
« Reply #27 on: October 22, 2010, 01:49 PM »
Hi gurus, Pls can u help me 2 crack macromedia fireworks software&send me d hint thanks
DoCo is getting indexed pretty well by google, is it? ;P

As for how warez and countermeasures affects software sales - gosh that's a big and complex debate, and it depends extremely much on your product, target market, competitors, et cetera. Personally I believe in making non-draconian licenses, and not over-doing the anti-piracy measures; a lot of the time, you end up penalizing the legitimate users while not being much of a burden for pirates. Put a few locks on to keep the honest people honest, but don't think you can ever win the battle - because you can't. Even ├╝bercomplex solutions which implement part of program functionality in hardware dongles, and do complex mathematical transformations of your program code into finite state machines, have been broken. The more interesting the task is (and of course the higher profile your product is), the more talented reverse engineers will be driven towards your product.

IMHO a really nice idea is using "partially validated keys", where your app will accept a "range" of valid keys - later revisions can do more refined checks, or use a webservice/whatever at a later point, to do a full key check (either using a full algorithm online, or verifying particular license through customer database lookup). The trick, then, is to let the user play around with his pirate copy and get "attached" to the program... then a few weeks later, throw up a nag screen every now and then telling the user that he's using a pirated copy, and that he might want to consider registering the application - but don't crashbomb the application, leave it fully working. For some products, that has given additional sales. Of course some crackers will also remove that part of the protection, but oh well.

You can't really do anything to completely fend off crackers, until we're all running on heavily locked-down Trusted Computing systems - and even then, there might be backdoors. But for now, even if you can generate per-user custom-built executables with code reorganizing and embedded watermarks, protection code in signed Windows drivers, encrypted code sections delivered by license-checking webservices, and parts running on custom hardware dongles... your system will be broken - so don't overdo it :)
- carpe noctem

umeca74

  • Member
  • Joined in 2006
  • **
  • default avatar
  • Posts: 48
    • View Profile
    • Donate to Member
Re: crack tracker
« Reply #28 on: October 24, 2010, 01:17 AM »
for the key/keygen part i believe i have it pretty much sorted out, see here:
www.zabkat.com/blog/27Jun10-openssl-keygen.htm

not that it will stop piracy either, but it will kill all keygens, leaving just the patches :)

f0dder

  • Charter Honorary Member
  • Joined in 2005
  • ***
  • Posts: 9,112
  • [Well, THAT escalated quickly!]
    • View Profile
    • f0dder's place
    • Read more about this member.
    • Donate to Member
Re: crack tracker
« Reply #29 on: October 24, 2010, 10:38 AM »
for the key/keygen part i believe i have it pretty much sorted out, see here:
www.zabkat.com/blog/27Jun10-openssl-keygen.htm
Yeah, read that back in August.

I hope you're not going to use a pipe-delimited set of strings for your registration data - go for something more flexible, at least a set of key/value pairs, and possibly XML. It might seem overkill, but you'll probably end up wishing you did if you don't :)
- carpe noctem

umeca74

  • Member
  • Joined in 2006
  • **
  • default avatar
  • Posts: 48
    • View Profile
    • Donate to Member
Re: crack tracker
« Reply #30 on: October 27, 2010, 01:45 AM »
I am using the scheme already for crack tracker
pipe delimited is functional and makes for shorter keys that can be emailed

f0dder

  • Charter Honorary Member
  • Joined in 2005
  • ***
  • Posts: 9,112
  • [Well, THAT escalated quickly!]
    • View Profile
    • f0dder's place
    • Read more about this member.
    • Donate to Member
Re: crack tracker
« Reply #31 on: October 27, 2010, 02:32 AM »
Doing a key-value format, even as XML, doesn't bloat size out of the "emailable" realm - and the added flexibility is well worth it, IMHO.

But hey, it might work well for your purposes, and if you're lucky you might not need to expand later on... pipe-delimiting just isn't a good general solution (again, IMHO).
- carpe noctem