[If you are not subscribed to short explanations, please sign up. We forwarded the feed from the other podcast for a month.] Show Notes: Don’t re-use passwords across sites How do you even remember each password? Using a password scheme (MyPassw0rd-facebook.com) - This is a bad idea because password cracking software knows this trick and will compromise all of your accounts First: Use your password manager generator Chrome Built in / Firefox built in Cred Stuffing Password Rules WEIRD password rules (8 chars, what?!) Longer is Better *Sharing passwords Join our signal group. Find us for an invitation Email the show: hosts (at) shortexplanations (dot) com

[If you are not subscribed to short explanations, please sign up. We forwarded the feed from the other podcast for a month.] We’ve always recommended password managers. Both Tom and Chaim are using Bitwarden, but we have recommended LastPass in the past. In fact we’ve had LastPass on the old show a few times. On December 21 they explained a breach that caused user vaults to be lost. That is bad. We explain why we are now recommending that you should move. However, if the choice is LastPass or nothing, stick with LastPass. They have done more for protection than others, but the fact they are not keeping up with newish protocols is a cause for concern. No Free Tier Bad legacy security Poor(ish) Disclosure Join our signal group. Find us for an invitation Email the show: hosts (at) shortexplanations (dot) com

[If you are not subscribed to short explanations, please sign up. We forwarded the feed from the other podcast for a month.] Anytime you start a new project, your first goal is to have a backup. That’s what today’s episode is about. Things have changed since we covered it last, so here we go again. First figure out what you want to backup. It should be way less than before. Most of everything already lives somewhere else. Your bills, statements, and other things have homes somewhere else. You are probably subscribing to music and movies, so that is somewhere else. Basically your documents. We recommend a cloud provider. They are all good enough for most people. If you want something more advanced, we mention SyncThing, Restic, and Synology. Join our signal group. Find us for an inviation Email the show: hosts (at) shortexplanations (dot) com

Welcome to our new podcast. We are a beginner security podcast where we try to explain what is going on in the security world in an easy to understand way. Please join us. In this episode we explain why we’ve moved, and what we plan on doing with this show. Please stay, and join our signal group for more. email the show: hosts (at) shortexplanations (dot) com

This is our last podcast here on inThirty. We are moving to ShortExplanations. We are just letting you know we are moving, and how to follow us. Hopefully really soon (like next week) we will be up and running. https://www.shortexplanations.com @shortexplan on Twitter

Tech Portfolio:

First: What do you want to communicate and why?Are you trying to get a job?Are you trying to make a repository of knowledge?Are you just playing around?Are you making an archive?

GitHub/GitLabPersonal WebsiteProjectsLearnings/MusingsLinkedIn

Must-Haves:High-Quality Writing – Communicating effectively is highly-sought-after in businessEase of Navigation (especially for personal websites)Don’t clickbait (unless you’re trying to get a job at a clickbait news website)

Ideas:ResumeProjects you’re proud ofProjects you’ve failed at, but learned something and can communicate those learningsVolunteer workOpen-Source contributions (even if this is just documentation-related, that counts)Stack Overflow profile (if you’re proud of your scores)Reviews10:08 PM

In a March Madness style game, we use this bracket from TechDirt to discuss misunderstood legal brackets

Announcing Techdirt’s March Madness: Get Your Bracket For The Most Misunderstood Legal Concept

We continue our discussion on how to get a job in security by discussing what you should put on your resume. Don’t feel like you can’t even apply. We talk about things you can do.

We discuss ways stores, government, individuals, computers track you. What to watch for, and how to protect yourself.

Google decided to take away Gapps legacy for a lot of old members. This rubs us the wrong way. We discuss what can be done, and why you should consider being so reliant on companies that can just take services away. Update: Google says, we will allow users to keep legacy.