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

Use HKPS as default protocol for SKS keyservers #10

Closed
Diagoras opened this issue Mar 23, 2016 · 1 comment
Closed

Use HKPS as default protocol for SKS keyservers #10

Diagoras opened this issue Mar 23, 2016 · 1 comment
Labels
enhancement New feature or request.
Milestone

Comments

@Diagoras
Copy link
Contributor

Currently, the plugin uses the SKS keyserver pool as the default keyserver (good) but requests and receives the keys in plaintext (not as good). It would be nice if the default was HKPS instead, and if HKPS was handled with the same kind of custom scheme and port logic as HKP in the PGPKeysCache constructor in order to support other HKPS keyservers.

However, this would involve grabbing the CA certificate from https://sks-keyservers.net/sks-keyservers.netCA.pem in order to validate the SKS HKPS connections, which especially in Java is a huge pain.

@slawekjaranowski slawekjaranowski added the enhancement New feature or request. label Mar 23, 2016
slawekjaranowski added a commit that referenced this issue Mar 25, 2016
Diagoras added a commit to Diagoras/pgpverify-maven-plugin that referenced this issue Mar 26, 2016
slawekjaranowski added a commit that referenced this issue Mar 29, 2016
Now using SKS keyservers over HKPS to resolve issue #10
@slawekjaranowski
Copy link
Member

Resolved by #13

@slawekjaranowski slawekjaranowski added this to the v1.2 milestone Mar 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request.
Development

No branches or pull requests

2 participants