New permission behavior

Close Codi but still slightly off in the respect that even if you obtain an object from the orginal creator that is full perms because the orginal linked subset has changed ownership once you cannot circumvent the orginal transfering permission set.

Example

Item A has been given to you its perms are No Copy No Transfer and was given to you by Creator Z

Now Creator Z gives you a single prim B that has Full mods on it.

Just because you have those both created by Creator Z you cannot take Prim B and Link it to Item A and force the permissions to change through out Item A to match Prim B.

Make Sense?

Shadow

yup I hadn't even thought of the possible loop hole you just described lol. So a better way to word it would be....

You cannot reset the permissions (to be more permissive) of an object by linking it to a new root prim (more permissive), if the original object (soon to be child prims) was not created by the av performing the operation

They Closed a Loop Hole that My partner and I found by accident. We reported it immediately and showed them how it was created.

This fix apparently is based on the extensive information we gave them through an accidental combined build she and I worked on.

The information I gave you in the last two threads were based on a Phone Call I made to support explaining the assumptions we were all making here.

Simply put the wording of the fix notes does not accuratly relay what exactly the fix does. Trying to put this sort of explination in a bullit coment on a release note is rather akward at best so even I was confused initially by its statment.

Hope this helps and I hope a Linden will Step foward and back up this information as per how I understood it on the phone.

Sincerely, Shadow Weaver

Bumping ....

Guilty as charged Shadow is a Bumper.. better than a bonker..

Shadow, thanks for reporting what you found quickly and quietly to LL.

LL, thank you for taking fast deliberate steps to close any permissions loopholes that your residents find.

Thanks for clearing that up Shadow

Thank you.

I appreciate the Sentiment everyone is expressing in this however, I must outline the Key members for getting this Loop hole sowed up from where I see it.

Pahoa and I Found it while building a fountain containing multiple owner permissions Prims.

When I went to pass it to Pahoa it passed with ease and she says " um I thought those prims were no Transfer" < I Said " yeah your right lemme check this" pulled it from inventory and found that all the permissions had been circumvented to include the creator name.

At that point since it was so recent as in minutes that she and I had created the fountain we back traced every step we took to recreate the incident. ( No I will not lay out the steps)

Through that method we were effectively able to recreate the loop hole.

Immediately we called in Jill Linden showed her and she turned it in as a bug for us.

Following that Dan Linden contacted me but I was sick for a week and was unable to meet with him.

Then from the time Dan took down the info to this patch was about 9 days to get the bug fixed so I am happy to say for those that dont think LL is busting thier ass they pretty well showed me by this just how much they really do care by reacting so quickly on this.

So for the Bug Team and those that worked on this fix at LL I thank you.

Sincerely, Shadow Weaver

Thank you LL for fixing this bug and making us content creators feel a bit more safer about the permissions.

Shadow, have you tried recreating any other permission test to make sure that there aren't any bugs. I have been meaning to do this (by using my boyfriend's account), but I keep procrastinating.

I would like to take this time and nominate Shadow Weaver for Linden of the month!
Thank you so much Shadow, I admire your patience and ability to explain things and help the community also your knowledge to so many different topics. *hugs*

Actually Kats I tinkered with this one again to be sure but I still have one phase of it that I have to consort with my partner on.

For the most part Textures seem to be safe at the moment due to how they fixed that a while back but Textures will never be totaly safe with the Ctrl+PrintScreen Buttons available because unfortunately there is no real way to disable them except through the client and doing that would also prevent screen shots as well. Soooo...

I still think the permissions thing needs an overhaul but there are so many opportunities for abuse even with an overhaul its scary. Whats even worse is if you make it to intensive to set up permissions. Things are going to get screwed up because people will forget this or forget that and boom we have stuff that got away from us. But thats a whole new topic entirely.

Shadow

OK, Translate..Does that mean any one can buy a object and put a alpha prim as the parent prim and resell, copy and resell your orginal no mod/no copy hard work?

Polly no, if you buy an object from the owner that objects perms are then set.

Adding prims whether it be yours or theirs with full modificatons will not change that as the intial permissions were set the moment it left the creators hands.


Shadow

I haven't experimented with the permissions in a long time, but it would help if the Select Texture menu wouldn't stretch out, allowing for people to select the texture, stretching it and taking a snapshot using "Prt Scrn". Also, the way that textures pop up on the screen when taken out of an object (even when the permissions were set to no mod/no copy) doesn't help the texture theft situation.