Nice try, gotcha guy. But it turns out that the supposed MtGox "hack" was an inside job. It had NOTHING to do with XSRF, SQL, or whatever technical point the oversensitive guy (who ran away rather than debate mean, stinky libertarians) was previously belaboring.
mt. gox was, within the last week and by their own admission, vulnerable to cross-site request forgeries. i don't recall "s" ever saying anything about sql injection, which is harder to detect without access to the code. (it's not worth debating this if you're not a technical person yourself.)
Nobody is debating whether the XSRF vulnerability existed any longer, as it was demonstrated on Friday night.
It's been fixed and had nothing to do with the break-in, which was the fault of MtGox's finance auditor AND NOT THE RESULT OF XSRF, SQL, TROJANS, TEMPEST, OR WHATEVER YOUR BUDDY WAS MOANING ABOUT.
Now the issue is that so many were so quick to point fingers immediately following the MtGox breach, without bothering to confirm or verify anything with the principals involved.
You aren't the only "OMG we tried to warn them but they DINT LISEN" bozo who was proven wrong by tonight's interview. There are/were a lot of expert opinions, ie, wild guesses being thrown around.
Spare us the "it's not worth debating this if you're not a technical person yourself" snobbery. You may rest assured that I understand the difference between a XSRF and SQL injection. I get paid to make damn sure such things keep running smoothly.
I'm sure your e-peen is so massive it would stampede the women and scare the children, so please keep it private and to yourself.
