[wp-forums] Exploit report

[Petit]

As a first attempt to stem the flood, I think it was wise to cut that 
thread.
If the matter dies that's fine - if not, some reassurance from  trusted 
people  will have to added.

Remember last time it happened. It's no joy but sure to happen from time 
to time.
/Petit

Michael B wrote:
> I'm simply suggesting that closing the thread with a post that the proper
> channels have looked into the potential exploit, and that if there's any
> legitimacy to the claim, that it will be addressed in  swift fashion.  
> I'm
> not saying my response is better, or right, I'm simply creating 
> dialogue for
> the inevitable next time this happens.
>
> I've already started seeing post titles show up in blogs in my feed 
> reader
> about the subject, so if there was a semi-official response out there, it
> might quell some of the mob.
>
> Just my 2¢.
>
> ~miklb
>
>
> On 5/26/06, TechGnome <tg at tannagh.com> wrote:
>>
>> The problem was that there was a response giving even more details. for
>> as long as I can remember, everytime there's one of these reports,
>> there's ALWAYS accusations of a cover-up. Podz has stated that at least
>> one person who needs to know about this stuff already knows... if some
>> one wants to start a thread accusing us of covering it up, I'll be the
>> first (if given the chance, second if podz gets to it before me) to
>> stand up and explain the situation and the circumstances and own up to
>> deleting it. If the thread had just died, that would be one thing. But
>> when people start replying to it giving more details, I think the line
>> needs to be drawn.
>>
>> -tg
>>
>>
>> Michael B wrote:
>> > On 5/26/06, TechGnome <tg at tannagh.com> wrote:
>> >>
>> >> Ack, jeezzes... I'm deleting the thread... it's starting to get
>> replies.
>> >>
>> >> -tg
>> >
>> >
>> > Was deleting the best idea.  Does that come across as WP is hiding a
>> > potential security flaw?
>> >
>> > ~miklb
>> >
>> >
>> > Podz wrote:
>> >> > TechGnome wrote:
>> >> >> Broke it.... but should we remove it, close the thread and/or
>> possibly
>> >> >> delete it? Don't want to sound like chicken little here, but we 
>> also
>> >> >> want to be cautious until we know the true extent of the 
>> allegation.
>> >> >>
>> >> > It's been seen by at least 1 of the right people.
>> >> >
>> >> > P.
>> >> >