Jeska, this answer did not even begin to answer the question I asked...
/139/a8/142546/1.html
Please do not copy and paste a generic answer to a very specific question.
I want to know exactly how the fix worked and if I should be going through my inventory trying to figure out if my full permissions objects have had their permissions change? I want to know if in the attempt to fix the permissions of items that were affected by the bug, if other items that were supposed to be full permissions were changed?
My inventory was being "repaired" when I logged in but as far as I can remember I didn't even log in during the time of the exploit so I don't understand what in my inventory would need "repairing.
A couple things...first I appreciate that someone is at least attempting to answer some questions here.
1. please try to answer or address each question in the order that it was placed rather than pick and choose the ones that you "know the answer" to.
2. please take some time and actually read and answer the questions rather than saying "oh this pertains to the bug fix so I'll paste in this answer" Like I said that answer didn't even come close to answering my question.
I'm not worried that someone took advantage of the bug I'm worried that LL inadvertantly broke the permissions of my legitimately purchased full permissions objects while trying to fix the illegally purchased ones.
Welcome to the Second Life Forums Archive
These forums are CLOSED. Please visit the new forums HERE
Please answer the question.... |
|
|
Musicteacher Rampal
Registered User
Join date: 20 Feb 2004
Posts: 824
|
10-12-2006 20:03
|
|
Jeska Linden
Administrator
Join date: 26 Jul 2004
Posts: 2,388
|
10-13-2006 13:57
I'm sorry if I wasn't clear enough in my answer, that was not my intention. The link to Robin's blog post provided further information which related to your question(s) (especially her follow up comment , which I've copied here.
The bug was introduced when we started the rolling update on Sunday at about 5:00PM. I thought I had included that time in the original post, and I apologize for leaving that out. The bug was discovered and eliminated by 1:30AM Monday morning. The rolling update wasn’t complete by then, so the entire grid wasn’t affected. Retroactively locked down means the permissions were returned to their original state. Only objects which were copied during that time (i.e. a fully permissioned copy was made) are affected. We realize this is our error, and we will help anyone who has reason to believe that something they created is being sold by someone else without their permission. If you think this is the case with something you made, please email [email]support@lindenlab.com[/email] with the header “PERMISSIONS BUG” and we will make sure to address the problem. I believe that answers both of your original questions -- How did the fix for the exploited full perms. items work? - it returned permissions to the original state on any fully permissioned copies made during that time and How did it know what to change the perms. on and what not to? - we were able to identify only those objects which were copied during that time AND fully permissions copies were made. Thanks again. _____________________
"The opportunity to participate in the creation of a new world is really a rare one, and so I hope you cherish it."
- Mitch Kapor on Second Life at the 2006 SLCC |