News for hackers. Stuff that matters.
Re:SendGrid employee’s account was compromised and used to a... by nwenzel on Friday May 01, 2015 @01:16AM (#9469617)
Two Factor Authentication. Please, all companies that have any of my data, don't just give me the ability to use 2FA, please force all of your employees to use it on their email, GitHub repos, everything. It should be a requirent right alongside https.

My personal favorite service is Authy, now part of Twilio.

Re:SendGrid employee’s account was compromised and used to a... by shard972 on Friday May 01, 2015 @02:46AM (#9469880)
> Two Factor Authentication. Please

My understanding is that Sendgrid isn't too keen on dongles.

Re:SendGrid employee’s account was compromised and used to a... by mtrimpe on Friday May 01, 2015 @04:56AM (#9470208)
Maybe they should just publicly fire someone to make this all go away.
Re:SendGrid employee’s account was compromised and used to a... by BhavdeepSethi on Friday May 01, 2015 @12:59PM (#9472869)
How will that solve anything? The damage is already done. No point someone losing their job over this.
Re:SendGrid employee’s account was compromised and used to a... by cheshire137 on Friday May 01, 2015 @02:49PM (#9473669)
It was a reference to this drama from a couple years back: http://arstechnica.com/tech-policy/2013/03/21/how-dongle-jok...
Re:SendGrid employee’s account was compromised and used to a... by hueving on Friday May 01, 2015 @03:24AM (#9469967)
too soon :)
Re:SendGrid employee’s account was compromised and used to a... by vidarh on Friday May 01, 2015 @11:55AM (#9472291)
Been long enough that it took me a while to get it...
Re:SendGrid employee’s account was compromised and used to a... by famousactress on Friday May 01, 2015 @09:52AM (#9471229)
Yes please. One of the thing that annoys me about these notices is that they all recommend that we turn on 2FA, when the fucking root cause was that THEY DIDN'T.
Re:SendGrid employee’s account was compromised and used to a... by toomuchtodo on Friday May 01, 2015 @01:44AM (#9469715)
Re:SendGrid employee’s account was compromised and used to a... by biafra on Friday May 01, 2015 @08:29AM (#9470835)
A service for 2FA?

I prefer a stand alone app or device for that. Why would Authy demand that I give them a phone number and an email address if not for monetizing (as in selling to anyone) my personal information?

Re:SendGrid employee’s account was compromised and used to a... by tracker1 on Friday May 01, 2015 @02:44PM (#9473632)
Secondary factor for authenticating your authy account? In addition to your own data key. 2FA for your 2FA.
Re:SendGrid employee’s account was compromised and used to a... by biafra on Sunday May 03, 2015 @04:51AM (#9480536)
Are you serious? This makes no sense. Does that mean Authy won't work if it has no internet connection? That would be an important limitation. I hear they do backup the seeds for 2FA. But why is that not optional?
Re:SendGrid employee’s account was compromised and used to a... by tracker1 on Monday May 04, 2015 @01:01PM (#9487420)
It is optional... but by validating your phone number, when you install the app, on for instance your tablet, you can authenticate the device. Backup is optional, with a client-side passphrase for encryption. It's not like it's the only app for this, 2FA/OTP is well documented with libraries in a number of languages. Is far as invasive goes, given what it is for, it's a pretty decent application.
Re:SendGrid employee’s account was compromised and used to a... by troycarlson on Friday May 01, 2015 @01:35AM (#9469682)
This. It's not unreasonable to flat-out require 2FA.
Re:SendGrid employee’s account was compromised and used to a... by atmosx on Friday May 01, 2015 @02:11AM (#9469775)
2-factor auth might be good for SendGrid but depending on another device (be it your phone or a token-device) sucks big time in the real world.
Re:SendGrid employee’s account was compromised and used to a... by jsmthrowaway on Friday May 01, 2015 @02:51AM (#9469889)
Your data growing legs also sucks big time in the real world.
Re:SendGrid employee’s account was compromised and used to a... by troycarlson on Friday May 01, 2015 @12:12PM (#9472457)
Exactly. If I'm trusting a company with a core component of my business/livelihood (code repositories, email marketing campaigns, etc.), phrases like "it's a minor inconvenience" are unacceptable excuses for lax security.
Re:SendGrid employee’s account was compromised and used to a... by dublinben on Friday May 01, 2015 @08:34AM (#9470854)
Enterprises that are serious about security have been requiring their employees to use security tokens for years. It's not an unreasonable burden to maintain control over account access.
Re:SendGrid employee’s account was compromised and used to a... by toomuchtodo on Friday May 01, 2015 @11:46AM (#9472206)
Seriously? People can't be bothered to take the extra 45 seconds to open an Authenticator app and type in the current 6 digit code?
Re:SendGrid employee’s account was compromised and used to a... by Karunamon on Friday May 01, 2015 @12:04PM (#9472376)
Seriously, because getting into the website is one thing, getting into anything that uses an API is something else altogether.

Google and Github both require the use of app specific passwords if you have 2FA on. Which means that accessing anything that uses the API is no longer a matter of username+password+token, it means username+password+log into site+generate huge and ridiculous password that is only shown once+save that into the app.

It's a pain in the ass. Massively.

Re:SendGrid employee’s account was compromised and used to a... by toomuchtodo on Friday May 01, 2015 @12:06PM (#9472394)
> It's a pain in the ass. Massively.

Compared to someone gaining access to your Gmail (and the rest of your Google platform services) account or Github access? Hardly.

I agree its not perfect, but its relatively painless for the benefit obtained.

Re:SendGrid employee’s account was compromised and used to a... by Karunamon on Friday May 01, 2015 @12:14PM (#9472483)
This is an argument that can apply to any particularly annoying security arrangement. What you miss is that by making the process so arduous, people will not use it.

There's no reason I can't generate my own app passwords, nor is there a reason to prevent me from accessing my own passwords later.

Re:SendGrid employee’s account was compromised and used to a... by tracker1 on Friday May 01, 2015 @02:50PM (#9473672)
I would just assume let the system generate one... usually it's as random/long as anything I would create and people in general create short/weak passwords... if the password requirements where 16+ characters, upper, lower, number and other characters that would piss people off too. In this case, if you didn't copy/paste it into your app/service... generate a new password, and revoke the old one.

The only flaw here is when you aren't able to label your prior passwords and are only given the option to nuke them all. That ticks me off more than anything. I've got 2fa enabled most places that allow it now, and use Authy too. The only times it's been a real pita is when I've had to setup email on a new phone with a generated passphrase (I'm trying to stop using the "password"). Other than that has been one day where I forgot my phone at home and didn't go back to get it after I was in my car...

Re:SendGrid employee’s account was compromised and used to a... by tomjen3 on Friday May 01, 2015 @02:21AM (#9469796)
You should never use an external 2 factor app, use the Google app since it implements a standard and works offline. You will want this eventually.
Re:SendGrid employee’s account was compromised and used to a... by jsmthrowaway on Friday May 01, 2015 @02:40AM (#9469847)
TOTP is fairly weak. Convenient, but weak, due to the shared secret. I've seen proofs of concept that trivially lift the secrets from Google Authenticator. On the server side, the service is probably storing your TOTP secret one column adjacent to your hashed password. When done poorly (and most are), TOTP is basically no additional factor. Also backup codes, app specific passwords, etc, etc.

Certain classes of non-shared-secret hardware token are waaaaaaaaay better. Just less convenient. You should look into DoD CAC, for example. Google Authenticator is nice but will never protect Secret information. I know this sounds way out of startup league, but it shouldn't; we should instead study what we can learn from such things instead of blanket advice like yours.

Reiterating: none = bad, TOTP = better, strong tokens/biometric/etc = best.

Re:SendGrid employee’s account was compromised and used to a... by StavrosK on Friday May 01, 2015 @03:38AM (#9470006)
The thread model TOTP addresses is someone having your password and being able to log in with just that. It's not to protect against people stealing the database, it's not to protect against people having root access to your phone, or anything like that.

Which of the solutions you mention works even if an attacker has actual physical access to the two-factor device?

Re:SendGrid employee’s account was compromised and used to a... by ak217 on Friday May 01, 2015 @03:51AM (#9470045)
> When done poorly (and most are), TOTP is basically no additional factor

TOTP protects against the most common threats, and is trivial to implement compared to other solutions you refer to.

Most of your complaints about TOTP security don't make sense under its threat model. Yes, if your phone is rooted, the TOTP secrets can be stolen. The point is that it's unlikely that both your phone and your laptop/point of access device both get compromised.

Re:SendGrid employee’s account was compromised and used to a... by minisu on Monday May 04, 2015 @06:17AM (#9485265)
Also worth mentioning is FIDO U2F. More convenient and more secure than TOTP.
Re:SendGrid employee’s account was compromised and used to a... by elliotanderson on Friday May 01, 2015 @03:45AM (#9470031)
> I've seen proofs of concept that trivially lift the secrets from Google Authenticator.

Android specific?

Re:SendGrid employee’s account was compromised and used to a... by tomjen3 on Friday May 01, 2015 @04:18AM (#9470108)
If the secrets are compromised, new secrets can be generated.
Re:SendGrid employee’s account was compromised and used to a... by dorfsmay on Friday May 01, 2015 @06:39AM (#9470505)
Absolutely, on the condition that you encrypt the device where you have installed gogle auth.

The reason people use authy and the like is because they make it simple to recover if you lose access to your device (lost, stolen, broken). My work around this is to take a screen cap of the QR codes and encrypt them with gpg. You could also save them inside a password manager (especially for less technical people).