Comment 104 for bug 538796

Chris, no decisions have been made here, and no one (certainly not me) meant to flat out block anything here w/o figuring out who's in charge of the Moonlight plugin and talking to them and giving them time to react. Flat out blocking w/o an existing update that solves the reason for blocking is our very last resort, we don't go there lightly. I apologize for not being clear about that.

If you read bug 582130, you'll see that one of the steps there is to "notify the authors", which clearly could've been worded better, but the intent there is to figure out who the authors are and let them know we have reason to believe blocking is necessary, and work with them on this issue. Sounds like you're one of the authors, please correct me if I'm wrong on that. And if other people on the Moonlight side need to be involved here, please feel free to cc as many people as necessary on this bug and on bug 582130.

But based on the talk in this bug so far, it does *seem* like old versions (possibly including the current versiono, even) need to be blocked, but if the problem turns out to not be in the Moonlight plugin then we'll naturally investigate further here.

Again, sorry for sending the wrong message here, that was certainly not my intent.