On Fri, 11 Apr 2014 22:40:39 +0200, Ray Banana wrote:
> Thus spake Double Derringer <
d-der...@gmail.com>
>
>> Meanwhile, three outages in six weeks strongly suggests that symptoms
>> were bandaged three times, while some undetected root cause remains so
>> far unaddressed.
>
> Seamus, will you, please, enlighten me
Why are you calling me "Seamus"? That's not my name.
> regarding the undetected root cause that could make one hardware box go
> belly up, cause a fan in another hardware box in a different location
> to fail
So far, that would suggest a shoddy subcontractor or parts-supplier --
either the organization switched to a new lowest bidder, or the existing
one started cutting corners on quality early this year.
> AND inject a software bug into an open source software library that
> goes unnoticed for two years?
That one's trickier. The fact remains that outages of E-S didn't used to
cluster closely together in time, and now they do, ergo *something*
changed. But the thing here that clustered with the other two wasn't the
software bug's creation. It was the bug suddenly coming to light. So the
common cause would have to have affected computer parts quality and
simultaneously made the bug get someone's attention. The obvious
explanation would be that a security researcher stumbled onto evidence of
the bug while trying to diagnose a third component failure caused
somewhere (not necessarily anywhere related to E-S) by the same new and
shoddy, or else newly-shoddy, hardware vendor.
> And how should I address such a creepy root cause? Nuke the NSA?
Oh, that's just paranoid.