Scripts and Permissions

From the SL Scripting Tips forum

Winter Ventura did the following tests to see how script permissions behaved. Scripts are similar to textures in SL, in that if they can be seen, they can be copied. However, there has often been some quibbling about exactly what effects the different combinations of permission had.

Well quibble no more!

You can see the full thread this is from here

ACTUAL BEHAVIOUR:
The following results were gathered on January 17, 2009, using Henri Beauchamp's Cool Viewer for SL, based on SL 1.21.6 (0).. the tests were conducted on a (non openspace/homestead) mainland sim, running server 1.24.10.106829. No inventory anomalies were encountered during these tests.

[x]M [x]C [x]T  Opens (code visible)
This case allows full editing of the script by the second owner, permissions can be changed, the code can be read, and the script can be renamed. This is basically an "Open Source" script. The guts of this script can be altered, or copied out using the text-copy tool, and pasted into a new script.

[x]M [x]C [ ]T  Opens (code visible)
This script can be opened, edited, and renamed, but it's permissions can NOT be edited by the second owner. Of course, this script is no-transfer, so there's really no point in changing next-owner permissions, is there? The guts of this script can be altered, or copied out using the text-copy tool, and pasted into a new script.. but the actual script can't be passed on (showing the original creator). This is a great way to share a script with someone, without worrying that they'll make a doomsday device that shows your name as creator.

[x]M [ ]C [x]T  "You are not allowed to view this script."
This script can NOT be opened.. however it can be renamed. You can alter the "modify" permission for a "third" owner, but you can not affect the next-owner's transfer permission.

[ ]M [x]C [x]T  "You are not allowed to view this script."
This script can not be opened, or renamed.. but the second owner CAN affect the copy and transfer permissions for a third-owner. Of course (as always) the choice is really CT, C or T. there's no "none" option here.

[ ]M [x]C [ ]T  "You are not allowed to view this script."
This script can not be opened or renamed.. and the second-owner can not change the third-owner permissions. (being no-transfer, this is a moot point).

[ ]M [ ]C [x]T  "You are not allowed to view this script."
This script can not be opened or renamed.. and the second-owner can not change the third-owner permissions.. Once no-copy, it seems that transfer is automatic.

[x]M [ ]C [ ]T  Case not possible
[ ]M [ ]C [ ]T  Case not possible
These two situations seem to be impossible to create.

[quoted without permission]