Saving encrypted customProperties outside the app?

[Alex Rice]

On Friday, September 26, 2003, at 03:38  PM, Richard Gaskin wrote:
> Weird perhaps, but functional and available now.
> <http://lists.runrev.com/pipermail/use-revolution/2003-June/ 
> 017437.html>

Thanks for the clarification Richard.

> For the future it seems useful to have another level of protection for
> custom props, but the hard part is coming up with a way for the engine  
> to be
> able to get and set properties in your standalone without having the  
> Rev IDE
> or stacks from intruders read them.   If you come up with a solution
> Bugzilla an ehancement request for it.

  From my perspective the whole password+encryption mechanism  
convoluted. Some aspects are encrypted, some aren't, some aspects are  
password protected, some aren't. The engine itself has elevated  
privileges and can open, run and edit almost all aspects of a  
supposedly encrypted stack. Something just doesn't seem right about  
this.

I would like to see a stack protection feature that does encryption-  
through and through. In order to open, run, read, edit, *do anything*  
no matter if via engine or via IDE, first one would first have to  
authenticate. It could be password authentication or public key  
authentication. Authentication could be done by prompting the user, or  
done by a script in an already running stack.

Maybe a good idea for a 3rd party plugin. The ABC framework for Cocoa  
programming has something like this- encrypted media bundles you can  
ship inside your app bundle.

Sorry for rambling,

Alex Rice <alex at mindlube.com> | Mindlube Software | http://mindlube.com

what a waste of thumbs that are opposable
to make machines that are disposable  -Ani DiFranco