I’ve learnt quite a few things from this:

AquaticPrime works just as intended. The flaw I highlighted yesterday isn’t a flaw because AquaticPrime wasn’t designed to defeat attacks of the kind described. Although nowhere on the AquaticPrime website or inside the documentation will you find any of this discussed. We can generously put this down to an innocent omission.

Even though this isn’t a flaw it seems great efforts are made in people’s code to prevent runtime attacks. Remember, it isn’t a flaw, it is a design decision.

Paradoxically, even though my posting failed to identify a flaw in AquaticPrime (so no harm done right?), several people are rather quite angry that I have discussed it in the open. Apparently openly criticising open source software is not allowed. In fact I have been called some very nasty names from one particular AquaticPrime supporter over this.

It seems that some developers have given up the fight with pirates over runtime/binary attacks. Granted this is a really tough fight to fight, but i find it very interesting that the recommended tactic is to just give up. I think this is wildly underestimating pirates and especially the more casual pirates. The argument seems to be that the casual pirates will not bother finding/installing/running runtime cracks. And that spending effort trying to defeat the hardcore pirate is a waste of time.

However, with all the file sharing sites/software available to anyone today, casual pirates will be able to find cracks rather easily. And casual pirates probably won’t have any problems running these cracks on their machines (after all they’re probably already running keygens for their stolen Adobe software). Giving this fight up seems to be giving up a little too easily.

So finally be really careful when claiming that the “emperor has no clothes”. Such claims will never be received in a positive manner, regardless of whether the emperor is indeed stark naked or in fact wearing the latest, most advanced, invisible wardrobe.