[Opensim-dev] Opensim-dev Digest, Vol 13, Issue 2

Fred Beckhusen fred at mitsi.com
Fri Apr 10 17:23:28 UTC 2015


I would love to see these documented in a separate INI file.   The 'wall 
of text' we have now in this section without a working example is an 
invitation to toggle it to "Severe".   Which I have always done, in 
spite of the risks, because  I need NPCs and the suggested configuration 
has never worked for me in spite of numerous attempts to get it to work.

Mister Blues suggestion jogged me into digging deeper.    The list in 
the post is incorrect;  it is case sensitive.   The correct camel case is :

     Allow_osGetAgents =  ...

and not

     Allow_OsGetAgents = ...

Also, the list as posted previously is incomplete, as it is missing 
Allow_osNpcMoveToTarget, and the wiki for this at 
http://opensimulator.org/wiki/OSSL_Enabling_Functions is missing many 
functions.
=====================
Here is another way to manipulate ossL Allow* for grid ops that need to 
allow ossl functions by person:

I added a series of UUIDs like this to [Const]

;; Use this for my UUID:
     ;; ${Const|GridOwner}
     GridOwner = "6f285c43-e656-42d9-b0e9-a78684fee15a"
     Debbie = "another UUID"
     Su = "another UUID"

and I use it like this:

DefaultEstateOwnerUUID = ${Const|GridOwner}

or this:

Allow_osGetAgents = ${Const|GridOwner}, ${Const|Debbie}, ${Const|Su}
...

================================
Reasons to support Mister Blue:

We should strongly discourage overriding the global threat level as it 
is serious security risk.    The only way to do this now is to enable 
them individually, so we need a documented list.

The  above case sensitive issue will be fixed by making a list in the 
INI and checking it into git so it can be maintained.

As new ossl functions are added, they can be added to the 
Opensim.ini.example (or the new INI file) so nothing is ever missing.

gridOps will be exposed to and new ossl commands that may pose a risk 
automatically when the Op updates and compares INI files.

Any missing entry can break useful content.

I would also suggest we look at creating a new INI with all override 
variables.  Digging through source code to find a variable that can be 
changed to tweak things is beyond most scripters or Ops ability. 
Documenting these in an INI file can thus expose some of the more 
awesome tweaks to scripters, and is a good place to indicate when one 
may be deprecated.

--ooo------/\/\/\-----|(------ooo------/\/\/\-----|(------ooo----
Fred K. Beckhusen / Ferd Frederix
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20150410/6d775676/attachment.html>


More information about the Opensim-dev mailing list