Estimated time (conservative) for an attacker to break randomly-constructed
bitcointalk.org passwords with current technology
s=second; m=minute; h=hour; d=day; y=year; ky=1000 years; My=1 million years
Password length a-z a-zA-Z a-zA-Z0-9
8 0 3s 12s 2m
9 0 2m 13m 3h
10 8s 2h 13h 13d
11 3m 5d 34d 1y
12 1h 261d 3y 260y
13 1d 37y 366y 22ky
14 43d 1938y 22ky 1My
15 1y 100ky 1My 160My
-------------------------------------------------------
1 word 0
2 words 0
3 words 0
4 words 3m
5 words 19d
6 words 405y
7 words 3My
Good luck to the password hashers with my 34 character random password. The security answer is similar strength garbage. Don't think I'll need to change it. The forum also has it's own non-reused email address, if any mail turns up there I know the source is the forum or a leak.
Once you are hosting-pwnd though, you have to audit EVERYTHING if you're not going to wipe and restore from backup pre-intrusion. Anything could have been done, such as redirects or php hacks to capture passwords or cookie sessions, or wholesale VM state dumps that still would allow compromise of existing accounts.