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.

Geek T-Shirts

I have 5 different geeky t-shirts listed for sale at SecondServer.net and at my in-world in Oyster. Now only L$5 each (cheaper then an texture upload).

Q2 Access Control System v2.0

I just posted version 2.0 of my Access Control System (ACS) on SLExchange and SecondServer.net. This version fixes several bugs and greatly improves the usability of the system. Included in the version are many new example systems including double sliding doors by popular demand. Also, I have decided to release all future versions as copy/no-transfer to ease the upgrading process. As the new version is copy enabled you do not need multiple copies.

Description
The Q2 Access Control System is a robust modular system designed primarily for controlled access doors but capable of handling other systems where restricted access is required. It maintains an access list of users that can lock and unlock the object. All the configuration details are controlled by an configuration note card modifiable by the owner. In addition all configuration details can be modified by users on the permissions list using the command channel.

This object can be either locked or unlocked. In locked mode only users on the access list can unlock the system via a command channel. When unlocked anyone can access the system (for example open/close the door). The object/door can be opened and closed (when unlocked) by touching it or via a sensor (if enabled). As a door the system can be configured to auto close after a time period set by the users. The action to opening and closing the system can be configured by the user via scripting. The ACS comes with several example systems including: Hinged Door, Hinged Door (1 prim), Double Hinged Door, Sliding Door, Double Sliding Doors, Iris Door, Shrinking Door, and a Window.

ACS v2.0 Features

• Open/Close on touch or optional proximity sensor
• Modular systems allows full customization of open/close actions (several examples included)
• Q2 ACS is not just for doors, see window example
• Optional auto close timer
• Option settings for sounds on open/close
• Lock/unlock via command channel for users on access list
• Maintains list access list of user names that can lock/unlock and configure the system in addition to owner
• Names based access list; No need to get UUID of users
• Fraud protection protects against various forms of name spoofing
• Optional auto lock system allows for valid users to open without issuing unlock command
• With optional auto lock enabled listen can be disabled
• Customizable welcome, locked, lock, and unlock messages
• All configuration settings including access list set using note card for persistence
• Owner and valid users can modify settings via voice commands
• Several example systems included: hinged, 1-prim hinged, double hinged, sliding, double e sliding, variable opacity window, turnstile
• All example prims are modifyable and copyable to fit your needs
• Now includes a simple menu driven system for creating examples

Permissions

• ACS script is no-mod, copy, no transfer. Purchase teh system once to control all doors in your building
• All example prims and action scripts are modifyable and copyable to fit your needs
• No-copy, transferable versions are on a per request only

SecondServer

The Q2 Access Control System has been listed at Second Server.net in addition to several geek t-shirts at 10L$ each. Listing to SecondServer is similar to listing at SLExchange with the additional ability to distribute the products to in game vendors. If SecondServer is as reliable and see as much traffic as SLE it is probably a better choice for distributing SL products. Only SLExchange takes PayPal (RL$) to purchase SL items but I don't see that as a big driver.

Q2 Access Control System

I've just released version 1.0 of what I'm calling Q2 (short for Qubius Quinn) Access Control System (ACS). The Q2 ACS is a robust script designed primarily for controlled access doors but capable of handling other systems where restricted access is required. It maintains an access list of users that can lock and unlock the object. All the configuration details are controlled by an included config note card modifiable by the owner. In addition all configuration details can be modified by users on the permissions list using the command channel.

This object can be either locked or unlocked. In locked mode only users on the access list can unlock the system via a command channel. When unlocked anyone can access the system (for example open/close the door). The object/door can be opened and closed (when unlocked) by touching it or via a sensor (if enabled). As a door the system can be configured to auto close after a time period set by the users. The reaction to opening and closing the door can be configured via scripting (examples for hinged, sliding, and iris type doors included).

Q2 ACS can be purchased through SLExchange or at K&S Creations.

Qubius Quinn

Hello, my name is Qubius Quinn. Thank you for visiting my blog. I am a resident of second life currently living at a friends establishment in Lebeau. My birthdays was June 5, 2005 although I didn't become a second life permanent citizen until June 13. I am extremely gratefully to Kento Dion and sunceray Jacques of K&S creations for there hospitality, companionship, and teaching me many things about second life. In my short time as a second life citizen I have spent most of it learning Linden script. I'm really enjoying the power it gives me to manipulate my environment. I hope that by developing in SL I can provide something useful to the second life world. Be sure to return to this blog for updates on my development as an expert Linden scripter or stop by K&S creations to see what is going on or just to say hi.