I think they're in my password manager but there's hundreds to try...
Some password managers provide a means to export their contents for backup purposes. From a security point of view this is a very risky thing to do. Assuming that you know the risks of exposing all your passwords and you are an advanced user of the command shell, here is what you can do to quickly work through a list of password candidates:
-Locate the key backup file the wallet directory (it has a .key extension) and copy it to a secure location on a safe machine (call it target.key).
-Use your password manager's export function to copy your password as a CSV (comma separated values) file to the same location as the key file (call it passwords.csv).
-Examine the CSV file to determine its layout (e.g. url,username,password,label etc) and note the column number of the password (it is 3 in the example).
-Copy this Unix script (it might need modification for Windows) alongside the CSV file (call it apply-guesses.sh) and give it executable permissions with chmod +x apply-guesses.sh.
#!/bin/bash
echo Usage: apply-guesses.sh [password CSV] [key file]
echo Password file: $1
echo Key file: $2
for password in $( awk -F , -v OFS=' ' '{print $3}' $1 ); do
echo ------
echo Attempting: $password...
openssl enc -d -p -aes-256-cbc -a -in $2 -out recovered.key -pass pass:$password
if [ $? -eq 0 ];
then
echo "Success!";
break;
else
echo "Failed";
fi
echo ------
done
You may need to adjust the {print $3} section on line 5 to reflect the password column (e.g. {print $12} if password is in position 12).
Once ready execute the script as follows:
$ ./apply-guesses.sh passwords.csv target.key
The script will report each password as it tries it and will stop immediately upon successful decryption. If all goes well you can use the password with MultiBit to rescue your bitcoins.
Make sure you tidy up all your files after you have finished. Use the Unix "secure delete" command to remove each file in turn using the 35-pass Gutmann algorithm if available:
$ srm passwords.csv
$ srm target.key
$ srm recovered.key
Make sure you erase your terminal scrollback history to avoid leaving traces of console output containing passwords. In MacOS Terminal use Edit | Clear Scrollback. On Linux echo -e '\0033\0143' might do the trick. Windows, um, no idea.
Nope that didn't work...