Permissions bug in SL
I recently posted to the SL forums what I thought was a serious exploitable copy bug. Turns out it is a bug but one that Linden feels is not serious (read here and thanks to Brent Linden for the help). I agree with them as long as the information is spread so content creators can avoid having their no-copy items copied.
The reasons that this bug exists is that permission settings that are set while object is in your inventory are not cross-checked with the objects contents until it is rezzed. So for example if you place a no-copy item in a copy enabled prim then the prim becomes no-copy are expected. If you place prim in your inventory and change back to copy enabled this state persists even after transferring to another resident because permission are not cross-checked with the objects contents until the object rezzed. If you are not careful you can allow receiving resident to copy no-copy items.
This is kind of like the old joke..
You: Doctor it hurts when I do this.
Dr: Well don't do that.
Only problem is that you may not know you've hurt yourself until it is too late. In my case I had a script that I wanted to be no-copy inside a free modifiable and copy enabled prim. I wanted to give the object to another resident and allow then to copy the container but not the script. I changed the permissions in my inventory and transferred the item to the user. Luckily in this case the second user was my wife's character with me at the helm. I discovered that I could drop multiple copies of the prim each with the no-copy item inside. As I dropped each item they became no copy but the one inside my inventory remained copy enabled. Luckily it was only to myself and not an expensive item anyway but you can see how damaging this could be to someone that sells high priced items.
The reasons that this bug exists is that permission settings that are set while object is in your inventory are not cross-checked with the objects contents until it is rezzed. So for example if you place a no-copy item in a copy enabled prim then the prim becomes no-copy are expected. If you place prim in your inventory and change back to copy enabled this state persists even after transferring to another resident because permission are not cross-checked with the objects contents until the object rezzed. If you are not careful you can allow receiving resident to copy no-copy items.
This is kind of like the old joke..
You: Doctor it hurts when I do this.
Dr: Well don't do that.
Only problem is that you may not know you've hurt yourself until it is too late. In my case I had a script that I wanted to be no-copy inside a free modifiable and copy enabled prim. I wanted to give the object to another resident and allow then to copy the container but not the script. I changed the permissions in my inventory and transferred the item to the user. Luckily in this case the second user was my wife's character with me at the helm. I discovered that I could drop multiple copies of the prim each with the no-copy item inside. As I dropped each item they became no copy but the one inside my inventory remained copy enabled. Luckily it was only to myself and not an expensive item anyway but you can see how damaging this could be to someone that sells high priced items.
posted by Qubius Quinn at 8:34 PM
0 Comments:
Post a Comment
<< Home