A) WD (by a government) or its staff (by WD management) were ordered to put in the backdoor, but didn't agree with doing so, thus made it obvious in the hopes that it would be found.
B) A backdoor that is found but written off as sloppy development is less damaging than a bug that if found and analysed looks deliberate (because bad development practices are hardly new for hardware manufacturers). _Potentially_ makes exploiting it less risky as well - if it's an obvious or known thing, the attacker could be anyone. If it's a subtle, undisclosed bug (that hasn't been used against many targets), that suggests, to some extent, the involvement of whomever could arrange for the bug to be placed there.
It probably isn't deliberate, but that possibility certainly isn't excluded either, so I'd be cautious about treating this as a hard and fast rule.
Is the objection that the way I said it was too disrespectful (no offense was intended, hence the :-) )? Disagreeing with the original statement (it might have downvotes too, but maybe more upvotes are hiding that)? Too obvious? Something else?
The initial view was a hotfix that just changed the hardcoded password, because senior management felt lightning would not strike twice.
What led them to believe you wouldn’t find it again? Was it a simple password that you guessed?
The timeline on the below link only refers to one specific incident, the time discussing this in principle went for roughly 11 months, and left me extremely disillusioned with the concept of responsible disclosure.
It's not that difficult to put in something much more subtle and still have deniability if the intent was malicious.
"The hard-coded backdoor that was found can't be a hard-coded backdoor, because Western Digital would never be so crass and incompetent as to put a hard-coded backdoor hidden in such a way that a security researcher would find it and attribute it to them."
How can one argue against such flawless logic when it even has an aphorism to describe it?
It's either the result an incompetent "secret backdoor" developer, or just plain incompetent development. Either way it's incompetent.
If it makes you feel any better, I acknowledge the spies / hackers / whatever will take advantage of it regardless of it's intent. :-)
How about creating a new aphorism?
"Never attribute to stupidity alone that which is adequately explained by both stupidity and malice."
"Never attribute to malice that which is adequately explained by management."
I guess the answer is no.
It seems to me that both are adequate explanations. One explanation requires one factor (stupidity), and the other two factors (stupidity and malice). The one factor explanation would seem to be the simpler of the two explanations.
It seems to me the original statement reverses the logic of Occam's razor by preferring the more complex example. I think my point still stands. The original statement makes as much sense as trying to reverse Occam's razor.
The whole enterprise is sabotaged by the simple fact that the logical foundation behind that aphorism can be bluntly, but better, summed as:
"Choose the most adequate explanation."
In this case Hanlon's razor (and probably any where it really applies), is just Occam's razor applied to a particular type of circumstance.
If someone actually wanted to implant a "secret" backdoor it would be disguised as a subtle bug and/or obfuscated in some way.
"Never attribute to malice that which is adequately explained by stupidity." Hanlon's Razor - https://en.wikipedia.org/wiki/Hanlon%27s_razor
[1] "[...] it turns out the error was caused due to buggy code and nothing I was or wasn't doing wrong." - if the code is so obviously buggy and the backdoor part isn't obviously a bug, the developers are probably just being sloppy, not malicious (bad or rushed development).