Security Systems in SL and how they should be.

I'm sorry. I'm quite new to forums here, but I have a deep concern for the security in SL.

A friend expressed to me that the removal of the option to eject people from parcels might be considered. In my opinion, this is partially due to the poorly designed security systems that are currently existent in SL.

In my opinion, only a house should be secure. Only a business. These are the matters of concern. A security system should be able to detect if a person is inside of a house. It is my goal to renovate the securty in SL and hopefully, if this rumor is true, come to a "happy medium".

I have developed a system that does exactly this. My only concern is the removal of ejection, which would make my system obsolete in it's early stages. I hope someone has info on this topic, and are available to offer their opinion/advice.

*CDru

I suspect the eject/ban options are going to be around for a very long time unless anyone has heard otherwise?
Maybe there's a Geneva convention thing happening, some avatar rights activists don't even want to keep shooting and freezing intruders/griefers as an option.

Well I hope it doesn't get removed. Anyway, in order to help people in the development of future security systems, this should definitely be included for all systems, IMO.

A detected area or perimeter, which will allow the system to know if the person has crossed a defined, restricted area (such as a house, closed store, etc.).

In order to use these systems, please consider this information:
Note, this is solely a partial pseudocode so you can understand how such polygon systems work. I have designed this myself (not based on some script I was given), so I hope it helps others in their work.

//Perimeter Vars for a Cubic/Rectangular Bounding Box
float minXcoord = 1.5; float maxXcoord = 10.0;
float minYcoord = 2.3; float maxYcoord = 8.7;
float minZcoord =4.2; float maxZcoord = 6.6;

integer check(vector dpos){//Basically this checks if their coords are within the min/max ranges
if(dpos.x > minXcoord & dpos.x < maxXcoord) count += 1;
if(dpos.y > minYcoord & dpos.y < maxYcoord) count += 1;
if(dpos.z > minZcoord & dpos.z < maxZcoord) count += 1;
if(count != 3) return FALSE;
return TRUE;
}


sensor(integer ndet){integer a = 0;integer count = 0;list tmp = [];
vector dpos = llDetectedPos(a);key ky = llDetectedKey(0);
for(a=0;a<ndet;a++){
integer a = check(dpos);
if(a==TRUE);{tmp += llKey2Name(ky);//Lagless Msg to ejected then eject}
}
//IM Owner the list of people ejected if any. IM ejected persons as well, if you use a strided list containing their keys. Possibly use 2 separate IM handling scripts for lagless system.
}

This is off the top of my head. You may find flaws, but the point is to get the "how to" across. I have also discovered that this technique is possible with cylindrical perimeters as well. (For spherical coordinates, simple use "float dz = llFabs(dpos.z-mypos.z);" [see below])


For cylinders:

The check for perimeter (This checks if the difference between the person's x,y coords and the center of the cylinder is smaller than 50. If so, then they are within the cylinder of 50m. Note that the prim containing the security script needs an object in the center of the cylinder (or the coords) as a reference, if it is not in the center itself).

integer check(vector dpos){vector mypos = llGetPos();//Only if the prim is in the center of the cylinder.
float dx = llFabs(dpos.x-mypos.x);
float dy = llFabs(dpos.y-mypos.y);
float highrange;//this is for maxZcoord
float lowrange;//this is for minZcoord
if(dx < 50) count += 1;
if(dy < 50) count += 1;
if(dz > lowrange & dz < highrange) count += 1;
if(count != 3) return FALSE;
return TRUE;
}


This is about all I can think of at the moment. I hope it helps somewhat.

*CDru

Charliedru, you haven't yet realised that when people get annoyed with each other (we're all human!) quite how nasty a small minority of people can get in griefing the people they're upset with. This can extend to attempts to destroy _all_ their builds, not just a house; disrupt _all_ their activities (and the houses and activities of their friends).

If a person has just a single house or a shop to protect, your suggestion makes eminent sense, and there are several systems already around that can do this. Make a better one and I will take my hat off to you and drink to your success!

But if a person owns a large sim, or a whole island, they simply _can't_ protect each item separately as you suggest. Only a blanket ban of a known and repeatedly malevolent griefer, and the alts they create to carry on the harassment, has any effect.

And that's why the Lindens invented the BAN command in the My Land window.

Christi Maeterlinck

They can't realistically get rid of eject without providing better alternatives! It's already against the ToS (and thus ARable) to use obtrusive or unnecessarily aggressive security devices.

I have a device I scripted myself which I feel is quite a fair one, if someone on the owners list is available then instead of pestering visitors, a dialogue is shown to the owner who can choose what to do (allow once, allow forever, ban or warn), it presents different options if the person is actually on your land, or simply within eavesdropping distance (can hear your chat) so you are forewarned if someone might be listening in, not perfect but 99% useful. If no owners are about, then people on the allowed list are still able to hang about, but others will be warned they are trespassing, and are given between 1 and 2 minutes to leave (depending upon when they arrived versus the scanner's frequency).

I feel the above is a very fair system, and it is configurable to encompass only a specific area on your land (mine currently encompasses my entire land area with a limit on vertical height, as I am protecting a build in the air that takes up the full area of my land).

There are however alternative proposals that would make security devices redundant, and provide real privacy, you can find these linked to the following JIRA proposal:
http://jira.secondlife.com/browse/SVC-241

My current personal favourite (yes one I submitted myself =) is the 3d permission zone which allows you to define areas within a build that have access restrictions, as well as some other useful privacy things:
http://jira.secondlife.com/browse/SVC-99

Well, I understand the point about griefers I guess. But those systems wouldn't serve me any good if I have a business and I have a room only paying customers should enter. Or if I have a colosseum (which is why I created my system), I wouldn't want people to enter the lower end of the colosseum (inside perimeter where gladiators fight) during the events. So I can perfectly protect this perimeter, with the formulas I posted here.

I'm sure there are a few decent security systems out there. My point is that there are too many of the bad ones.

For griefers, though...I think there is also a freeze command as well. And how can a griefer listen/attack if you deactivate scripts on your land? Maybe we should be able to target specific people who wouldn't be able to run scripts on the land. Then we could script something to add them to that list.

*CDru

*scratches head*
Well, I'm confused a bit here. But I don't seem to see any serious flaw that should be removed in the current security system, more like there need to add more to it.

Ideally, I want to be able to set permission base on both X,Y and Z perimeter. I want to seal off entire 3rd floor from entering, for example. But we can already do that with security scripts, so I'm sated.

On the sim owner pov, i want better and quicker way to ban /and/ eject people than bringing down three windows and spend a full minute figuring it out. If I want something or someone banned, I want it /right then/. I want to right click on a particle and eject its generator and its owner. I want to click on a spam chat and ban the owner of the speaker. The slowness of the traditional tools come with the client is the reason aggressive security system exists. If I want someone banned, I can just shout their names and they'd be gone for good.

Actually, I've even thought about automate ban system that detect a rate of grey-goo spawning on a protected parcel. If someone's object are being replicated too fast and too much in short amount of time, I want the system to automatically kick them off and put a temporary ban of, perhaps, 24 hours. If someone is generating too much particles for their own good, I want the system to detect it and kill those generators. If someone purposedly spam the chat, I want an automate warning to be issued. Well, maybe someday such system could be created without much load on the server.