Object Permissions

Lately I've seen stuff crop up about "changing permissions". Tonight, with eltee's help, I think I narrowed down the cause and filed a bug report about it. Post here is for some discussion and a longer-winded bit of info than in my bug report.

Basically when you set permissions on an object in inventory, they don't mean a thing.

Reproduction steps:

1. Create a prim
   
2. Take the prim
   
3. Right-click in inventory, and view Properties
   
4. Set some permissions. Whatever you want.
   
5. Drop the prim, view permissions via edit panel.
   [/list=1]
   
   You'll notice that the in-world version of your prim has different permissions than the in-inventory one. Note that this doesn't seem to affect textures, scripts, etc.. only Objects.
   
   So that's good, we know now to only set object permissions in-world, and you'll be safe. But why do they change?
   
   It seems that if you set permissions in inventory, and then give that to someone, the "true permissions" (those shown in-world, in the repro) don't appear until it goes in-world or is used in an outfit. (Something to do with UUIDs, I bet). Note that if you attach the object with "false permissions" it will not reveal the true ones, as the system doesn't seem to count that as going in world. You can test this by giving a copy of the prim for the repro steps to someone, and asking what they see for permissions a) when they first receive it, b) when they drop it on the ground, and c) when they pick it up again. A should differ from B & C which should be the same.
   
   Moral of the story: Do NOT set object permissions in inventory until this is fixed. ALWAYS set them in-world.

I saw a bug with a no transfer item. The original is okay to copy, but not transfer. But, when I "take" the original I had drug out of inventory, I then have the original and the "copy" I took. The copy could then be given away. That copy I gave away had no permissions set once received.

I dont really mess with permissions that much, but something is definately broken and needs to be investigated.

that about all sums it up what cie said... the unfortunate thing is *not* knowing about it up till now has made it very difficult to collaborate on multi-person build projects, especially ones with additional scripts with differeng permissions as well becaue seeminlgy randomly stuff would just start locking or unlocking...

we have an example of something with 'triple' owners (worked on by three seperate people, myself for scripting, and michi and arito for linking and design) that even a linden wasn't able to properly restore anymore.

The moral really is until they fix inventory permissions *NEVER* change things in the inventory.. if you made something and ever want to give it to someone else. *DROP* it in world to set the permissions, then pick it back up and hand it to them

I have a set of wings that are no-mod, but if I rez a copy then pick the copy up, it comes back as no-mod no-copy =)

I think this might explain why some people say no-transfer can occasionally bug out and go back to allowing transfer,

This is unfortunately probably why a lot of people are too paranoid to sell their clothing as mod/copy/notrans.

This shouldn't apply to clothing, textures, scripts, sounds, or notecards. (Did I miss anything?) In my testing you can't ever have one of those actually in-world, it's rezed in the inventory of a dummy prim. Since they're always in an inventory, you don't have to worry about world vs. inventory permissions.

yeah it seems basically confined specifically to setting the permissions of 'in word' prim objects, when they are in inventory (which is unfortunately second-nature for alot of people, hence the large numbers of glitchouts)

Holy crap.
I think that is a sign of the flaky backend implimentation of permissions. Stuff like that always comes back to bite the devs in the butts sooner or later. I once had an encounter with a permissions glitch myself, I was working with someone to help align their house, when they gave me the copy of the house, they said that they gave me full permissions on it (and triple checked, to boot), however, the game wouldnt allow me to copy, modify, or transfer the given inventory.

==Chris

\


actually chris.. that *IS* this bug

they set permissions on it in their inventory instead of in world

you simply can't do that... it'll LOOK like its unlocked.. .but try'n do anything with it an you'll find out its not

They did both