Re: Just What Does Password Protect/Inhibit?

[Peter Reid]

>  > So what does password protecting a stack inhibit:
>
>(snip)
>
>You can create objects, but I think the restriction you are running into is
>that you can't copy objects (the only other restriction I know is that you
>can't get or set scripts).  If you could, then you could copy password
>protected objects into a non-password protected stack and thus access the
>scripts.
>
>Regards,
>
>Kevin

OK, thanks for the info, now I know what I need to work around as necessary.

Cheers
Peter
-- 

Peter Reid
Reid-IT Limited, Loughborough, Leics., UK
Tel: +44 (0)1509 268843 Fax: +44 (0)870 052 7576
E-mail: [EMAIL PROTECTED]
Web: http://www.reidit.co.uk

Archives: http://www.mail-archive.com/metacard@lists.runrev.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.

Re: Just What Does Password Protect/Inhibit?

[Kevin Miller]

On 23/12/00 1:43 am, Peter Reid <[EMAIL PROTECTED]> wrote:

(snip)

> So what does password protecting a stack inhibit:

(snip)

You can create objects, but I think the restriction you are running into is
that you can't copy objects (the only other restriction I know is that you
can't get or set scripts).  If you could, then you could copy password
protected objects into a non-password protected stack and thus access the
scripts.

Regards,

Kevin

Kevin Miller <[EMAIL PROTECTED]> 
Runtime Revolution Limited (formerly Cross Worlds Computing).
Tel: +44 (0)131 672 2909.  Fax: +44 (0)1639 830 707.


Archives: http://www.mail-archive.com/metacard@lists.runrev.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.

Just What Does Password Protect/Inhibit?

[Peter Reid]

I thought that setting the password on a stack stopped anyone getting 
at the scripts but otherwise left the stack modifiable.  However, I 
just put a password on a stack that creates grouped image + text 
objects on the fly as and when needed and found that this no longer 
worked with the stack password protected.  As soon as I removed the 
password (or used the "set the passkey of this stack" command), it 
worked again!

This is a potential problem since I want to protect the scripts (and 
any externals, as per licence conditions), but can't do so if the 
stack needs to create objects on the fly!!  Alternatively, I have to 
get the stack to unlock itself on the fly as and when needed by using 
the "set the passkey of this stack" command - again, a bit messy!

So what does password protecting a stack inhibit:

- creating new objects (using "copy" and "paste")?

- creating/updating object properties?

- modifying existing scripts?

- creating new scripts/handlers on the fly?

etc.

This was tested with the latest build (downloaded a couple of days 
ago) of MC 2.3.2 for PowerPC Mac.

Peter
-- 

Peter Reid
Reid-IT Limited, Loughborough, Leics., UK
Tel: +44 (0)1509 268843 Fax: +44 (0)870 052 7576
E-mail: [EMAIL PROTECTED]
Web: http://www.reidit.co.uk

Archives: http://www.mail-archive.com/metacard@lists.runrev.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.