Pa$$Word Doesn't Matter
I didn&#x27;t see anything in there that XKCD-936 wouldn&#x27;t fix. Combine such a password generation system (note: words MUST be chosen randomly for it to have value), with a password manager, and finally, don&#x27;t use the most commonly used operating system (hint, hint) - and you&#x27;ll likely be &quot;safe&quot;.<p>Perfectly safe? No. If the attackers are trying to get at you specifically, and know you use TempleOS - then they can target for that.<p>Practically safe? Yes.<p>Most attackers aren&#x27;t going at specific targets, and most people aren&#x27;t going to become or be &quot;specific targets&quot;. Most attackers are going for the lower hanging fruit, who use the most common software stacks, because they comprise the largest attack surface.<p>Get out of that &quot;rut&quot; - and your odds of being a victim will go down drastically. Of course, you&#x27;ll have to guard against potential phishing attacks and such, but most of those even will be trying exploits against the &quot;common stack&quot;.<p>What I find funny, though, is every time there is some kind of breach, the only time the software on the system is mentioned - if at all - is when it -isn&#x27;t- running on the &quot;common stack&quot;. I think this does a real disservice, and I wonder why it seems like this is what is happening. Maybe it&#x27;s just confirmation bias on my part?<p>But - if every time there was a ransomware attack, or some other kind of breach via phishing or whatnot - if the reporting said something to the effect that it occured on a system running the &quot;common stack&quot; - maybe those affected by the breach would think to themselves, &quot;Hmm - maybe we should be using this stack of software, it seems to get breached multiple times all over the world every year now for 25+ years running - maybe we should try something different?&quot;<p>But that wouldn&#x27;t bode well for that &quot;common stack&quot;, would it?<p>And certainly, I&#x27;m glad that the focus of the attackers is over there, and not on the software stack that I use daily at home, and less so on the stack I use for work. It means I am safer (except again, against a directed attack - and I am a nobody, so unlikely to be targeted). Not perfectly safe (after all, there have been the odd-duck attacks directed at these other platforms) - but safe enough.<p>Ultimately - especially on the level of the world as an &quot;attack surface&quot; - the greatest threat has come from this virtual mono-culture of the &quot;common stack&quot; of software. It has been a boon otherwise, but like any monoculture, it is subject to massive failures should an invader&#x2F;attacker succeed against its defenses. We see this kind of thing nearly every day. If your system is a part of a large enough such monoculture &quot;attack surface&quot;, you can expect to potentially become a victim.<p>But even on such system(s), using an XKCD-936 password generation scheme, coupled with a password manager - and then following other security &quot;best practices&quot; - you can ultimately limit your exposure. Not as great as coupling that with a lesser used software stack, but probably good enough for the common user.<p>The one area though (which is growing at a fast rate, and is being more frequently targeted) that a lot of this breaks down is that of &quot;walled gardens&quot;. While in theory such systems, with app stores and whatnot, should be able to keep issues to a minimum, in practice we have seen there are still vulnerabilities. With people more and more using these kinds of systems, mainly with their phones, it is proving to be a very ripe target for attackers. People don&#x27;t generally think of their phones as computers, and their attitudes and education (if they had any at all) from the PC world doesn&#x27;t translate or carry over. So their security on that front is lagging.<p>What I imagine we&#x27;ll see in the future (likely it already exists) is an underground market for &quot;popular apps&quot; - where programmers create certain apps that everyone wants (imagine if &quot;flappy bird&quot; had been this way?), downloaded millions of times, then the developer sells it on a black market list (code and everything) for others to continue to update with malware, etc - but the reputation on the app store is already established. If these updates to the code base are done slowly enough and stealthily enough (piecemeal), a large malware base attack surface could be realized; by the time it is found out and removed from the store, tons of users would already have it on their devices. Even if some uninstall it because they heard about it being such an issue, many if not most won&#x27;t - especially if it is very useful software otherwise. Alternatively, the software might exploit other weaknesses to install other bits in places that won&#x27;t be removed by an uninstall...<p>The problem is multi-faceted of course, but I have to disagree with the conclusion of the article that passwords are worthless.<p>Weak passwords are worthless. Easily guessable passwords are worthless. Reused passwords are worthless. But passwords, with a great enough length (XKCD-936), combined with a password manager, and ideally de-coupled from the &quot;common stack&quot; of software - and use of commonly known other security techniques (mainly, be wary of phishing attacks) - and you will greatly reduce your level of vulnerability, likely into the sub-single digit range.<p>Of course, the authors of this piece would not likely want to tell people that, for obvious reasons.