Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"What about GK?" argument doesn't make sense. #1

Open
jpgoldberg opened this issue Feb 21, 2017 · 0 comments
Open

"What about GK?" argument doesn't make sense. #1

jpgoldberg opened this issue Feb 21, 2017 · 0 comments

Comments

@jpgoldberg
Copy link

Disclosure: I work for AgileBits, the makers of 1Password. I am also not sure whether a GitHub issue is where I should be trying to make the following point. If this is not the right place, please point me to where I should be saying this.

The section on "What about Gatekeeper" is technically correct, but it misses a more basic point: Any user with the motivation and skill to verify a PGP signature would also be capable of checking the CN of an Apple Developer codesigning certificate. In particular

codesign -v -d /Applications/1Password\ 6.app

will display the Identifier and the TeamIdentifier. That, plus Gatekeeper's insistence that the signature and certificate be valid does everything that a PGP or DSS check would do.

If you want to duplicate Gatekeeper's check and check the signing identifier, you can do this:

codesign -vvv R="identifier com.agilebits.onepassword4 and anchor trusted" /Applications/1Password\ 6.app

My contention is that anyone who is ready and able to verify a PGP signature for a download is capable of running those codesign commands, and so I am not sure what providing PGP or DSS signatures adds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant