I'm trying to think of a use case when I wanted a PARCEL_OWNER to have privileges that the ESTATE_MANAGER did/should not have and can't think of one off the top of my head. In every scenario I can think of where I assigned an Estate Manager through the Estate tools rather than using group permissions, it was because I expected them to have MORE permissions than the parcel owners and was setting that explicitly.<div>
<br></div><div>Having said that, I do agree with Melanie that I would not expect a permission change on PARCEL_OWNER to affect the permissions for ESTATE_MANAGER. Generally I think of permissions inheriting "down" the hierarchy, not "up", and I'm not sure the average grid owner would expect that kind of behavior.</div>
<div><br></div><div>- Chris/Fleep</div><div><br></div><div>Chris M. Collins (SL/OS: Fleep Tuque)</div><div>Center for Simulations & Virtual Environments Research (UCSIM)</div><div>UCIT Instructional & Research Computing</div>
<div>University of Cincinnati</div><div>406A Zimmer Hall</div><div>315 College Drive</div><div>PO BOX 210088</div><div>Cincinnati, OH 45221-0088</div><div><a href="mailto:chris.collins@uc.edu">chris.collins@uc.edu</a></div>
<div>(513) 556-3018</div><div><br></div><div><a href="http://ucsim.uc.edu">http://ucsim.uc.edu</a><br><br><div class="gmail_quote">On Fri, Apr 13, 2012 at 9:02 AM, Melanie <span dir="ltr"><<a href="mailto:melanie@t-data.com">melanie@t-data.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Not true.<br>
<br>
Even in SL estate owners/managers don't have some parcel rights. If<br>
I specify parcel owner, i expect parcel owner. Maybe a way needs to<br>
be found to combine multiple strings, e.g.<br>
ESTATE_MANAGER,PARCEL_OWNER. That would be acceptable. Changing the<br>
current behavior that people already depend on to relax security is<br>
not acceptable. It may mean that someone suddenly can do something<br>
they could not do before and the owners may not be aware of this,<br>
causing issues.<br>
<br>
Also, in case of a group owned parcel, group permissions govern what<br>
people in the group can do. Group members are by no means owners,<br>
often parcels are deeded only for access control but normal members<br>
have no rights whatsoever. Giving them potentially dangerous<br>
functions is not an option.<br>
<br>
On group owned parcels, those functions can be allowed either to<br>
group owners only (the group invite functions already do this check)<br>
or to deeded prims only. Allowing them for every member of the group<br>
is really bad. You don't really want to have your roleplay's members<br>
osTeleportAgent the opponents out of the fight!<br>
<br>
Again, relaxing existing constraints is not an option, but as you<br>
can see above, ways can be found to define combinations of<br>
permissions to allow more flexibility.<br>
<span class="HOEnZb"><font color="#888888"><br>
Melanie<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On 13/04/2012 14:42, Oren Hurvitz wrote:<br>
> The decision whether to allow the parcel owner to call a function or not is<br>
> set by whoever setup OpenSim.ini: they can choose to allow PARCEL_OWNER, or<br>
> only ESTATE_OWNER. If they decided to allow the PARCEL_OWNER then we should<br>
> also allow the estate manager/owner to call that function. In addition, in<br>
> the case of a group-owned parcel, all members of the group are owners.<br>
><br>
> So this change doesn't allow more permissions: it would only correct the<br>
> implementation of the existing permissions system, when PARCEL_OWNER has<br>
> been specified.<br>
><br>
> --<br>
> View this message in context: <a href="http://opensim-dev.2196679.n2.nabble.com/Remove-check-for-IsGod-in-some-OSSL-functions-tp7462127p7462567.html" target="_blank">http://opensim-dev.2196679.n2.nabble.com/Remove-check-for-IsGod-in-some-OSSL-functions-tp7462127p7462567.html</a><br>
> Sent from the opensim-dev mailing list archive at Nabble.com.<br>
> _______________________________________________<br>
> Opensim-dev mailing list<br>
> <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
> <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
><br>
><br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
</div></div></blockquote></div><br></div>