On Wednesday, February 4, 2004, at 06:12 AM, Robert Brenstein wrote:
Unfortunately, setting password protection for a stack is currently
a one-way street: setting passKey at execution time will open the
stack to prying eyes with no option to close it back until
Revolution quits.
Can you do all
On Wednesday, February 4, 2004, at 06:12 AM, Robert Brenstein wrote:
Unfortunately, setting password protection for a stack is currently a
one-way street: setting passKey at execution time will open the stack
to prying eyes with no option to close it back until Revolution quits.
Can you do all y
On Tuesday, February 3, 2004, at 01:02 PM, Bojsza wrote:
From the Transcript dictionary for encrypt it says that mcEncrypt
is an internal function...so how can I do it? Is their another
function built in?
Look at password and passKey in the Transcript dictionary.
When you clone to create a data
At 12:57 pm -0700 3/2/04, Dar Scott wrote:
On Tuesday, February 3, 2004, at 12:52 PM, Bojsza wrote:
It doesn't have to be the same password. I just want to have the
stacks that are created by a standalone to be encrypted. So, if I
placed a password field with a password in it and had that placed
--- Bojsza <[EMAIL PROTECTED]> wrote:
> You would have thought that someone would have done
> this at one time to
> protect their "data" stacks?
>
> From the Transcript dictionary for encrypt it says
> that mcEncrypt is an
> internal function...so how can I do it? Is their
> another function bu
Bojsza wrote:
> You would have thought that someone would have done this at one time to
> protect their "data" stacks?
>
> From the Transcript dictionary for encrypt it says that mcEncrypt is an
> internal function...so how can I do it? Is their another function built
> in?
I don't know of one,
On Tuesday, February 3, 2004, at 01:02 PM, Bojsza wrote:
From the Transcript dictionary for encrypt it says that mcEncrypt is
an internal function...so how can I do it? Is their another function
built in?
Look at password and passKey in the Transcript dictionary.
When you clone to create a data
You would have thought that someone would have done this at one time to
protect their "data" stacks?
From the Transcript dictionary for encrypt it says that mcEncrypt is an
internal function...so how can I do it? Is their another function built
in?
Glen
On Tuesday, February 3, 2004, at 01:57
On Tuesday, February 3, 2004, at 12:52 PM, Bojsza wrote:
It doesn't have to be the same password. I just want to have the
stacks that are created by a standalone to be encrypted. So, if I
placed a password field with a password in it and had that placed in
the stack that is part of the distribu
It doesn't have to be the same password. I just want to have the stacks
that are created by a standalone to be encrypted. So, if I placed a
password field with a password in it and had that placed in the stack
that is part of the distribution build can it be used to encrypt any
stacks created?
On Tuesday, February 3, 2004, at 12:25 PM, Bojsza wrote:
Is there a way to have the standalone create stacks that are encrypted
using the same password that was used for the distribution build?
Does this have to be the same password? If the password was put into
the script and the build is encr
I am trying to figure out if it is possible to encrypt a saved stack
that is created from a standalone. When I build the distribution for
the Rev Employee database example I check "Encrypt with password" in
the stacks tab and this works fine for the stacks in the build (the
stacks are : EmpDB,
12 matches
Mail list logo
