I am familiar with the existing permissions methods and the definite inherent risks of user modifiable and deployable scripted objects and scenes, and have been seeking a method to deter potential dangers for a long time now, since August 2007 at least.
In one post at the caligari forum, a thread and post by Wigand, at the following link http://forums1.caligari.com/truespace/s ... php?t=4221 SEE POST 5
Wigand said:
now...I would suggest something like a certificate.
Maybe something like encrypted :
* TS serial number/Username
* MAC adress
* unique key number of the object
Every created object should get these numbers
encrypted by Ts, programmed by the caligari developers.
And if objects are uploaded to shared space
they should pass through a certification process.
It is also possible to scan the objects for
file access scripts or dll call to classify their
riskiness.
we no longer have the potential of getting the official corporate Devs to do this for us since there is no more official development, but we do have our own capabilities to do this by thinking and working and innovating "outside the box" as usual on it in a focused collaborative way over however many months it may take to achieve an effective breakthrough for us all to utilize online.
This quote of Wigand here is ripe with potential on direct ways to absolutely control all these issues. I just wanted to point this out and also suggest each of us download every page and file in that thread for future reference in this effort. I already have.
However long it takes us to achieve a breakthrough in securing our online scenes, objects, and servers, we can do it together, and I believe the right direction for the focus is here in Wigand's remarks.