Encrypting Stack Breaks Field References

[Richard Gaskin]

Mark Waddingham wrote:

On 12/13/20 6:02 PM, Richard Gaskin via use-livecode wrote:
 >>
 >> Copying objects is disallowed in an encrypted stack, since of course
 >> once an object is copied it could be pasted into an unencrypted
 >> stack, and thus expose the source.
 >
 > Its not the copy that will be failing - but the create. In general you
 > can't do anything to an encrypted stack which might cause a script to
 > move from where its encrypted to somewhere else or vice-versa. (The
 > reason create is disallowed is that you could create a new script via
 > setting props of the template object).

Would the copy action not fall under the rubric of "anything to an 
encrypted stack which might cause a script to move from where its 
encrypted to somewhere else or vice-versa"?

If I receive a protected stack and copy an object out into an 
unprotected stack, I would then have access to the object's script.

-- 
  Richard Gaskin
  Fourth World Systems
  Software Design and Development for the Desktop, Mobile, and the Web
  ____________________________________________________________________
  Ambassador at FourthWorld.com                http://www.FourthWorld.com