News for hackers. Stuff that matters.
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...