aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/OpenSim/Region (follow)
Commit message (Collapse)AuthorAgeFilesLines
* replace calls to SOG.GetEffectivePermissions() by the new ↵UbitUmarov2017-01-224-5/+5
| | | | SOG.EffectiveOwnerPerms, some of those inline permissions checks should be reviewed and pass by permissions module
* don't let part lastowner be the groupUbitUmarov2017-01-221-2/+2
|
* share before groupr roles was a testing elsewhere induced mistake, clean it upUbitUmarov2017-01-221-46/+36
|
* work around group sharing and owned permitions issues, fix a non copy ↵UbitUmarov2017-01-224-89/+214
| | | | objects delete issue
* a few more changes on permissionsUbitUmarov2017-01-211-51/+47
|
* fix CanReturnObjectsUbitUmarov2017-01-211-13/+20
|
* add/fix CanRunScriptUbitUmarov2017-01-213-5/+53
|
* fix llScriptDanger(); don't call old ScriptDamage on ossl health functionsUbitUmarov2017-01-213-52/+47
|
* fix CanObjectEntry and CanTerraformLand group permissionsUbitUmarov2017-01-211-33/+30
|
* change the initialization point of SimwideAreaUbitUmarov2017-01-212-4/+6
|
* initialize SimwideAreaUbitUmarov2017-01-211-1/+3
|
* Oops.. fix the null on the correct place.. jenkis may now fail for another ↵UbitUmarov2017-01-211-2/+3
| | | | reason
* fix a null ref on jenkinsUbitUmarov2017-01-201-6/+4
|
* test jenkinsUbitUmarov2017-01-201-4/+4
|
* change CanObjectEntry() to use a SOGUbitUmarov2017-01-207-51/+40
|
* remove redundant IsGod, rename some GOD as Administrator (both only on ↵UbitUmarov2017-01-202-118/+65
| | | | permissions module)
* change CanDuplicateObjectUbitUmarov2017-01-194-14/+19
|
* actually make use of it as viewers requestedUbitUmarov2017-01-191-6/+1
|
* fix the meaning of objectDuplicate[OnRay]() flags parameter but still not ↵UbitUmarov2017-01-195-9/+13
| | | | using it
* change CanDeedObject. WARNING like on other grids, if you do not set next ↵UbitUmarov2017-01-193-24/+41
| | | | owner rights on object and ALL ITS CONTENTS, you may loose all rights on it
* add a comment about parts permissions aggregationUbitUmarov2017-01-191-0/+2
|
* add CanEdit check for SOGs, iclients and SPs that need to be in scene and use itUbitUmarov2017-01-193-21/+60
|
* fix a null checkUbitUmarov2017-01-191-2/+3
|
* object CanMove is for in scene SOGs Icleints and SPs and permitions module ↵UbitUmarov2017-01-195-81/+57
| | | | is NOT a shared module
* object Take and TakeCopy are for in scene SOPs and SPs and permitions module ↵UbitUmarov2017-01-195-25/+35
| | | | is NOT a shared module
* a few more aux methods and changesUbitUmarov2017-01-191-152/+133
|
* add a GetItemPermissions() to be used use on object contents checks in ↵UbitUmarov2017-01-191-16/+83
| | | | Permissions module
* a few more changes on Permissions moduleUbitUmarov2017-01-181-90/+80
|
* enforce effective perms hierarchyUbitUmarov2017-01-181-42/+59
|
* antecipate baked cache check and Xbakes requests, so they happen before ↵UbitUmarov2017-01-181-26/+33
| | | | viewer check request (or force it to wait via locking).
* Permissions module: fix in prim inv CanEditNotecard group edit rights check ↵UbitUmarov2017-01-181-3/+17
| | | | ( in last commit plz read .. by GetObjectPermissions)
* Permissions module: replace some GenericObjectPermission by ↵UbitUmarov2017-01-181-123/+51
| | | | GenericObjectPermission on some checks. Note that in some cases behavour is now diferent.
* Permissions module: GenerateClientFlags() no need to keep looking for the ↵UbitUmarov2017-01-174-77/+70
| | | | same part several times; fix locked mask in GetObjectPermissions()
* Permissions module: add GetObjectPermissions() that should replace ↵UbitUmarov2017-01-171-1/+77
| | | | GenericObjectPermission
* add more calls to effective permissions aggregation, some paths may still be ↵UbitUmarov2017-01-1714-30/+58
| | | | missing on objects changes, but remove the aggregation on check paths, so all can be tested.
* add more calls to effective permissions aggregation; do not change groupmask ↵UbitUmarov2017-01-174-2/+15
| | | | on deed
* start adding calls to effective permissions aggregation on changes; ↵UbitUmarov2017-01-175-36/+29
| | | | rearrange code in DuplicateObject();
* remove now unused SetRootPartOwner()UbitUmarov2017-01-161-21/+1
|
* replace calls to SetOwnerId and SetRootPartOwner by a single new SetOwner() ↵UbitUmarov2017-01-164-6/+27
| | | | so owner is not changed twice on rootpart
* fix EffectiveGroupOrEveryOnePerms C&T == 0 caseUbitUmarov2017-01-161-5/+27
|
* avoid lastOwner beeing the groupUbitUmarov2017-01-163-4/+11
|
* chance new effective permissions code to ease aggregation on demand( ie on ↵UbitUmarov2017-01-164-149/+121
| | | | changes). But still doing full aggregation on checks, so still heavy
* Merge branch 'melanie'Melanie Thielker2017-01-163-7/+9
|\
| * Remove the last instance of the legacy slam but being setMelanie Thielker2017-01-163-7/+9
| | | | | | | | New objects now get only the real slam bit.
* | add code for fixing effective permitions. This is a test, and currently too ↵UbitUmarov2017-01-154-15/+252
|/ | | | slow for prodution. just finding our way home
* bad move.. revertUbitUmarov2017-01-141-11/+5
|
* permissions GenerateClientFlags() also needs group GetEffectivePermissions() ↵UbitUmarov2017-01-141-5/+11
| | | | for the everyone case. Current naive uncached GetEffectivePermissions() must be improved since its now a lot more used.
* fix incoerent definition of Slam bit (bits 3 and 4 used in diferentUbitUmarov2017-01-143-8/+8
| | | | | places.) this may still be wrong on other places; Do not loose folded permitions, WARNING MASTER IS NOW UNSTABLE. permissions are still broken"
* fix: send viewers the Everyone permitions of items inside other objectsUbitUmarov2017-01-141-1/+1
|
* Fix the new permissions error introduced with the inventory fixMelanie Thielker2017-01-132-17/+46
| | | | | | | | | The fix to allow setting perms in inventory accidentally caused folded permissions to be used as a mask for the next owner perms. The current solution isn't optimal but better than anything else we have had. Legacy objects may experience a net loss of permissions if trying to set their perms in inventory, this is deemed preferable to the prior privilege escalation possibility. New items will handle properly.