| Key: |
SVC-4243
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Duplicate
|
| Priority: |
Critical
|
| Assignee: |
Unassigned
|
| Reporter: |
Fred Rookstown
|
| Votes: |
1
|
| Watchers: |
3
|
|
If you were logged in you would be able to see more operations.
|
|
|
llDialog, llLoadURL, and similar functions that create a blue dialog are being used heavily by griefers to crash or log out users in sandboxes, welcome areas, etc. A fix is required.
To reproduce this type of spam:
- Place the Master script into a prim
- Paste the slave script in it 100 or so times (make it in an inventory folder, CTRL-C, and hold down CTRL-V for a while, then drag them all into your prim).
- Copy the box six times and say "CRASH ME" in local chat.
Your window should fill with llDialog spam and some of you may crash. I have designed the scripts to die when you log out or leave the sim. You can also delete the box, of course.
My suggestion for a server-side fix (needed in conjunction to a fix in the viewer, see VWR-3561) is the following:
- Throttle llDialog/llMap/llRequestPermissions for the RECEIVING USER (not the script or object) to, say, 1 per second UNLESS IF THE ORIGINATING OBJECT IS OWNED BY THE RECEIVER. THis will prevent some guy from running around on several accounts planting llDialog spammers all over the place to spam someone, yet will allow some weapons HUDs to continue operating.
- Excessive llDialog/llMap/llRequestPermissions calls from the SENDING OBJECT should set all scripts in that object to non-running. Again, however, an object owned by the recipient of the dialogs should allow all dialogs to the owner to pass.
- llDialogs should only be sent to a user if the object is within the same sim.
- llDialog, etc network messages should be given a lower priority than connection-critical SL traffic, to prevent logouts from excessive llDialog spam.
|
|
Description
|
llDialog, llLoadURL, and similar functions that create a blue dialog are being used heavily by griefers to crash or log out users in sandboxes, welcome areas, etc. A fix is required.
To reproduce this type of spam:
- Place the Master script into a prim
- Paste the slave script in it 100 or so times (make it in an inventory folder, CTRL-C, and hold down CTRL-V for a while, then drag them all into your prim).
- Copy the box six times and say "CRASH ME" in local chat.
Your window should fill with llDialog spam and some of you may crash. I have designed the scripts to die when you log out or leave the sim. You can also delete the box, of course.
My suggestion for a server-side fix (needed in conjunction to a fix in the viewer, see VWR-3561) is the following:
- Throttle llDialog/llMap/llRequestPermissions for the RECEIVING USER (not the script or object) to, say, 1 per second UNLESS IF THE ORIGINATING OBJECT IS OWNED BY THE RECEIVER. THis will prevent some guy from running around on several accounts planting llDialog spammers all over the place to spam someone, yet will allow some weapons HUDs to continue operating.
- Excessive llDialog/llMap/llRequestPermissions calls from the SENDING OBJECT should set all scripts in that object to non-running. Again, however, an object owned by the recipient of the dialogs should allow all dialogs to the owner to pass.
- llDialogs should only be sent to a user if the object is within the same sim.
- llDialog, etc network messages should be given a lower priority than connection-critical SL traffic, to prevent logouts from excessive llDialog spam.
|
Show » |
|
LLNotifyBox-creating functions need serious throttling.
