Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 2440 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Google Chrome Frame being detected as Google Chrome browser....

mikepiet

Even though you have a entry in browser-plugin section for the Google Chrome Frame, when I try to install the Google Chrom Frame standalone msi installer found here...

http://www.google.com/chromeframe/eula.html?msi=true

Sophos is blocking it and detecting it as Google Chrome browser. From my email notification...

File "C:\Program Files\Google\Update\Install\{A162139A-AA97-4DC8-8BAE-79FB94F308DE}\chrome_frame_installer.exe" of controlled application 'Google Chrome' (of type Internet browser) has been detected.

Please see that this is fixed as soon as possible.

:34901


This thread was automatically locked due to age.
Parents
  • 0

    Hello mikepiet,

    This is something that SophosLabs, the department who creates and maintains application identities investigated some months back. These are the results of their testing:

    Following extensive testing, Sophos engineers have verified that there is an irrevocable clash between detections of Google Chrome and Google Chrome Frame.

    This is due to the way in which identities are created and the shared components of Google Chrome and Google Chrome Frame.

     

    Google Chrome Frame has attributes which are a subset of the attributes of Google Chrome thus it is possible for Google Chrome Frame to be blocked and Google Chrome to be authorised. The opposite, however, is not the case. It is therefore not possible to block Google Chrome without causing Google Chrome Frame to be blocked. We apologise for the inconvenience this may cause.

    Support will create a knowledgebase article for future reference for any other customer who comes across this.

    Hope this helps,

    Dan Kirtley

    Product Manager

    :35053
Reply
  • 0

    Hello mikepiet,

    This is something that SophosLabs, the department who creates and maintains application identities investigated some months back. These are the results of their testing:

    Following extensive testing, Sophos engineers have verified that there is an irrevocable clash between detections of Google Chrome and Google Chrome Frame.

    This is due to the way in which identities are created and the shared components of Google Chrome and Google Chrome Frame.

     

    Google Chrome Frame has attributes which are a subset of the attributes of Google Chrome thus it is possible for Google Chrome Frame to be blocked and Google Chrome to be authorised. The opposite, however, is not the case. It is therefore not possible to block Google Chrome without causing Google Chrome Frame to be blocked. We apologise for the inconvenience this may cause.

    Support will create a knowledgebase article for future reference for any other customer who comes across this.

    Hope this helps,

    Dan Kirtley

    Product Manager

    :35053
Children
No Data