"they would never get convicted on anything close to CFAA levels."
The amount of 'negligence' this amounts to (hijacking EVERY type of traffic, including VPN) leaves them no room. They should've discovered this in a basic software audit. It took some random joe like 8-12 hours to crack this and make a program to sniff the traffic of EVERY computer with this stuff installed, and log the traffic.
Don't have the TIME?!?
It takes like 15 minutes to build a system from base components if you're handy with a hex driver (for standoff installation) and a screwdriver for the rest of the system.
It takes longer to cook a pot of rice.
"a decent, 7200 RPM, SSD"
One of those terms does not belong. I'll leave it as an exercise to you as to which one.
It's been proven that in many cases emulating/virtualizing is much faster even in running software.
But you probably are to young to remember when at one point and time WINE was giving games better Linux performance versus their native Windows version - upwards of a 10% increase in framerate.
I've had several shit runs with Toshiba recently. Let's see...
Newer Toshiba - 64-bit system - dual core, Intel 965, HARD LIMIT TWO GIGS OF RAM.
Older Toshiba - 32-bit system - dual core, Overclockable Intel 945 (and it stomps the shit out of the 965 once brought to the original design spec clock speed of 400MHz vs 166 MHz and does so with almost ZERO increase in thermals) and can have a maximum of 4GB of RAM.
That's pretty shitty as far as I'm concerned. Thoughtless hardware limitations, newer hardware that's WEAKER than a prior-gen model FOR MORE CASH, and their DC jacks fucking SUCK (I've just hard-soldered the power adapters to the board to fix that problem.)
Their batteries are equally shit, more prone to heat degradation even moreso than HP, and HP is the king of hot fucking laptops.
"Yes, using the BIOS to flash the BIOS will definately remove any malware.
Oh wait....."
While you jest, this is how we used to fix broken BIOS - swap with a known good one that has had it's contents dumped, boot the machine, remove BIOS, insert briced BIOS chip, re-flash with the known good image ripped from the boot BIOS.
In fact, that's how many systems operate today, as they come with a secondary backup BIOS.
Since this thing tries to infect the Cert Store each browser utilizes, removing the stuff from the Windows Cert Store will not remove the stuff in Thunderbird, FF, or Opera. Those are still infected and vulnerable.
Looks like a full DBAN zero-out format is the only way to go.
Apparently you can't follow the conversation.
Try reading at my first post and working your way down the thread, instead of assuming you know full-well what is being discussed. It's obvious you missed some critical stuff.
http://imgur.com/H8459Z3,87zOr...
Oh how quickly you changed your original statement from January to February.
Good thing we can screencap and HTML-rip your entire site for the proof, Lenovo.
Still doesn't absolve Lenovo of failing to do proper audit/review.
http://marcrogers.org/2015/02/...
And *NOW* Lenovo is trying to CYA more by issuing a 'security advisry' for the software:
Chrome fails more than 50% of the time when it crashes on JS on anime sites I view. Whole browser locks up. Chrome can't even deliver a warning.
Also, Chrome's default security sucks.
You apparently don't know how to read.
It injects into FF's store. Not the fucking OS.
Re-read, comprehend, understand, then try your comment again.
https://forums.lenovo.com/t5/W...
Registry entries are there even on laptops from 2011.
So this has likely been in planning stages for years.
Considering it's bypassing BANK security stuff as well as anything else using SSL...
Well, the execs won't see jail time - they're in fucking China.
"Really guys? This is on the Windows side"
Nope, just tried using the injection code that the malware has for FireFox under Linux (Ubuntu) - it works and injects into FF's certificate store.
Perhaps you should do some of the work yourself instead of spouting off nonsense.
The flow chart is a most thoroughly oversold piece of program documentation. -- Frederick Brooks, "The Mythical Man Month"
