FuN_KeY 0 Report post Posted February 13 (edited) Hello, For ~the past week enpass does not want to cooperate with my Chrome anymore. It says: "chrome.exe is trying to establish connection with its code signature unrecognized by Enpass. Do you allow Enpass to connect?" I am using the following versions: Chrome: 72.0.3626.96 (Official Build) (64-bit) Chrome plugin: 6.0.0.1 Enpass: 6.0.4 My chrome.exe seems pretty legit & signed, with code signature in place (SHA256: F6FA354889EF81AD521F1F0E4C9AFF4D54B95994573791C897A248F52B0479FD) Edited February 13 by FuN_KeY Quote Share this post Link to post Share on other sites
lilalinux 0 Report post Posted February 14 (edited) Same here with Chrome/OS X. This is a fresh Chrome Download from the official website. Previously I used an older version (which automatically updated itself every now and then, it had different hashes). Anyway, please get this shit fixed and setup automated tests for such cases! It's extremely frustrating and no, I won't disable the code signature check in enpass! Even if the problem is chrome's fault, setup automated tests and inform your customers or otherwise help them. Extension: 6.0.0.1 Chrome: Version 72.0.3626.109 (Offizieller Build) (64-Bit) Enpass: 6.0.5 (306) Signature: $ codesign -dv --verbose=4 /Applications/Google\ Chrome.app Executable=/Applications/Google Chrome.app/Contents/MacOS/Google Chrome Identifier=com.google.Chrome Format=app bundle with Mach-O thin (x86_64) CodeDirectory v=20200 size=337 flags=0x800(restrict) hashes=3+5 location=embedded VersionPlatform=1 VersionMin=657664 VersionSDK=658432 Hash type=sha256 size=32 CandidateCDHash sha1=6841688135c124e5229129d4e02d6f654083153e CandidateCDHash sha256=774d80ba76cc0218b9fe1c599b519b7917576fe5 Hash choices=sha1,sha256 Page size=4096 CDHash=774d80ba76cc0218b9fe1c599b519b7917576fe5 Signature size=8949 Authority=Developer ID Application: Google, Inc. (EQHXZ8M8AV) Authority=Developer ID Certification Authority Authority=Apple Root CA Timestamp=13.02.2019, 05:47:07 Info.plist entries=37 TeamIdentifier=EQHXZ8M8AV Sealed Resources version=2 rules=7 files=171 Internal requirements count=1 size=204 Edited February 14 by lilalinux Quote Share this post Link to post Share on other sites
Anshu kumar 306 Report post Posted February 15 Hey guys, I would like to share that recently, Google Chrome changed their signing certificate which leads to the failure of code signature verification in Enpass. We have implemented the fix and a new update will be rolled out asap. Meanwhile you can click Alllow button and continue. Thanks! Quote Share this post Link to post Share on other sites