[#SVC-1366] Group owned object on havok 4 sim changed owner to group member with insufficient perms to move or change said object.

2. Second Life Service - SVC

Group owned object on havok 4 sim changed owner to group member with insufficient perms to move or change said object.

Created: 30/Jan/08 03:02 PM Updated: 31/Jan/08 11:21 PM

Return to search

Component/s:

Physics

Affects Version/s:

Havok4 Beta

Fix Version/s:

None

File Attachments:

None

Image Attachments:

1. h4_memberpermissions_properownership.png
(486 kB)

2. h4_ownerChange.png
(712 kB)

Environment:

« Hide

You are at 277743.1, 289158.3, 27.9 in FurNation Phoenix located at sim5674.agni.lindenlab.com (8.2.34.230:13006)
Havok4 Beta Server 1.18.6.78103

Issue Links:

Relates

This issue Relates to:

~~SVC-121~~ Share with group does not respect Role Limitation

SVC-585 Use same group policy for group-owned and group-shared objects

Linden Lab Issue ID:

DEV-9742

Description

« Hide

A normal member of the Furnation Ponyclub group tried to delete a texture she thought to be a picture off a building that was deeded to the group.

As a normal member she has no rights to move/change or delete said object.

The building vanished for a couple seconds only to reappear in a different location (couple meters away).

We checked the reappeared structure and found it had changed ownership to the normal member instead of its proper owner or the group.

The location is:
FurNation Phoenix/239/134/27

The first picture shows the object that changed owner
the second picture shows the proper object ownership as it should have been as well as the members permissions in the group.

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Sidewinder Linden added a comment - 30/Jan/08 04:24 PM

Is it possible that the member had priv's to take the whole building into inventory, and then put it back? (Trying to figure out if there is any reproducible sequence that might trigger this, either as a bug or expected behavior...)

[ Permlink | « Hide ]

Squirrel Wood added a comment - 30/Jan/08 05:08 PM

That can be definitely excluded. The member does not have permissions to do that.

They are just in the everyone role which has only the listed permissions (see screenshot).

[ Permlink | « Hide ]

Squirrel Wood added a comment - 30/Jan/08 05:13 PM

I am still able as an officer of the group to move / resize / edit the object so it may still be owned by the group but it definitely shows that member as owner.

[ Permlink | « Hide ]

Harleen Gretzky added a comment - 30/Jan/08 08:39 PM - edited

I was able to easily reproduce this with one exception, using Take instead of Delete. Delete always returned the object to the last owner's Lost and Found. Didn't matter whether it was Havok 4 or Havok 1. The key is the "Share with Group" flag. To reproduce:

Create an object.
Set it to full perms.
Deed the object to group.
Re-check the Share with Group box.
Normal member can move object.
Normal member Right-clicks and Takes the object.
Normal member rezzes the object and now is the new owner.

If the "Share with Group" box is not checked, the normal member cannot move, take or delete the object.

[ Permlink | « Hide ]

Harleen Gretzky added a comment - 31/Jan/08 02:04 PM

Resolving, don't believe this is a bug, as far as I know this is way the "Share with Group" tag is supposed to work.

[ Permlink | « Hide ]

Squirrel Wood added a comment - 31/Jan/08 10:29 PM

If someone can take your items as their own without you putting said item for sale or giving it away then it IS a bug.

This is neither resolved nor misfiled.

Also I advise you to check on the status of issues before going and resolving them.

[ Permlink | « Hide ]

Harleen Gretzky added a comment - 31/Jan/08 10:34 PM - edited

Not if it is the intended behavior of "Share with Group".

And it is not even a Havok 4 only issue.

Just because it is being worked on doesn't mean that if it is discovered not to be an issue it should not be resolved. Marking something as resolved, is sending it back to the OP (you) to reopen or close, nothing more.

[ Permlink | « Hide ]

Harleen Gretzky added a comment - 31/Jan/08 10:48 PM

This is by design see ~~SVC-121~~. Please see SVC-585 for more information, or if you wish to change this behavior.

[ Permlink | « Hide ]

Andrew Linden added a comment - 31/Jan/08 11:09 PM

Squrrel, could you please double check to make sure the objects in question are NOT using the "share with group" bit? If the bit is set we'll leave this bug closed, otherwise please open it up again with a "repro recipe" (a simple set of instructions on how to reproduce the bug for a fresh object) such as the one above.

I would love to NOT have to tackle this "bug", since I don't know the group perms system very well, but if it is real then I would consider it high priority and will figure it out.

[ Permlink | « Hide ]

Harleen Gretzky added a comment - 31/Jan/08 11:17 PM

You can see it still checked in the second picture.

[ Permlink | « Hide ]

Andrew Linden added a comment - 31/Jan/08 11:21 PM

Ok thanks Harleen. Let's leave this one closed. The perms system is confusing, but I think this behavior agrees with that of the "share with group" bit.