Out-Of-the-Box Exploitation Possible On PCs From Top 5 OEMs (arstechnica.com)
According to a report published by two-factor authentication service Duo Security, third-party updating tools installed by Dell, HP, Lenovo, Acer, and Asus (the top five Windows PC OEMs) are exposing their devices to man-in-the-middle attacks. Dan Goodin, reports for Ars Technica: The updaters frequently expose their programming interfaces, making them easy to reverse engineer. Even worse, the updaters frequently fail to use transport layer security encryption properly, if at all. As a result, PCs from all five makers are vulnerable to exploits that allow attackers to install malware.Duo Security adds: Hacking in practice means taking the path of least resistance, and OEM software is often a weak link in the chain. All of the sexy exploit mitigations, desktop firewalls, and safe browsing enhancements can't protect you when an OEM vendor cripples them with pre-installed software.
Why that kind of crap happening on both smartphones and computers, is there anyone still surprised why Apple didn't want carriers to install their own crapware on iPhones?
OEM Rescue Kit
That's a job for the TSA !!
App apping devices running Appdows 10 are 100% secure and appy because they ONLY app apps, unlike LUDDITE PCs that let hackers pwn them with LUDDITE software!
Apps!
You'd have to be a moron to buy anything from Dell or Lenovo by choice, after the root certificate crap they both pulled.
So what Windows OEMs are left that don't fuck up their computers? Let's start by eliminating the five mentioned in TFS, and also Microsoft, Sony and Samsung because they have a history of abusing their customers and have terrible support. That leaves us with... LG, Toshiba and MSI. And a bunch of tiny companies.
No wonder the PC market is declining so hard.
made more from pre-installed software, especially games, than we did from the hardware, this problem will never go away. The closer to malware that the software is, generally the more profitable it is.
are the OEMs getting paid to put this crap on there, is it just that cheap to let someone else do it (and buy some liability insurance), or a combination of the two?
Step 1: buy the box Step 2: wipe, install clean OS
I had had enough with bloatware years ago, so now it's nothing but OEM Windows (if not Linux) for me.
The updaters frequently expose their programming interfaces
The dirty beggars.
systemd is Roko's Basilisk.
I don't want to use Windows. I don't really want to use OS X, either. But once I've excluded those, my only other options are Linux and FreeBSD.
Linux happens to support my hardware better, so I've tried to use it. But modern Linux distros are just so awful.
It wasn't always this way. I had some great experiences using Linux in the late 90s and early 2000s. But when I tried Linux earlier this year, I ran into all sorts of problems with systemd. I'm clearly not alone, given how many bug reports and mailing list emails from other people I read when trying to solve my problems!
Shit, it was only a few days ago that I saw a story here at /. about how systemd now breaks screen and tmux! That's fucking unbelievable!
To make matters worse, it's like all of the major Linux distros have switched to systemd, too. Unless I want to relegate myself to niche distros like Slackware or Gentoo, or use insecure outdated versions of other distros, I'm forced to use systemd! Well none of those are options for me.
After much fighting with systemd, I found myself face to face with GNOME 3. What a frigging disaster! I've used countless desktop environments since the 1980s, and GNOME 3 is the worst I've ever seen. Everything about it is just plain awful, in my opinion. I found it to be a usability nightmare.
Now I think I'll just get a Mac. It's not my first choice, but thanks to how the major Linux distros have ruined themselves I have no choice.
Let's put this into perspective.
If your attacker can either A) hack into the Internet back-end routers; or B) physically colocate on your private network, he can hack your PC during an update check.
If we assume update checks are sufficiently frequent, then your most likely attack is from a PC on your network--a neighbor or white van that's connected to your wifi, assuming it's not encrypted with a non-trivial password ("lemonade_ghost_riders" would keep the NSA out if they had to brute-force your WPA2--don't use that password; it's public knowledge now).
The only reasonable scenario is a targeted attack by an infected machine on coffee-shop wifi. Such an attack would need to connect to the local wifi, spoof ARP packets of the router at your particular device, spoof ARP packets of your device at the router, and interpose itself. Not impossible, but very much not reasonable if two competing devices are attempting to do it.
Support my political activism on Patreon.
expose their programming interfaces, making them easy to reverse engineer
I fail to see how this statement should ever be construed as bad. If done properly, knowing the programming interfaces and how they work should in no way compromise the security of the system.
Also, while it's good that the new Lenovo utility employs all the security best practices and it wouldn't hurt to have signed manifests, if TLS is working properly the signed manifest seems likely to be a mostly redundant security feature.
XML is like violence. If it doesn't solve the problem, use more.
Put Windows onto a USB stick.
Download Double Driver and put on stick.
Back up the drivers using Double Driver onto a folder on the aforementioned stick.
Start the Windows 10 install. Go have dinner.
Copy the drivers to the hard drive.
Reinstall any drivers from the folder on the drive as and when you need them. I tend to find the default wireless one provided by Microsoft to be rather flakey.
Avantslash - View Slashdot cleanly on your mobile phone.
I wasn't even worried about security from OEM updaters; I just don't want to spend the time, bandwidth and CPU cycles checking two sources - especially since any driver or OS patches are likely to come from Microsoft first, and I wouldn't trust an OEM to correctly relay such patches to me. Also, I don't want the OEM "updating" me to an older downgraded version of a driver or patch because they just put it up yesterday while Microsoft has had the patch up for weeks or even months.
He said "hacking".
Anyhow, another good example of how computer security industry posers are abusing words and failing to heeding the consequences. Here, it sounds very much like this particular loser is advocating security by obscurity and "locking down" things such that end-users end up with even less control... but not more security. Good job, "researcher"!
No such thing as a clean install of Windows anymore.
Linux is also fine for the headless box in the closet performing server functionality or providing a console environment (yeah, its still useful for some thing). Sometimes I have cpu intensive console jobs that will be running for days at a time and I'd rather not be running them on a laptop. Such headless boxes are generally an old PC that's been retired from development use.
Apple is also a nice way to get a clean MS Windows environment via Boot Camp. Its an end user installation of Windows, like a build-your-own-PC, so its a fairly clean install.
I've been building my own PCs from parts since 386 days. I've only had a small fraction of the Windows problems others complain about. Even good Linux compatibility. OK, it may help that the "No" and "Cancel" buttons are my friends, especially when someone is generously offering to install something for me. And I look out for those sneaky checkboxes on the installers of products I do want, sneaky checkboxes that enable the installation of some 3rd party crapware. On second thought some of the crapware is not 3rd party, I also do custom installs not default installs to catch that.
So yeah, 3rd party bundling is the source of much trouble, whether at the PC factory or in a software installer.
https://tech.slashdot.org/comments.pl?sid=9179991&cid=52224549
Use Windows for your games until every game developer tells Microsoft to fuck off and codes for Linux. For everything else, see link I pasted above.
Microsoft tried to make multi-booting a hassle but it's not. Secure boot is a name. It is not a secure boot. Not only is Windows not secure when you bring your retail PC home, it is either Windows 10 Global Mother Fucking Spyware edition out of the box... or it's a 7/8 that goes full Global Mother Fucking Spyware as soon as you let it update.
Bill has enough money to write a decent fucking OS.. from scratch. Ask the US gov why his shit is spyware, why Google tracks, why Facebook profiles, etc.
Cunts. Wrap it up. dabbbft.
Then Windows 10 proceeds to install the OEM crapware automatically, since it is embedded in the system BIOS.