I was scammed by MtGox.

[kiwiasian]

Guys, stop telling me I need to change my password. For anything important, I never reuse a password from a different site. I had a secure alphanumeric password as well. My account was COMPROMISED, like a lot of other users here.

Let me reemphasize that I am not the only one affected. Please read the entire thread and see the link that someone posted earlier.

MtGox on the issue, addressing the security hole:

[jondecker76]

I feel your pain.
I too got BTC stolen from mtgox because of the comprimise, and its been reported to mtgox for a while now (who repeately denied it to all of us that got robbed)

Now lets see if the do the right thing, and refund the money to us that was lost due to their negligence and lack of security. (20.19 BTC in my case)

[Doktyr]

It is very simple to match http logins with IP addresses.  Any sane trading/currency site would do this logging so if it looks like this:

XX/XX/XXXX XX:XX:XX a.a.a.a - San Diego, CA - Comcast - example
XX/XX/XXXX XX:XX:XX a.a.a.a - San Diego, CA - Comcast - example
XX/XX/XXXX XX:XX:XX a.a.a.a - San Diego, CA - Comcast - example
XX/XX/XXXX XX:XX:XX b.b.b.b - Evil Hacker Town, China - ChinaNet - example

Then it would be pretty clear from their side if an account was hacked.  Mt. Gox is the only one who knows for sure.

Hopefully the logging server is intact.

EDIT: assuming the same account.

[sturle]

Why would I lie?

I even provided a picture for proof

You are still claiming you were scammed by Mt.Gox, and this picture shows an entirely different scenario.  So you are either lying or trying to prove something else.

Btw, if your password was cracked from a salted MD5 hash, it wasn't secure.  By definition.  Secure passords can't be cracked in finite time with todays technology, even when given the hash.

[BCEmporium]

Btw, if your password was cracked from a salted MD5 hash, it wasn't secure.  By definition.  Secure passords can't be cracked in finite time with todays technology, even when given the hash.

I'm a bit sick and tired with this load of "I'm a security expert" BS! Stop blaming it on users!
Let your db to leak into the web is way more serious than use even 123 as password. There's no way to blame this guy, except that MtGox hasn't "scam him", he just opened an account at a place with a lousy service.

[sturle]

Btw, if your password was cracked from a salted MD5 hash, it wasn't secure.  By definition.  Secure passords can't be cracked in finite time with todays technology, even when given the hash.

I'm a bit sick and tired with this load of "I'm a security expert" BS! Stop blaming it on users!
Let your db to leak into the web is way more serious than use even 123 as password. There's no way to blame this guy, except that MtGox hasn't "scam him", he just opened an account at a place with a lousy service.

Just ten years ago password files, YP, etc with password hashes in the open was the norm.  A crackable password was  as good as a plaintext password.  Passwords had to be good, and the openness ensured that people made good passwords.

Unfortunately after September 1994 a lot of clueless newbies entered the Internet.  Users who had no idea about passwords, security or computers or networks in general.  Also passwords had to be made more and more complex due to increasing computing power available to malicious users.  During the last few years systems have tried to remedy the problem a bit by hiding the hashes from public view.  I'm not sure if this is a good idea or not.

This kind of security by obscurity is false.  First and most important: it is impossible to know if your password is stored in a properly salted and secure hash, or if it is kept in an open database or hashed in an insecure way (NTLM springs to mind).   Secondly: users tend to make bad assumptions about cracking being difficult, and make bad passwords. 

Treat all password databases as open.  Make good and unique passwords, and you are secure if the password database use properly salted and hashed passwords.  (If not the site isn't secure anyway.)

Don't trust "security experts", btw.  People calling themselves experts on computer security typically have little or no real knowledge about security.  Just have a look around this forum for proof.  Real security experts can be recognised by i.e. the lack of firewalls and open WiFi at their home, but would never claim to be an expert on such a complex field.

[BCEmporium]

There're a few wrong concepts on your idea sturdle.
There IS security trough obscurity. This a simple fact, you can't know what you don't see.

The idea of "open everything" is the ultimate insecure protocol, for the following main reasons:

- The attacker will know exactly what he is after.
- A regular user by seeing a hashed pass will believe to be facing the ultimate uncrackable thing on Earth, as no matter how weak the hash it will look like mumbo-jumbo to him.
- Computing power is expanding by the day. MD5 was safe for the computing power back in the 90's, isn't anymore today. Same will happen to SHA-512 in time being.

The whole idea must be to have a set of password and use them according. Your car key is by far more complex than the one to open your bike's chain; still you need to have a way to open and start your car (remember in the case of passwords) it otherwise you would be on foot.

[sturle]

There're a few wrong concepts on your idea sturdle.
There IS security trough obscurity. This a simple fact, you can't know what you don't see.

Just the fact that you can't see it doesn't make it unknown.  It can even be visible and in plain sight, you just don't know what to look for or where to look.  Treat as much as possible as if it is visible to everyone, and it won't hurt you if it is.  Make sure to protect what you need to protect.  A password is simple to protect.  If you need to protect the password hash to protect your password, you have lost because the hash isn't under your control.

[BCEmporium]

sturle,

That's the "expect the worse" part, to that end I agree.
You can have security trough obscurity, but you can't think that obscurity may will stand forever.

Now, making everything open doesn't make nothing safer, actually it does the other way around as a potential attacker would know what and where to look for. Making open is a security breach by nature.

[Chucksta]

So you created an account (that's the complete history, right?), just to put some coins there and about two hours later that money disappeared? I am sorry for my distrust, but with hat kind of title and TradeHill in your signature I think it all looks somewhat suspicious to me.

Hmm, I wonder if a pro Tradehill person had anything to do with the recent bleep hit the fan MT Gox hack ?

[cryptoanarchist]

So you created an account (that's the complete history, right?), just to put some coins there and about two hours later that money disappeared? I am sorry for my distrust, but with hat kind of title and TradeHill in your signature I think it all looks somewhat suspicious to me.

My thoughts exactly

[makomk]

It is very simple to match http logins with IP addresses.

This doesn't work if you've got a CSRF vulnerability in your website. Since it's the victim's browser carrying out the request on behalf of the attacker, no unusual IP addresses show up in the log. In fact, it's actually impossible to prove that a CSRF vulnerability hasn't been exploited from server logs, which is one of many suspicious things about MagicalTux's recent statements. (You can look at the referrer header, but there are ways for the attacker to blank this out, and many users' browsers don't send a referrer anyway.)