Google Will Block Third-Party Software From Injecting Code Into Chrome (bleepingcomputer.com)
Catalin Cimpanu, writing for BleepingComputer: Google has laid out a plan for blocking third-party applications from injecting code into the Chrome browser. The most impacted by this change are antivirus and other security products that often inject code into the user's local browser process to intercept and scan for malware, phishing pages, and other threats. Google says these changes will take place in three main phases over the next 14 months. Phase 1: In April 2018, Chrome 66 will begin showing affected users a warning after a crash, alerting them that other software is injecting code into Chrome and guiding them to update or remove that software. Phase 2: In July 2018, Chrome 68 will begin blocking third-party software from injecting into Chrome processes. If this blocking prevents Chrome from starting, Chrome will restart and allow the injection, but also show a warning that guides the user to remove the software. Phase 3: In January 2019, Chrome 72 will remove this accommodation and always block code injection.
Perhaps I am misunderstanding the affect of not allowing any injected code into the browser. The article didn't say what google would do to prevent users from malicious sites, as currently antivirus software does. Does this mean we are back to square one?
I've always said English was my second language. Had Romeo and Juliet been written in C, I might have understood it.
What's the difference between "plugging in" and "injecting"? Spin!
Availability of plugins is good, threat of injections is terrifying. The technically-important differences? I don't see any...
In Soviet Washington the swamp drains you.
This could be reasonable, but only if there is an API to allow plugins to scan downloadable content. Forcing the use of an API rather than injecting code would be safer, allow Chrome to monitor software causing delays, and make the system more stable. Does anyone know if this is possible via official APIs?
...that they would block injecting javascript code from a gazillion of 3d party sites, just to display one fucking page of text.
Google's next new feature will be to require users to raise their hand and ask permission before typing a URL in the address bar. If you aren't clicking a link in a Google search result page you're just asking for trouble!
"A person is smart. People are dumb, panicky dangerous animals and you know it." - K
Considering how much Google injects into other processes.
What the heck am I going to do? Use the Yahoo toolbar? Jeez, they always release bad news on a Friday.
I love it. I wish other software vendors would do a better job and informing users as to the root cause of issues they're seeing. More information is better. I don't care if something like "Please wait" or "oops, sorry" tested as being friendlier. I want information!
... first-party injection.
It little behooves the best of us to comment on the rest of us.
Anything that needs to inject itself into an otherwise secure boundary between processes and sniff all of a user's sensitive data in order to "protect" them is not, in fact, protecting them.
People rail on Google for harvesting all of a user's data, but they are in fact quite detailed and honest about exactly what they're collecting, and it is not as nightmarish as the tinfoilers want to believe.
You know who DOES collect lots of unnecessary data under the guise of user protection? DING DING DING, the correct answer is: AV software that injects itself into Chrome!
I am not aware of any method whereby a process is guaranteed the ability to defend itself from any and all such attacks at least in Windows.
Sure there are things you can do on the margins yet it's not like third parties doing the injecting are stupid and have not already invested significant resources into their work. I wonder how effective this will actually be in real life or if it will become just another pointless unwinnable evolution between adversaries.
That's fycking priceless coming from them.
On Chrome stable, I've had to fix several of these issues over the years:
Total Profile corruption
Browser failing to start after update
Updates crashing mid-update
Versions of browser that had insane memory leaks. (Caused by any graphical update or timers)
Versions where Google Play didn't work.
versions where extensions wouldn't install
UIs of windows behind bleeding through over the top of Chrome. (STILL happens on some current versions on some computers!)
Chrome for Android, most recent update for it, has so god damn many bugs it isn't funny. There's a persistent issue with Offline mode being forced when browser recovers from close. Only fix is copy address, close, new tab, paste & enter.
Speaking of URLs, impossible to edit them now, it forces the Search link on you rather thsn default direct load. Only fix I found was removing the protocol.
File saves no longer allow renames. The UI doesn't even show unless you go to other tab and back again.
I've deleted the shit thing permanently. It's insufferable having to find workarounds because retards can't do BASIC tests.
None of these were external plugins or injections. All were forcibly disabled and these issues persisted.
All across various OSes from WinXP to Win10, Android, and hardware configs.
Go fuck your 15%, your trash college-tier developers cause more issues than anyone else.
So they will add some commands, that will check if the list of commands has been modified, TO their list of commands, . --.--
And they expect the user to, who, remember, is the one to instruct his CPU to execute their list of commands (Chrome), to fully honor that? Even when he also instructed his CPU to run another list of commands (e.g. anti-virus) he cares about, and instructed the master list of commands (OS) to not hinder that other list from telling it to alter any other lists to be executed on said CPU?
Yeah. That will happen. --.--
See subject & NEW APK Hosts File Engine 10++ 32/64-bit https://www.google.com/search?hl=en&source=hp&biw=&bih=&q=%22APK+Hosts+File+Engine%22+and+%22start64%22&btnG=Google+Search&gbv=1/
Ads/script/malware rob speed/security/privacy/bandwidth.
Hosts add speed (via hardcodes/adblocks), security (vs. bad sites/malware/poisoned dns), reliability (vs. dns down), & anonymity (vs. dns requestlogs/trackers).
Less power/cpu/ram + IO use vs. DNS/routers/addons/antivirus + less security bugs/complexity & faster vs. addons/routers/remote dns!
Avoids DNSChangers in routers/IP settings & dns redirect (99++% of ISP DNS != patched vs. it) + DNS tracking & lighten DNS load & resolve faster via local RAM!
* Via what u NATIVELY have in a FASTER kernelmode IP stack (does more w/ less).
APK
P.S. - Safe https://www.virustotal.com/en/file/e01211ca36aa02e923f20adee0a3c4f5d5187dc65bdf1c997b3da3c2b0745425/analysis/1433430542/ (self checking vs. infection of it built-in)
MAYBE ASLR would help but not sure vs. DLL injection - it does after all change load address to 'random' locations & to 'hook' a process you need to know it's startpoint in memory.
See subject & afaik it's how 'whitelists' are being beaten by the badguys out there (DLL injection or hiding under services in Windows) & ASLR has been defeated before too.
* LoadLibrary functions for std. "oldschool" non-OLE .dlls have an export table & if your app starts calling the exported functions from a DLL, like they do OS apis? I don't know what to tell you - sorry. Maybe others do.
(OLE DLL's though 'marshalled' by GUID (globally unique identifiers) wouldn't be much diff. except for HOW they are called (done to stop DLL Hell/Version of lib/dll mismatches if they are loaded from outside the .exe calling them's folder (say %WinDir%\system32 or another %PATH% folder, & iirc, whatever it sees 1st outside the program's own folder it uses w/ std. non-OLE dlls).
In my hosts engine @ least, on DISK? It can't be attached to @ tail of the .exe to alter jump tables @ least (like oldschool TRUE viruses did) but in memory? ASLR = my best bet & what's below too.
APK
P.S.=> There's also a BOATLOAD of added calling rules that the registry iirc, has rules lists on & governs (perhaps looking up "DLL CALLING CONVENTIONS" that goes past local folder & %PATH% + OLE marshalling, iirc, they govern std. oldschool dll loading (vs. OLE type or ActiveX) some & will help you more (seems to 'ring a bell' here), but I don't recall the exact sections - but I don't think it can help either really - on a FINAL note? Man, lol - I haven't thought about this in a decade or more... apk
Your arrogance is disgusting.