Created
September 16, 2014 17:10
-
-
Save ianchesal/3316a7fd5466e01871e6 to your computer and use it in GitHub Desktop.
Debugging 1Password extension problem with browser signature verification
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
○ → codesign -dvvv /Applications/Google\ Chrome.app | |
Executable=/Applications/Google Chrome.app/Contents/MacOS/Google Chrome | |
Identifier=com.google.Chrome | |
Format=bundle with Mach-O thin (i386) | |
CodeDirectory v=20100 size=186 flags=0x0(none) hashes=3+3 location=embedded | |
Hash type=sha1 size=20 | |
CDHash=a8d3a44cc2a7957e8d9cd9c6f6eb9124a7e4a9fd | |
Signature size=8507 | |
Authority=Developer ID Application: Google Inc. | |
Authority=Developer ID Certification Authority | |
Authority=Apple Root CA | |
Timestamp=Sep 3, 2014, 6:30:20 PM | |
Info.plist entries=33 | |
TeamIdentifier=not set | |
Sealed Resources version=1 rules=9 files=221 | |
Internal requirements count=1 size=132 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here's what I see in Console when the verification fails:
I'm going to try the Sophos whitelist change...