Chromodo Browser Disables Key Web Security (thestack.com)
An anonymous reader writes: A Google Security Research update has claimed that Comodo's internet browser Chromodo, based on the open-source project Chromium, contains significant security failings and puts its users at risk. This week's Google alert suggested that the Chromodo browser – available as a standalone download, as well as part of the company's Security package – is less secure than it promises. According to analysis, the browser is disabling the Same Origin policy, hijacking DNS settings, and replacing shortcuts with Chromodo links, among other security violations.
There's a lot of Chromium and Firefox clones/forks by small teams that have certain targeted goals (better UI, different default settings, etc.), but I tend to avoid them; I figure that Google and Mozilla have world-class security experts working for them, whereas these little forks, even if competently done, do not and might introduce security holes by accident.
The same is also true for Linux distros--I advise people stick to the big ones (Debian, Ubuntu, Fedora/Red Hat/CentOS, Arch, Gentoo, SUSE, Tails) since they're thoroughly audited by security professionals, whereas those tiny little forks that do nothing but alter the UI probably aren't.
A shady browser that nobody has ever heard of is insecure? Who actually finds and installs this garbage besides the clueless and elderly?
Only the State obtains its revenue by coercion. - Murray Rothbard
How cute, thinks privacy exists on the internet
It doesn't. But why make it easier for them? At the very least, I get to opt out of those targeted ads.
Please do not read this sig. Thank you.
Wasn't this the company who gave us forged compromised certificates last year that installed malware on some pcs and phones?
They use a Lenovo style spearfish SSL MITM and replace legitimate certificates with their own. Gee no security problem with that. Kaspersky does the same too until you tell it not to scan HTTPS connections.
http://saveie6.com/
Can't comment because I'm not an Arch user and don't know much about it, but Greg Kroah-Hartman endorses it. I assume the world's second foremost kernel hacker knows enough about its security to do such a thing.
Cors in general is broken in general and for numerous reasons but on the client side more than server side.
Cors should be good. Cors could be good. But its primitive, difficult to write with when dealing with things such as Hybrid mobile development. If Web Services need a header acceptance policy solution then drop the same origin policy anyway and make it a totally separate thing. Make it so same origin resource sharing on the local side is blocked by default with an established white-listing system in place the also records management of how the resources are used would be even better!
You can get some of that that with the inspection tools on Chromium now but it would be far better if it was more definitive. E.G LocalStorage we could know when requests are made rather than just seeing the variables change.
Chromium is the open-source base for Chrome. There aren't really releases for it like Chrome. Most Linux distros will have a package for it, but on Windows you pretty much have to seek out and download one of the snapshots which isn't something most casual users are going to do*. So I'd assume anyone who has Chromium installed on Windows probably knows what they are doing.
*Or download someone else repackaging of it, like Chromodo.