Missing signature on gcswf32.dll (Flash) unfriendly to AppLocker whitelisting
Reported by brian.re...@gmail.com, Dec 3 2010
Version of Google Chrome (Wrench-> About Google Chrome):7.0.517.44 Version of MSI (if applicable): Using group policy settings? Yes Flash fails to run in Chrome when using AppLocker DLL rules, having white listed EXE and DLLs signed by GOOGLE INC. The issue is that the Flash player DLL distributed with Chrome is neither signed by Google nor Adobe. This makes it difficult to create a viable AppLocker ruleset that allows Chrome to run correctly out-of the box. The simplest fix would be to ensure that all DLLs distribued with Chrom are signned by Google. It would be OK if Flash were signed by Adobe but this would require a second whitelist entry for DLLs signed by Adobe. See also. http://thoughtfulcode.wordpress.com/2010/12/02/headbang-chrome-flash-and-applocker-dont-play-together/
Dec 3 2010,
Moving to Feature-Flash. Definitely does affect enteprises, but we should probably be signing the DLL regardless to avoid other problems (Antivirus?) everywhere.
Jun 24 2011,
I'm not sure when it started but gcswf32.dll comes with a valid Adobe digital signature in Chrome 12. Seems like this issue should be closed.
Nov 14 2011,
thanks for the report! Closing per the last comment.
Oct 13 2012,
This issue has been closed for some time. No one will pay attention to new comments. If you are seeing this bug or have new data, please click New Issue to start a new bug.
Mar 11 2013,
Apr 6 2013,
Apr 6 2013,
Sign in to add a comment