[BUG-11839] LSL - llAttachToAvatarTemp fails when item is "No Transfer"

[sl-service-account]

Steps to Reproduce

Testing the drink dispenser

Actual Behavior

Tried to make a drink dispenser item using llAttachToAvatarTemp function.

Expected Behavior

I was expecting the drink dispenser item to be able to be transferred, with the drink itself using llAttachToAvatarTemp to actually attach to a third avatar.

Other information

Many mesh maker's TOS forbid sending final products out using their kits in both a copy AND transfer state. This hampers LEGITIMATE use of said kits for food/drink dispenser purposes.

Temporarily attaching is NOT a full transfer from one avatar to another - why is this being limited by transfer perms?

Links

Related

• [ ] https://github.com/secondlife/jira-archive/issues/2738

Original Jira Fields

| Field | Value | | ------------- | ------------- | | Issue | BUG-11839 | | Summary | LSL - llAttachToAvatarTemp fails when item is "No Transfer" | | Type | Bug | | Priority | Unset | | Status | Closed | | Resolution | Expected Behavior | | Reporter | Structura Finesmith (structura.finesmith) | | Created at | 2016-04-26T19:26:00Z | | Updated at | 2016-06-17T21:26:36Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2016-04-26T17:13:49.446-0500', "Is there anything you'd like to add?": "Many mesh maker's TOS forbid sending final products out using their kits in both a copy AND transfer state. This hampers LEGITIMATE use of said kits for food/drink dispenser purposes. \r\n\r\nTemporarily attaching is NOT a full transfer from one avatar to another - why is this being limited by transfer perms? \r\n\r\n\r\n", 'ReOpened Count': 0.0, 'Severity': 'Unset', 'System': 'SL Simulator', 'Target Viewer Version': 'viewer-development', 'What just happened?': 'Tried to make a drink dispenser item using llAttachToAvatarTemp function. ', 'What were you doing when it happened?': 'Testing the drink dispenser', 'What were you expecting to happen instead?': 'I was expecting the drink dispenser item to be able to be transferred, with the drink itself using llAttachToAvatarTemp to actually attach to a third avatar. ', } ```

[sl-service-account]

ObviousAltIsObvious commented at 2016-04-26T22:13:49Z

If BUG-7702 is still possible, then this behavior may be desired for the time being.

[sl-service-account]

Whirly Fizzle commented at 2016-04-26T23:02:12Z

I guess this should be a feature request?

I'm not sure this is a good idea though. Is the block on being able to drop a temp attachment viewer side only? If it is, this would be a really easy way to transfer no transfer objects (or no transfer anything in object contents) to another avatar.

[sl-service-account]

Structura Finesmith commented at 2016-04-26T23:23:42Z

Whirly,

This NOT referencing the drop of an attachment. Rather, this refuses to temporarily attach AT ALL.

ObviousAlt,

I cannot see BUG-7702, how about a summary of the contents?

[sl-service-account]

Structura Finesmith commented at 2016-04-27T00:20:26Z

I haven't been able to "drop" a mesh attachment when it's worn anyway, in addition to any block for dropping temp attached items.

[sl-service-account]

Whirly Fizzle commented at 2016-04-27T02:08:13Z

BUG-7702 is: When llAttachToAvatarTemp fails to attach (due to all slots occupied or some other reason) the prim stays rezzed as owned by the target owner. If the attachment was no transfer (your request), the target owner can easily pick up the attachment & circumvent permissions.

[sl-service-account]

ObviousAltIsObvious commented at 2016-04-27T05:35:12Z

Yse, that's my worry. The rezzed object transfers ownership for real, and the limited-capability attachment is a separate second step that can fail. I suspect that even if BUG-7702 were fixable, and even if the drop prevention were bulletproof, there would still be a race condition where an avatar could possibly grab the rezzed object between when it's transferred and attached.

[sl-service-account]

Lucia Nightfire commented at 2016-04-27T06:43:05Z

Also, when server version 16.04.21.314319 is released, BUG-7702 will be even easier to achieve.

[sl-service-account]

Strife Onizuka commented at 2016-04-30T20:15:38Z

This is likely being limited because you could otherwise follow the following steps:

1. Stick an item you have no-transfer ability in an box.
2. Insert a script that gives contents of box to owner.
3. Temp attach box to 3rd party.
4. 3rd party activates script to give themselves the no-transfer item.

Basically you could use this to sell items you don't have the transfer rights to sell.

[sl-service-account]

Dan Linden commented at 2016-05-02T17:10:45Z

The current behavior is the Expected Behavior.

Thank you.