[Potential for UUID ripping from system layers and consequent use with appliers]

4 hours ago, Drake1 Nightfire said:

You realize that every texture you have ever seen in SL is stored on your computer, right?

Oh please, you know perfectly well that there's a difference between needing an external tool and patience to spot the one texture you're hunting for, and dropping a script in a prim and clicking it. Don't act like those two scenarios are even close to similar. That's BS and you know it.

It's blindingly obvious that SL should not include the tools needed to break its own permission system.

[Potential for UUID ripping from system layers and consequent use with appliers]

I explained what I wanted to see change: A way to find out an object's "true" non-inherited permissions by script.

The reason for this is the way that llGetTexture(face) works. It will return a valid UUID as long as the script is in a full-perm object.

[Potential for UUID ripping from system layers and consequent use with appliers]

Here's a quick example of how linkset mechanics work in SL:

Those that understand the significance of this will know why this is very bad. This also means that ANY omega-compatible mesh that happens to be mod is vulnerable.

It should be pointed out that there is NO way via LSL to distinguish between a "really" no-trans object and a "temporarily" no-trans object.

To solve this, LL needs to do two things: Add an llGetLinkPermMask(category) function, and add an extra category that stores the unlinked permissions.

EDIT: Without naming names, it does indeed work on mod meshes that are omega enabled. Meaning it's possible for much less than 999L$. I'd like for LL to fix this.

[Potential for UUID ripping from system layers and consequent use with appliers]

On 5/1/2018 at 4:00 PM, Blush Bravin said:

I stopped including system layers with my appliers because it was brought to my attention how easy it is to rip the UUID numbers of any worn system layer. So my question is if this project goes forward with an applier system in place what safeguards will there be to prevent use of a UUID# without actually owning the texture to make appliers?

You are aware that Omega literally sells the tools needed to copy UUIDs on their own marketplace store for L$999, right? https://marketplace.secondlife.com/p/LNL-Mesh-Maker-Dev-Kit/6525668

While it isn't intended for that use, it can be used for it because of how SL treats linkset permissions.