> ensure that there is something broken about them that easily identifies them as a cracked copy. If the broken thing ends up publicly known, then it will just

> ensure that there is something broken about them that easily identifies them as a cracked copy. If the broken thing ends up publicly known, then it will just get fixed in the next cracked version. But if you keep it under wraps, then you'll end up with a reputation for writing buggy, unstable software, especially when the inevitable false positives occur.