On Cybersecurity and Being Targeted
I applaud the fast response, especially contacting a security engineer to be removed from the GitHub organization. One particular bit stuck out to me.<p>&gt;&gt;<i>In this instance, though, the attack vector was DNS. My account at the not-so-incredibly-common DNSimple.com did not use a highly secure password. I didn’t think it was necessary, as in my mind, the only reason that the security of an account like that would be at risk would be if I was the explicit target of an attack. Once again, I thought to myself “That’s something that only happens to other people”.</i><p>Kenneth used a randomly generated password and two-factor authentication on his GitHub account, which is great! But on DNSimple he made the decision to forego better security because it seemed unlikely to be a target.<p>It is not enough to use <i>some</i> strong passwords for the things you <i>think</i> are sensitive. Every weak password is a weak link in your total identity chain.<p>The best way to use a password manager is to never give yourself authority to make passwords unless they are randomly generated. Even if the site or account in question appears innocuous or insignificant, even if it does not allow you to make a password of your manager&#x27;s default strength, <i>commit yourself to going through this process 100% of the time.</i><p>Yes, it&#x27;s a usability pain to constantly use a browser extension to log in. But that pain is nothing compared to the stress of a compromise or targeted attack.<p>Until password management or authentication are substantially overhauled on the web, the most optimal solution for protecting yourself is constant, militant vigilance with passwords. I don&#x27;t know any of my passwords at all, and what&#x27;s more, I even have randomly generated answers to security questions.<p>Also, where possible, use two-factor authentication. You can use SMS, Authy, Google Authenticator, a Yubikey, whatever. Just turn the damn thing on and use it if it&#x27;s available to you.