I had the same problem they told they use the same Chromium engine like google Chrome and will not support XP and Vista just like Google Chrome .
Sadly still no Twitter video support…
and there will no support soon… it is a fact and real time experience :-X
To those asking about video playback, they appear to have forgotten to include Pepper Flash(PPAPI) in their latest update with no way to enable/install it. For new comers, Pepper Flash is the built in Chrome Flash player.
And to those asking about XP and/or Vista, Comodo uses Chrome’s source code which no longer supports those operating systems.
Flash Player cannot solve the Twitter videoplay problems,
Please see: “This browser does not support video playback.”
Only IceDragon can play that videos right now :-TD
I was responding to Jeruku’s post.
Comodo is working on it. All we can do is wait for the support to arrive.
New revisions (or are they called sub-versions?), please update the text and the hashes… The links are ok.
These are maintenance updates. I have updated the file hashes in the topic start.
There are no release notes for Dragon v48.12.18.248 and Chromodo v48.12.18.249 released (yet).
Got a funny issue looks like the about page needs fixed cause it says I have 48.12.18.249 which is the newest version for Chromodo, but I have Comodo Dragon, so seeing that version on the about page made me laugh. Apparently something went wrong in the Comodo Dragon updater or more likely you must have put up the Chromodo version up first, and forgot to change the version to the one for Comodo Dragon. So nice mistake, please fix.
Also are the vulnerabilities as mentioned by US-CERT for Chrome, present in Comodo Dragon as of since the latest update?
- The ImageInputType::ensurePrimaryContent function in WebKit/Source/core/html/forms/ImageInputType.cpp in Blink, as used in Google Chrome before 49.0.2623.87, does not properly maintain the user agent shadow DOM, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that leverage “type confusion.” NVD - CVE-2016-1643
- WebKit/Source/core/layout/LayoutObject.cpp in Blink, as used in Google Chrome before 49.0.2623.87, does not properly restrict relayout scheduling, which allows remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via a crafted HTML document. NVD - CVE-2016-1644
I adapted the topic start to reflect the proper version numbers of Chromodo and Dragon.
My Dragon installation just updated 2 the latest version (*.249) and it added ‘Comodo Secure DNS’ and changed my DNS settings due to that. I’ve NEVER used ‘Comodo Secure DNS’ before so… what’s going on… It’s was an easy fix but it shouldn’t have added it anyway.
Are the vulnerabilities mentioned by the US-CERT in that they found in Chrome, present in Comodo Dragon as of since the latest update?
- The ImageInputType::ensurePrimaryContent function in WebKit/Source/core/html/forms/ImageInputType.cpp in Blink, as used in Google Chrome before 49.0.2623.87, does not properly maintain the user agent shadow DOM, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that leverage “type confusion.” NVD - CVE-2016-1643
- WebKit/Source/core/layout/LayoutObject.cpp in Blink, as used in Google Chrome before 49.0.2623.87, does not properly restrict relayout scheduling, which allows remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via a crafted HTML document. NVD - CVE-2016-1644
Comodo does not fix issues with Chrome. So I would say no yes because the latest Dragon is based on a build of v48 (which is prior to 49.0.2623.87).
Read the words carefully for those reports:
Both (1) and (2) say “some file” as used in Blink then Chrome, or just in Chrome, before 49.0.2623.87 does have “these problems”.
Chromodo and Dragon are both based on Chromium 48, which is before 49.0.2623.87, so both Chromodo 48 and Dragon 48 do have these vulnerabilities.
I edited my post. I meant to say yes instead of no.
When I download this version from this link, SHA-256 in downloaded file is not 0B2C82734C45AA52E2FA772B400A1D10E65D2E8DE88042F25B724A824953045F. What I have to do to get right file with right SHA-256?
I see that when editing the topic start with the hashes for the latest installers I made an error. The SHA 256 hash should be: 1A93358B231853FE254F77A71E8CDC161770C8D3D62B89DD8A8297E12FC396BA
I have edited the topic start and it now shows the proper SHA 256 hash.
In case of doubt you can check the digital signature of the installer. If that is OK then the file is unaltered; it is the real deal.
What are differences between Chromodo and Comodo Dragon ?
From what I can tell, they are similar products although Dragon allows you to run in “virtual mode” (as long as CIS is installed).
