News for hackers. Stuff that matters.
Re:Bitcointalk Server Compromised by ah- on Sunday May 24, 2015 @11:44AM (#9596556)
What's the best way nowadays to protect yourself as a user against this? You certainly can't trust anyone to store your password securely, so you're forced to have a strong password per site, and it's impossible to memorize that many passwords.

I'm currently using Password Hasher (https://chrome.google.com/webstore/detail/password-hasher-pl...), but that only works well because I mostly use just one machine.

Re:Bitcointalk Server Compromised by hobarrera on Sunday May 24, 2015 @12:45PM (#9596729)
pass[1] is a pretty good choice. But you also have to make sure your provider really follows decent security practices.

gandi.net is a pretty decent provider not full of BS (as their slogan states).

[1]: http://zx2c4.com/projects/password-store/

Re:Bitcointalk Server Compromised by ufmace on Sunday May 24, 2015 @03:18PM (#9597232)
I've come to the conclusion that the most important thing by far is a different password for every site. If you do nothing else, figure out a way to do that. It's probably also a good idea to make sure that your security question answers are anything but the actual answers to those questions. I prefer looking up random words for each one, and storing them in the Lastpass entry for the site.

I view password complexity and obsessing over how hard it would be to crack your password hash with various setups to be of little value. If they're far enough in to get your password hash, it's better to assume they can see and do anything and everything on the site even if they can't crack your password. If you've actually used a different password on every site, there isn't much left to worry about. Still, if you're using a password manager, it's cheap to make all of your passwords long, random strings with upper, lower, numbers, and specials, so why not do it?

Re:Bitcointalk Server Compromised by yuvadam on Sunday May 24, 2015 @11:47AM (#9596562)
Use a password manager. KeepassX is a good choice if you only trust yourself (and your backups).

LastPass and 1Password are good choices if you don't care about letting others host your (supposedly encrypted) passwords.

Re:Bitcointalk Server Compromised by mannkind on Sunday May 24, 2015 @12:38PM (#9596708)
> LastPass and 1Password are good choices if you don't care about letting others host your (supposedly encrypted) passwords.

That statement doesn't apply to 1Password; AgileBits does not host your data.

Re:Bitcointalk Server Compromised by becausecomputer on Sunday May 24, 2015 @01:18PM (#9596833)
1Password works with Dropbox, unless you manage the storage and backup manually.
Re:Bitcointalk Server Compromised by tetrep on Sunday May 24, 2015 @02:09PM (#9597001)
> 1Password works with Dropbox...

Because it has the amazing feature of storing all your passwords in a file. It's nothing like the features offered by lastpass with respect to serving you your passwords from a remote host and if you can't trust your password manager to KDF & encrypt then you really shouldn't be using it as it's doubtful it's properly generating secure passwords.

Re:Bitcointalk Server Compromised by imrehg on Sunday May 24, 2015 @11:57AM (#9596592)
Thumbs up for KeePassX too!

Also, there's Mitro, encrypted password manager living inside a Chrome extension: https://www.mitro.co/

Re:Bitcointalk Server Compromised by jiayo on Sunday May 24, 2015 @12:05PM (#9596616)
I am using KeePass Password Safe v2 (while on Windows), and KeePassX on linux and OS X.

I use a strong password, and a key file, which is just a blob of random bytes. The encrypted password database (.kdbx) is published to Dropbox, which handles sync across devices. The key file (.key) stays on an encrypted USB stick on my physical keychain, and is physically backed up in a few safe places. It is never published online. This makes it effectively a second factor.

I have a domain, example.com, which is set up for wildcard email forwarding. When I sign up for a service, I use [email protected] (recently I have started obscuring this a bit more, e.g. [email protected]). This limits password reset exposure, and also the ability for other services that are in cahoots with each other to link my accounts together by email address.

Everything connected to this domain (registrar, DNS provider, email provider) is protected by separate TOTP 2FA tokens.

I simply do not access any authenticated services if I don't have access to KeePass and my password vault.

I have over 250 entries in my vault. At this point, it's less about remembering and generating passwords than it is about keeping track of what I've signed up for and when. Some things, you only look at once every few years, and my S.O.P. before KeePass was usually password resets.

For extremely high value accounts, I have memorized a "prefix" which I prepend to generated passwords. This limits exposure in the case my entire password database leaks, to just things like hackernews, reddit and other low value services.

I do not use KeePass for my dropbox password, because I could end up locked out entirely.

So this is really 3 things to remember: Password vault password, Dropbox password, and high security prefix.

There are some weaknesses in this scheme. As another user mentioned below, I am not invulnerable to an @N style hijacking. Someone could socially engineer my registrar, DNS provider or email provider, hijack my email and then initiate a password reset. I'm not sure how to defend against this. Common knowledge is to not use custom domains, since it's easier to hijack example.com than gmail.com, but for me the value of having unique email accounts per service is too high to give up.

The other obvious point of vulnerability is keyloggers and trojans that attack the KeePass processes directly. This is not something I've spent a lot of time thinking about. It is a scorched earth scenario, and in that case I won't be the only one in trouble.

This method has served me well for over 5 years. I've acknowledged there's some flaws here, but I fundamentally do not trust any of the online password management services (LastPass, 1Password, etc.) and I find the idea of paying to store/access them distasteful at best and extortionate at worst.

edit: I also use KeePass to generate my security questions. Very few online services are savvy enough to use a one-way hash on these questions, that are the keys to the castle. I've had to recite these to support reps over the phone, who can see them in clear text.

e.g.,

What was the name of the street you grew up on? => xcmqbbpgpuuxyrdw

What was your first pet's name? => owuynnfhwscgigciq

Re:Bitcointalk Server Compromised by ams6110 on Sunday May 24, 2015 @12:28PM (#9596681)
Nitpick, "mydomain.com" is a real domain (registrar). Use "example.com" for example domains.
Re:Bitcointalk Server Compromised by jiayo on Sunday May 24, 2015 @12:34PM (#9596703)
Fixed, thanks!
Re:Bitcointalk Server Compromised by unclebucknasty on Sunday May 24, 2015 @04:15PM (#9597414)
Sad part is that, even with all of this, you're only as secure as each service not being otherwise breached, and that scenario is probably more likely in aggregate than your credentials being compromised. We are all as vulnerable as the engineering practices of each service with which we engage.

We (especially in the tech community) tend to focus strictly on tech solutions. But, one of things that isn't discussed nearly enough is the legal aspect of all of this. That is, penalties for hacking, international cooperation, etc. As it is, the scammers have an unlimited free pass to just keep coming at us/services. The worst that can happen to them in most cases is that they simply don't get what they are after. It's all upside and little risk. With that motivation, they will simply persist until they find the weak links.

Re:Bitcointalk Server Compromised by crobertsbmw on Sunday May 24, 2015 @02:35PM (#9597086)
You probably already know this, but you can set up unique emails through gmail using the "+" character. [email protected]. This will let you keep track of who is using what email address. Although, as this becomes more common knowledge, people could just strip off the anything after the "+" when saving email addresses.
Re:Bitcointalk Server Compromised by tokenizerrr on Sunday May 24, 2015 @06:45PM (#9597918)
Why not use regular Keepass on Linux? It runs under Mono.
Re:Bitcointalk Server Compromised by Buge on Sunday May 24, 2015 @06:41PM (#9597904)
What registrar do you use?