Last report: [Click Here]
Here it is again, some stats on how many insecure RCs were in the staff= serveroptions on the Graal playerworlds, until they were removed.
Like last time I've been server hoping and removing those bad RCs with an IP range of *.*.*.*. Since the last time I have seen a considerable decrease in the amount of bad doings on playerworlds, due to a general increase in security of playerworlds - preventing some attacks.
There is, however, room for improvement as always. It's good to see it has improved though, and the same amount of servers are basically online, so it's easy to compare last times data to this. So on with the stats and graphs!
.:THE STATS:.
1. How many RCs had an IP range of *.*.*.*?
170RCs had an IP range of *.*.*.* compared to
339RCs last time.
This is a good decrease, and hopefully next time it would be nice to see it lower than 100 RCs, as it should be very low as there is no real reason to allow an insecure RC into staff= and leave it there.
2. How many playerworlds were 100% Secure?
By secure, I mean all RCs in staff= had an IP range set.
This is a good increase, however it should be alot more. I am happy to see that most servers had only 1/2 insecure RCs and that it's a few playerworlds that let down the amount of insecure RCs with practically all of them insecure.
3. What level RCs were in the staff= server option with an IP of *.*.*.*?
Number of level4s: 57/170 (33%)
Number of level3s: 26/170 (15%)
Number of level2s: 15/170 (9%)
Number of level1s: 44/170 (26%)
Number of level0s: 28/170 (17%)
Below is a graph to show the general decrease in all the insecure RCs over all the RC levels:
4. Which playerworlds were 100% secure?
Classic playerworlds 100% Secure: 6/9 (66% -30% last time)
Hosted playerworlds 100% Secure: 2/8 (25% - 30% last time)
Other playerworlds 100% Secure: 32/82 (39% - 21% last time)
.:THE POINT:.
Okay, enough with the graphics and stats on with the points:
Odd Points:- NO RC should have an IP range of *.*.*.*
- IP ranges should be checked every so many months, to make sure they are all set
If your a manager:- Make sure you check the Admin-Playerworld accounts IP range, because this doesn't need to be in staff=, so you may forget it.
- Never add anyone to the staff= serveroption without an IP range, make them give you the IP range first.
- Don't give high rights to new staff.
- Give staff only the rights they need
If your a staff member:- Check your IP range is always set
- Remind the Manager/Admin to set your IP when they add your RC
Punishments:
1) Those with big RC levels on player accounts, in the Hosted tab, have been removed for up-to 10days.
2) Those with lots of insecure RCs this time, as well as last time will later have their playerworlds disabled for a week.
How to set an IP range: [Click Here]
Thank you.