Unless this has changed from years back, an enencrypted stack, even when built into a standalone, can be pried out if someone is naughty.
On Wed, Feb 27, 2013 at 4:31 AM, Monte Goulding <mo...@sweattechnologies.com > wrote: > > 1. Who is going to check on this sort of thing? > > Not me... hoever, there's likely to be lots of lc users wanting RunRev to > stay in business so they will often report breaches. > > > > 2. Is a Livecode OS standalone going to be constructed in such a way > that it > > can be "unpeeled" without having recourse to a bare stack? > > Actually it's already like that. Once upon a time I wrote a script to > decouple the engine from the attached stackfile... But basically look at a > standalone you didn't password protect in a text editor. > > -- > Monte Goulding > > M E R Goulding - software development services > mergExt - There's an external for that! > > > > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
