The session id prevents certain kinds of spoofing attacks.
On 2006 Aug 2, at 09:21, Jesse Nesbitt wrote:
So you fixed the exploits, took away the god mode stalking thing [:(], and started putting in all the new RESTfull stuff. All in all, that's great! Although, why put a session id into those object fields? Keep up the good work guys and gals! --Jesse On 8/2/06, Phoenix <[EMAIL PROTECTED]> wrote:ObjectAdd has been shuffled a bit so that most of the information is available in a new AgentData block. ObjectPosition, ObjectScale, ObjectRotation, ObjectFlagUpdae, ObjectImage, ObjectMaterial, ObjectShape, ObjectExtraParams, ObjectPermissions, ObjectSaleInfo, ObjectName, ObjectDescription, ObjectCategory, and RequestTaskInventory have all picked up a session id. SetScriptRunning, ScriptReset, UpdateTaskInventory, RemoveTaskInventory, and RezScript were all slightly shuffled or simply picked up an AgentData block with at least the current agent id and session id, and a few picked up the current group id as well.
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ libsecondlife-dev mailing list libsecondlife-dev@gna.org https://mail.gna.org/listinfo/libsecondlife-dev
