Pues sí, a mí también me gustaría saber algo.....

Tenemos nuevo mensaje en la web de mt.gox con lo que ha salido de la reunión que había hoy.

Las cosas más interesantes que he visto son las siguientes:
1 - Están investigando la desaparición de los BTCs con la ayuda de compañías IT.
2 - Están buscando compradores y realizando un proceso de selección de posibles compradores de mtgox
3- Se va a retrasar la implementación del formulario para rellenar con los documentos para pedir los BTCs (Ya no va a ser 28 de Noviembre)

Salu2

I feel a moron for this, but I locked myself out of my wallet (w/ about 2.5 BTC in it) today,
right after setting a passphrase. (I use bitcoin-qt.)

I tried all the obvious typing variants of the phrase, and then ran the Ruby script in this thread for an hour or so (basically through depth 2 of all 1-character substitutions into the passphrase I thought I was using).

Anyone have suggestions for next steps? I haven't "forgotten" anything about my passphrase; I even wrote it down "exactly" to store elsewhere for safekeeping. I don't have an unencrypted backup because I am a moron.

I run Ubuntu, but I am still nervous that my system might have been compromised somehow, although that's pretty unlikely. I didn't do anything in particular to secure the system (I don't encrypt my filesystem). I ran a couple of utilities to check for rootkits, but they didn't find anything suspicious.

So... somehow I must have mistyped the passphrase twice in a non-obvious way, which seems extraordinarily unlikely. I tried:
* Case inversion (caps lock)
* Adding punctuation and a space at the end
* All obvious variants for punctuation and capitalization in the passphrase
The script (I think) tried:
* All adjacent character swaps
* All 1-letter character changes
* Most 2-letter character changes

The form of the passphrase is (with capitalization and punctuation)
"Proper Name, Same Name; random word another Word"

Can anyone think of other good typing modifications to try?

If not, can anyone think what could be going on other than a strange repeated typo, or a malicious actor having installed (somehow!) a keylogger on my system and then changing the passphrase? Also I didn't have bitcoind installed at all until today, when I added it to run the Ruby script for brute-forcing the passphrase. Would it even be possible for someone else without physical access to my machine (which I'm fairly certain was safe) to have changed my passphrase with only bitcoin-qt installed on my system?

I've been using a version of bitcoin-qt installed via the Ubuntu package manner roughly 2 months ago (I think), and I have had some issues; once the block data got corrupted and I had to redownload the whole blockchain and start a new wallet, although this was before I owned any bitcoins, so I just moved on.  Could a buggy bitcoin installation have somehow caused my problem? Is it worth installing a new software wallet program and trying to import wallet.dat using that?

YES!!!! panic over nevermind  this thread

Lol I cant be the only one that's been a bitcoin noob lolz

OK, start!

Someone already have made website's Spanish localization. Hovewer strings.xml for Android app is still missing.

Lets try.

Well, you had a good idea to see if you can crack the known short password with umlauts.

1) I currently don't have access to any other machine except my single laptop, I really can't help you with details. In particular I'm almost illiterate in German.
2) verify if the "Language for non-Unicode programs" in Control Panel is still "German (Germany)".
3) using regedit.exe verify the settings in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage\ACP. It should probably be 1252 which means the Windows-1252 encoding was used for non-internationalized programs like Satoshi's client. Also note the OEMCP value from the same page. Ostensibly OEMCP is used only for DOS compatibility mode, but some programs use it because of bugs.
4) If you encrypted your wallet using bitcoin-Qt then verify that you can decrypt it from the command line by using bitcoind.
5) Make sure that the step 4) works for all umlauts you may have used, both lower-case and upper-case.
6) configure Ubuntu's terminal program to use Windows-1252 or if you access it from Windows via ssh configure your ssh client to use that encoding
7) rerun the test decryption of the known-password wallet on Ubuntu's command line.
verify that your Ruby program is using the correct encodings for umlauts
9) run the Ruby crack program

While I'm almost illiterate in German I'm very familiar with the computer-specific problems encountered by German-speaking people, especially in multi-language places like Switzerland. Because of the QWERTY vs. QWERTZ vs. AZERTY keyboard layout issue, when you were entering your password sight-unseen you may have entered some other characters because of accidental switching of the keyboard layouts. Have you actually verified in the Language Bar that you were using the correct layout while typing your password?