Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0008437opensim[REGION] Scripting Enginepublic2018-12-31 08:022019-01-04 23:49
Reporterunregi 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Statuspatch includedResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0008437: Remove Threat Levels
DescriptionosslEnable.ini Permissions are enough, lol
(and those are already too tough.... i mean...osMessageObject restricted per default? Come on...)

Attached a Patch.
TagsNo tags attached.
Git Revision or version number
Run Mode Grid (1 Region per Sim)
Physics EngineBulletSim
EnvironmentMono / Linux64
Mono Version5.x
Viewer
Attached Filespatch file icon 0001-Remove-ThreatLevels.patch [^] (68,376 bytes) 2018-12-31 08:02 [Show Content]
jpg file icon no-fun.jpg [^] (54,932 bytes) 2018-12-31 08:03

- Relationships

-  Notes
(0033700)
BillBlight (developer)
2018-12-31 08:24

I'm going to say this is not going to happen .... (don't quote me but I doubt it)

The other thing and I'm just going to be blunt ..

If threat levels and OSSL are too hard, I just don't think you should be running opensimulator yourself at all ..
(0033701)
unregi (reporter)
2018-12-31 08:38

I counter this with the exact opposite statement:
If threat levels get relevant for you, i don't think you should be running opensimulator yourself at all.

The ThreatLevel just matters for functions that have no line in the osslEnable.ini, so if your setup isn't messed up, it will never be relevant for you.
(0033702)
BillBlight (developer)
2018-12-31 08:44

I'll counter with, you are right, for a specific case ..

BUT if you have simulators spread across 8 servers, you may not want to hand touch each one to adjust levels for individual functions, but you can change large groups of functions via threat levels without having to edit a bunch of lines in the osslEnable .ini, this is very useful when you have a lot of public sims where you want to blanket allow or disallow these functions.
(0033703)
unregi (reporter)
2018-12-31 08:59

If i would be grid owner, i wouldn't go through the hassle and delete Allow_os* lines from every osslEnable.ini just to be able to use the ThreatLevels, just to then encounter someone who needs osGetNotecard, which is VeryHigh, just like osForceAttachToOtherAvatarFromInventory...

Would this make my life really easier? Or isn't this prone for configuration mistakes?
Do we even know any real example of someone using ThreatLevels?
(0033712)
tglion (reporter)
2019-01-03 22:45
edited on: 2019-01-03 22:47

It seem there is a bug since one of the last master commits.
Thread level should have a lower priority than ossEnable.ini

But since the last update I get Thread-Level Script-Errors on osFunktion's that should allowed in ossEnable.ini
???

(0033713)
BillBlight (developer)
2019-01-03 22:47

Most likely you did not update your ini correctly, they are no longer configured in the xengine section they have their own OSSL section ..

I have seen nobody have OSSL perms issues when configured and included correctly ..

Usually what has happened is one has used the old config files rather than adapting the new ones as it is recommended .
(0033714)
tglion (reporter)
2019-01-03 22:54

Ok, thanks for the hint. I try to check that. I don't saw any warning hints on git commit comments for this ;-)
(0033715)
tglion (reporter)
2019-01-03 23:03

Mhhh... what is the correct section for this in which ini, or what is exactly changed, so i can migrate this on my grid-configuration correctly?
(0033716)
BillBlight (developer)
2019-01-03 23:15

Use the new osslEnable.ini that comes with master ..

And make sure you have


//
[OSSL]
    ;# {Include-osslEnable} {} {Include file for enabling and permissions for OSSL functions} {}
    ;; Optionally include file to enable OSSL functions and set permissions on who can use which.
    ;; If this INI file is not included, the OSSL functions are disabled.
    Include-osslEnable = "config-include/osslEnable.ini"
//
in your configs
(0033717)
tglion (reporter)
2019-01-03 23:42
edited on: 2019-01-03 23:42

OK, thanks. OK I have changed this. I don't found this entry in OpenSimDefaults.ini nor in my old OpenSim.ini :-(
But: This change does not work for me, I get the same Thread-Errors.
I can not simply put the original osslEnable.ini from master, because its much work on this, so I can only migrate or merge this ini.
I try a diff on it later, to see what exactly is changed...

(0033718)
tglion (reporter)
2019-01-04 23:49

latest master (fc4de64af430bee0ca316421cd286afa51753480) solved this for me, its all ok now :-)

- Issue History
Date Modified Username Field Change
2018-12-31 08:02 unregi New Issue
2018-12-31 08:02 unregi File Added: 0001-Remove-ThreatLevels.patch
2018-12-31 08:03 unregi File Added: no-fun.jpg
2018-12-31 08:18 unregi Status new => patch included
2018-12-31 08:24 BillBlight Note Added: 0033700
2018-12-31 08:38 unregi Note Added: 0033701
2018-12-31 08:44 BillBlight Note Added: 0033702
2018-12-31 08:59 unregi Note Added: 0033703
2019-01-03 22:45 tglion Note Added: 0033712
2019-01-03 22:47 tglion Note Edited: 0033712 View Revisions
2019-01-03 22:47 BillBlight Note Added: 0033713
2019-01-03 22:54 tglion Note Added: 0033714
2019-01-03 23:03 tglion Note Added: 0033715
2019-01-03 23:15 BillBlight Note Added: 0033716
2019-01-03 23:42 tglion Note Added: 0033717
2019-01-03 23:42 tglion Note Edited: 0033717 View Revisions
2019-01-04 23:49 tglion Note Added: 0033718


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker