GetTextures and GetMesh are guaranteed to serve only textures and mesh.
But yes, if those are meant to be protected, then something needs to
protect them.
We never really finished the CAP mechanism properly in core, because the
default configuration doesn't need the extra protocol. That would be
nice to have in core.
On 8/17/2019 11:32 AM, Mike Dickson wrote:
Agreed on the security. It’s not useable in a commercial setting as is. In
Halcyon we had a region module that created the CAP for avatars on the region
and pushed it to the shared server. Also removed it when the avatar left the
region. So you had some authentication happening and the actual cap handler
wasn’t wide open. As you said, using it as is opens assets to the world.
What makes the caps obsolete? What is replacing them?
MIke
Sent from Mail for Windows 10
From: Leal Duarte
Sent: Saturday, August 17, 2019 2:02 PM
To: opensim-dev@opensimulator.org
Subject: Re: [Opensim-dev] Packet Pooling - Should it work?
Hi,
GetTexture and GetMesh (and GetMesh2) are in the path to be obsolete.
If you bypass the simulator as provider data as assets, then it is
your job to provide proper access authorization on the replacement provider.
To expose Robust assets to viewers is expose all assets to world.
Regards,
Ubit
On 16-Aug-19 23:31, Diva Canto wrote:
GetTexture and GetMesh
...
_______________________________________________
Opensim-dev mailing list
Opensim-dev@opensimulator.org
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
Opensim-dev@opensimulator.org
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
Opensim-dev@opensimulator.org
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
