SLUniverse Forums - View Single Post - Second Inventory is fixing transfer of creator information

Samantha Fuller · 05-26-2009, 12:09 AM

I was just over at the fourms at OLG and found out that Second Inventory is trying to fix transfer of creator information (currently testing) as a condition of allowing its clients to log onto the OpenLife Grid.

But this will solve some IP problems and highlight others.

below is my crosspost.

I'm very glad to hear that the hold up is related to saving creator information. Holding out for this is really good if it is possible, and it appears as if Sakai & the SI team think it is possible though extremely difficult. Sometimes difficult customers spur creators to new heights. And if you think about it should be possible because a client can take a full permission prim remake it and upload the new object, how is the server to know what the original prim creator information was it has to rely on the client passing that along. ^^

Of course this will highlight an IP issue that needs to be examined, SI code is not open source but half of reverse engineering something is knowing that it can be done. Once SI proves that it is possible other client hackers will realize that they can spoof the creator field on created prims and cause all kinds of havoc. about the only thing the server can check will be that their is that the uploaded creator information is a real av and possibly that the creating av has a full permission prim in its possession.

I think we need to be thinking about these things before they come out of the woodwork and bite us on the ass.

05-26-2009, 12:09 AM	#1 (permalink)
Samantha Fuller Senior Member Mostly quiet Lurker Join Date: Jun 2007 Posts: 341 My Mood:	Second Inventory is fixing transfer of creator information I was just over at the fourms at OLG and found out that Second Inventory is trying to fix transfer of creator information (currently testing) as a condition of allowing its clients to log onto the OpenLife Grid. But this will solve some IP problems and highlight others. below is my crosspost. I'm very glad to hear that the hold up is related to saving creator information. Holding out for this is really good if it is possible, and it appears as if Sakai & the SI team think it is possible though extremely difficult. Sometimes difficult customers spur creators to new heights. And if you think about it should be possible because a client can take a full permission prim remake it and upload the new object, how is the server to know what the original prim creator information was it has to rely on the client passing that along. ^^ Of course this will highlight an IP issue that needs to be examined, SI code is not open source but half of reverse engineering something is knowing that it can be done. Once SI proves that it is possible other client hackers will realize that they can spoof the creator field on created prims and cause all kinds of havoc. about the only thing the server can check will be that their is that the uploaded creator information is a real av and possibly that the creating av has a full permission prim in its possession. I think we need to be thinking about these things before they come out of the woodwork and bite us on the ass.