Ubit would you care to clarifiy 
" ( the C# scripts was a example i just had to kill ) "
Its true that in official release 090 C# as XENGINE scripting language did not 
compile anymore . 

But I notice that  in release 0901 C# compiling / running  was allowed again .  

Opensing C# as scripting source has high threat level as it give access to all 
system functions. I have tested and validated that in opensim 0901 one way to 
limit the threat is to assign a unique user as able to run such script by 
populating the [Startup] section of opensim.ini with the GrantCS = UUID in the 
same principle as high threat level OSL scripts can be granted  per owner UUID 
. Using that restriction  I have observed that when a C# script is allowed  in 
XENGINE ini and run by a owner not GrantCS listed, will  compile with error and 
fail to save.
I think, that the XENGINE section of opensim.ini is a cleaver way to give the 
simulator server operator all the tooling to customize the osl features and 
control the risk level he is willing to allow in his server for his land owners 
. 

You bringing an interesting point when you mention that one script allowed by 
one simulator system operator might have impact on more then the simulator 
server where it is run . But is it not the case of opensim itself as a 
distributed system where grid server and simulator server are operated by 
different party. Unless we all fall back to standalone where asset and 
simulator reside on same system  the example provided  about notecard  and  
llGetNotecardLine(..) is only one example of many and will be true for all open 
grids where simulator connection is accepted. 

The beauty of opensim is freedom of choice. There is already  a second choice  
for the others.

GiMiSa 

    Le jeudi 17 octobre 2019 11 h 10 min 10 s UTC−4, Leal Duarte 
<ajldua...@sapo.pt> a écrit :  
 
 Well lets try put some perspective on this...

The problem is not how hard it is to detected and handle disabled functions

The problem is WHY are you using them !!!

See OSSL got a lot a functions in time and for very different reasons.

Many are there because they are just funny/useful on very specific 
regions or cases.

Once the allow control was introduced, that got worse, because as dev in 
can just not care, i just flag a specious feature as SEVERE, 
ESTATE_OWNER only. And just let you change it and shoot your own feet, 
or worse someone else feet...

And in many cases you are just doing that. ( the C# scripts was a 
example i just had to kill )

see a very simple and useful(?) example

osGetNotecardLine(..)

none of that Dataserv mess of llGetNotecardLine(..) right?

well wrong.. Dataservice is need because the notecard may be on a assets 
server on the other side of the world...

and not using it will stall the engine thread, potentially all of then.

Why do i see its  errors at osgrid LBSA ?

A lot more examples, but you got the point.

When one writes a script, one must take in consideration its target 
audience..

you can't use osSlerp()  if you want it to run at current Kitely, can you?

So issue is to identify a set that should be universally supported, and 
everyone make the effort to support it.

...

Ubit


On 17-Oct-19 15:17, dz wrote:
......
_______________________________________________
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

Reply via email to