Password-protecting a stack

[David Vaughan]

Chipp

Do you need to go cross-platform? How good do you need the protection to 
be?

I was thinking that you may be able to use a scriptable encryption 
program on OSX to secure your stack between use, although it would still 
be accessible during the time it was decrypted and in use.

A stream encryptor would remove the accessible-file problem, so the data 
was stored in a file and decrypted only in memory for insertion in an 
empty stack at startup (if that is where you need to have it). I do not 
know immediately of any stream encryptors useable by Rev unless you 
write a basic one yourself although I am sure they are out there (at 
least as a set of algorithms). It seems a popular field for writing 
free- and shareware.

Sorry about the "thoughts" rather than "answers" nature of the response.

regards
David

On Wednesday, April 10, 2002, at 04:32 , Chipp Walters wrote:

> Thanks for your response, Wolfgang.
>
> I understand what you're saying. The problem I'm having is that I can 
> save a
> stack, set the password, but still anyone with RunRev can view the 
> contents
> of the saved stack (and are only prompted for the password when they 
> try to
> edit a script) -- as I'm saving the stack for ONLY the contents (as in a
> datafile) it doesn't provide me much security.
>
> thanks anyway,
>
> Chipp
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>