I wrote this little guide for my aunt. Her email password got hacked a while back. If you don’t currently do something similar, you should!<\/p>\n
First, here is how to make a bad password<\/strong> that will get hacked:<\/p>\n Now here is how to make a good password that is easy to remember and won’t get hacked<\/strong>:<\/p>\n Change all your passwords to follow a pattern. Make the pattern something you can easily figure out but a password thief could never do.<\/p>\n That’s it!<\/p>\n Your final password should be between 9 and 12 characters. (some websites stupidly limit the length of your password, and you don’t want to have to use a different strategy on those sites, lest it be harder to remember.<\/p>\n You now have a REALLY GOOD PASSWORD<\/strong> that is REALLY EASY TO REMEMBER<\/strong> and REALLY HARD TO GUESS<\/strong>. And it’s DIFFERENT ON EVERY SITE<\/strong> so when one website gets hacked, the bad people don’t know your password on other sites!<\/p>\n ————————————————–<\/p>\n If you have gmail, I strongly<\/strong> recommend you turn on 2-step verification. Yes, it takes a little effort, but so does locking your front door when you go out.<\/p>\n Short story: last year I sat down at a public computer at City College. As I typed in my password, I got this chill, wondering if there might be a virus on the computer, sending my password off to some nefarious Russian hacker den or somesuch. So the first thing I did was enable 2-step verification. Yes, the bad people got my password. But my password strategy and 2-step verification protected me. Nuff said<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":" I wrote this little guide for my aunt. Her email password got hacked a while back. If you don’t currently do something similar, you should! First, here is how to make a bad password that will get hacked: Use a word that is in the dictionary, even if you r3place s0me l3tt3rs w1th number5 (that’s […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3303","post","type-post","status-publish","format-standard","hentry","category-general"],"_links":{"self":[{"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/posts\/3303","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/comments?post=3303"}],"version-history":[{"count":1,"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/posts\/3303\/revisions"}],"predecessor-version":[{"id":4462,"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/posts\/3303\/revisions\/4462"}],"wp:attachment":[{"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/media?parent=3303"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/categories?post=3303"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/tags?post=3303"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\n
\nHow to enable it<\/a>.
\nA friendly video that walks you through it.<\/a><\/p>\n
\nFlash forward 3 months to this ABC News article<\/a> that starts out “A computer virus found at the City College of San Francisco may have been part of an elaborate international scheme stealing students’ personal information for more than a decade.”<\/p>\n