Google Experiment Tests Top 5 Browsers, Finds Safari Riddled With Security Bugs (bleepingcomputer.com)
An anonymous reader writes from a report via Bleeping Computer: The Project Zero team at Google has created a new tool for testing browser DOM engines and has unleashed it on today's top five browsers, finding most bugs in Apple's Safari. Results showed that Safari had by far the worst DOM engine, with 17 new bugs discovered after Fratric's test. Second was Edge with 6, then IE and Firefox with 4, and last was Chrome with only 2 new issues. The tests were carried out with a new fuzzing tool created by Google engineers named Domato, also open-sourced on GitHub. This is the third fuzzing tool Google creates and releases into open-source after OSS-Fuzz and syzkaller. Researchers focused on testing DOM engines for vulnerabilities because they expect them to be the next target for browser exploitation after Flash reaches end-of-life in 2020.
Turn off javascript and related scripting shit.
Google finds their own browser is best. News at 11.
it's shit, the new IE6.
what a DOM engine is.
Safari is Apple's IE 6 of this decade. It hasn't been updated in a long time and they can no longer piggy back both Google and Konqueror for new code since Chrome forked -webkit with -blink.
I worked for a famous software supporting their cloud software. Safari was the one browser which always had trouble with even drag and dropping files. Something rudimentary in the HTML 5 standard. Even IE 9 from 2011 can easily support this.
Sometimes Safari would work. Sometimes it would not and the Apple users always get mad at us for some reason never blaming their shitty browser.
http://saveie6.com/
Seriously? They tested IE but not other browsers?
I mean, I get it, IE still has a bigger user base than many other third party browser out there... but come on!
I can't even get it to run anymore. Piece of shit.
I can't believe so many of you are such zealots when it comes to your web browser of choice.
#DeleteChrome
This is a good retaliation against the new feature of Safari that undermines Google AdWords snooping mechanisms (tracking cookies). Apple may have good intentions (I like the way they started to fight against creepy ads) but they have to think how to make a Safari a good browser again. They have to find a way to go further, after the webkit fork.
Next move?
Adblock can't do 14 things hosts do:
1.) Protect vs. bad sites (past ads)
2.) Protect vs. botnet C&C servers
3.) Protect vs. downed DNS (reliability)
4.) Protect vs. DNS redirect poisoned/downed dns
5.) Protect vs. trackers
6.) Protect vs. spam payloads
7.) Protect vs. phish payloads
8.) Protect vs. caps
9.) Get past dns blocks
10.) Keep off dns request logs
11.) Speed up 2 ways (adblocks & hardcodes)
12.) Work on anything webbound multiplatform.
13.) Ez data edit
14.) Block ads more efficiently in cpu/ram/I-O use
* BEST hosts file maker = APK Hosts File Engine 9.0++ SR-7 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/
APK
P.S.=> Ab+ does less vs. hosts less efficiently (a 151mb memory hog http://cdn.ghacks.net/wp-conte...)
ClarityRay defeats it
Ab+'s bribed not to work by default http://www.businessinsider.com...
AdBlock's SLOWER: http://superuser.com/questions...
Found already a couple of other crashes with the tool, some of them security related.
Google testers could find no security bugs whatsoever in Chrome. "It's a fucking rock," said one tester.
It looks like all of the Safari bugs were fixed earlier this year...
I print, therefore I am.
And yet Safari is the most secure from advertiser tracking now that it intelligently blocks cookies from domains you donâ(TM)t actually visit. So sure, Safari offers the least security to Googleâ(TM)s business model, but itâ(TM)s keeping secure what I want secure, so I plan to keep using it anyway.
So, it is interesting that they do not mention versions that they used of any of these browsers, unless I missed that detail. They only mention 'currently released'
But much more odd "Instead of fuzzing Safari directly, which would require Apple hardware, we instead used WebKitGTK+ which we could run on internal (Linux-based) infrastructure". Google does not have a Mac, anywhere?
So they did not run this as a user would, or in fact a proper OS X Safari release build at all. Ok, seems legit...
This from the company that gets hurt the most by Safari beginning to block tracking of users through advertising blocking mechanisms. Maybe they were looking at ways to bypass that?
...and Chrysler has the second most. Ford had none.
Film at eleven.