There is something negative in exchange for the average tax payer, called: we prop up the difference because the bills still need to get paid. Teachers, public safety, roads, etc etc.

This is yet another example of how that thick, bought-and-paid-for tax code benefits those who bought and paid for it. That means most of us that thought that government fairness wasn't an oxymoron get another kick in the slats.

Remember to vote. And if in Chicagoland, often and frequently.

Think about it. They already know who you are unless you anonymously purchased a "drop" phone. With either GPS or LBS, they know where the phone's been. It was with you, likely. You fell asleep where you live, so that's your address, resolved to about 1m most places. There's a MAC address on the phone, very difficult to spoof. There are two more IDs on the phone, one as your EIMI or equiv, and other that's buried in a firmware-reachable mem location.

You drove by the sniffing cell towers on your way into the airport. If WiFi was on, it sniffed that, too. Up against a database linking users to cell, another easily done link says: whoa there, Chuck, you're on the no-way-Jose list. We're going to ask you to step into our office after we get the nekkid picture of you.

Yeah, I'm giving them too much credit, partly in humor. Such a scenario isn't outside of the realm of real possibility. Why use so much technology when you can mark ropes? Next they'll be weighing passengers with rugs made out of load cells so they can balance plane weights before you ever get to the bankrupt pizza maker on the next concourse.

Um, the line goes to here, so about X. If the line goes to there, ummm, y.

They just wanna check your MAC address to ensure you're not on the NoFly list so that they can handle your incarceration discretely.

More of a problem is finding 32-bit distros with updated apps that don't trigger CVE issues. Dusty Linux distros are almost as dangerous, as, dare I say it, old Windows releases.

Try an energy link and go check CVEs using the string openssh for starters. Kernel? No. All the crap in the back? Oh, yeah.

Some kids will become good and responsible coders, but not all kids. Some will be artists, musicians, mechanics, farmers, etc., and for the rest of the world that doesn't code, a heavy responsibility is placed on the FOSS community to do code reviews.

People don't compile at all. They download binaries, and they don't know the difference between an MD5, a SHA-x and a hole in the ground. Binaries therefore need special protection. Open Source doesn't mean anyone's actually looking at the code, and there needs to be peer review on critical components given with distros, but this isn't guaranteed to happen. Instead, there's an incredible bloat of stuff that we HOPE is good. An actual process might be better. What kind? Something more than Linus yelling at you.

I would agree with you, but we need to train them first so as to avoid the problems associated with the usual tech support issues. There are many that could easily qualify, including token devices, session-based tokens, even anonymized public keys. Many choices.

But businesses don't want the overhead, and no one seems to get punished except----> users when the info is breached or misused in any way. Nobody seems to get punished.

"Locks keep your friends out; your enemies have pick tools".

You can make anything up you want, but changing them frequently is the key to killing their usefulness when there are bulk thefts of passwords. These things go undetected for months. If you'd changed already, you're good-- unless the crack gets the deltas, too, which is unlikely.

Stupid passwords will still be stupid, but no use to go to incredible lengths unless your keys are extremely valuable-- then go to a Yubikey or another secondary auth. Key age is probably more critical than its ability to be dictionary attacked, IMHO.

Liberty exists rarely, anywhere.

You see, it might be Dubai, but the software will be perfected there, and it will migrate elsewhere. Slowly, it becomes acceptable in a conventional sense. Then it becomes "the norm".

A thousand cuts..... then a million.

Already here. One more intake method.

Depends on the jurisdiction and the procedures used THERE. How many stories about languishing in jails do you need to become reviled at the concept?

You forgot to mention the necessary sense of walking around: liberty. Even if you're a "positive", what of due process? Will you land in a jail, await a long process? How and who guarantees that you'll be then excluded if you're falsely positive? It's a slippery slope. Google has opened a Pandora's box of paranoia.

Will people stop traveling in fear of false-positives? Where are governments permitted to gnaw on their citizenry, privacy death by a thousand cuts?

Oh, the persecution complex, a martyr for ostensible blindness in capitalism maybe?

Victimized recently?

None of this is tough, and there is no science fiction, and the post cites oh, 10 CVEs in four years. My underwear has more than 10 CVEs in the past four years.

So maimed are these Tea Party software sweatshirt-wearing jokers that they're taking their bruised asses into BSD, and any place, anyplace but Linux.

No, they don't tell you about any of the actual features, they just cite covering their system's butts cause they can't kill -1. You can still hobby, still futz, still cobble with Linux. And you can run huge multi-core systems with very complex (o)virting, docker, ad infinitum while you learned a few new dependencies.

Those that compare all this to WIndows 9 know neither Linux or WIndows to make such an abrupt comparison. Adoption? It's not science fiction folks. It has similarities to how Solaris has evolved, and you can take a look at Solaris for some of the roots about WHY systemd. Go ahead and initd if you want. Nobody's stopping you. RH, Deb, etc, didn't pick this because it was stupid, or because they're part of a herd. All of them have strong egos, and they picked systemd because it's so NOT 1986.