Quote from: Clipse on June 21, 2011, 01:18:29 AM

Quote from: DukeOfEarl on June 21, 2011, 01:14:08 AM

10364 toasty toasty@dragondata.com $1$rtQupk2h$FR.Ee1vC2s70WFatliWHz1

Google this guy. He has a unique skillset to match.

Thanks, all I find is security work and loads of mailinglist articles where he is involved in various security related content with regards to websites.

Must be another flakey coincidence that he seems to know his parts around that world more than avg joe and to get burn like this aswell, wtfever.

Which is likely why MtGox's story given to him seemed suspicious at best, fraudulent at worse - and even perhaps is when he decided to hold off on sending the funds he did get out back? If you worked in this field daily, you'd likely at least have suspicions of the same thing given the responses offered. I know I did. They were pathetic and easily immediately proven false. Something didn't add up right, so the correct course of action was to pause and let information come to light to ensure the correct course of action was taken. This information was not forthcoming.

The truth may or may not come out eventually, I really truly hope it does and simply proves incompetence. Now not only for Bitcoin's, but Kevin's sake. I feel rather bad for my part in helping convince him to post his story publicly, to try to elicit some form of reasonable level of transparency about the issue. There was only downside for him, but I did my part in helping convince him the community benefits would outweigh the possible drawbacks on the personal side. I was wrong. It truly was, whether you believe it or not, an attempt to bring the spotlight on what he felt as a major accountability and transparency issue. If this had been handled reasonably, the money would almost assuredly be back in the proper accounts and you wouldn't have heard about much other than a simple hack and a brief market crash.

It goes beyond a simple hack. The fact he's blaming Kevin for the "hack" itself proves that in itself for me. Note that only third parties have been blamed in all this. Not once has MT taken any responsibility for this supposed "hack" - why is that?