Permissions badly broken in v1.9 ?!

Here are a number of problems with permissions that I just discovered:

1) Setting permissions for next owner on objects you created only get applied when set in world, and not from inventory.

2) When you set permissions on a rezzed object that you did not create, and then take it, the new permissions are applied to you as if you were given that object !

3) This one is SERIOUS: when setting an object full-perm and sending it to someone, it appears that scripts inside it are set full-perm, free to copy and shared for group, without explanation !

Can someone confirm this, or is it a weird interaction of my various acounts being granted mod rights on each other's objects ?

Yet one more I just remarked: when you are given a full-perm object which contains not-full-perm scripts, if you rez it then take it the object takes on the permissions of the script and you're screwed !

Hmm... that one seems to be the way that permissions were working for me before 1.9, though. For example, if I gave someone a full-permissions object that had a no-modify no-copy script in it... the moment they rezzed it, the object also became no-modify no-copy. :/

If it was full perms, surely you'd still have the original in your inventory, thus not as screwed as you think you were.

Scripts and other object in object always had there own rights..

You can set an object no mod, and then have fully open notecard in side, you cannot edit those as the object is no mod unless you can take them out...but then because no mod you cannot put back in..

So has always been that way. I always set my script permission, objects in object permission, then I set the main object permission as they are all seperate.

But in the end do add, you will see object in your inventory like object (no mod, no copy) (no transfer)...which means the object itself is no mod, no copy, transfer, but there is things inside that are no transfer, copy, mod..

So yes confusing, yes takes a few minutes before selling, etc, but have been that was for a long long time.

The way I've seen it happen is that the item shows the "worst" permissions available for anything inside it. However, SL only works this out when the object is rezzed; until that time it shows the permissions set on the top level object. (I suspect that items in inv are just stored as references to something, and the references to their contents aren't resolved until they're needed, ie, on rez.)

So.. drop a "no modify" script inside an object, and the object shows up as "no modify", but in fact you can still modify it. However, if you get given a modify-ok object with a no-modify script inside it, it shows up in inventory as modify-ok, until you rez it, when SL notices that it contains a no-modify script and therefore starts showing it as no-modify from then on, even if you pick it up again.

It gets even more confusing if you have a "no copy" script inside a "copy ok" object, because if that happens, when you rez it SL realises that the object as a whole should be "no copy", and then does a double-take: "hey, hang on, that means I need to take it out of their inventory or they'll be able to copy the script by rezzing copies of the object!"

And in my case, it suddendly made the whole 'top' object retrograde its permissions and I couldn't set it for sale anymore

I was used to the object staying modifiable, for example, even though it showed "no mod" in inventory.

Anyway, I found a workaround to my problem, by rezzing the object to give, and setting it for sale as original and buying it with the other account, as full perm, then moving it to its definitive selling place.

You can, you just have to rez it in-world to do it. This is purely an inventory user interface issue... it behaves as if the server doesn't send the whole permissions down to the client, it just sends a summary, and the client uses that summary to determine what it'll let you do. In-world where the whole object's visible to the client you don't have that problem.