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

Bypassing restrictive proxy for keyserver #446

Conversation

mirmillo
Copy link
Contributor

Restrictive proxies on certain networks block access to port 11371 causing the gpg call to the keyserver to fail. Changing to use apt-key instead of gpg allows alternate ports, in this case using port 80, the same as the web UI for the Ubuntu Keyserver.

@jeremyfelt jeremyfelt added this to the 1.2 Release milestone Sep 19, 2014
@jeremyfelt
Copy link
Member

Thanks for the PR, @mirmillo! This sounds sane. I'm going to test it out a bit over the next week and then hopefully merge.

We're in the middle of a license transition to MIT. (see #346) Can you confirm whether you're ok licensing your contribution as MIT? Thanks!

@mirmillo
Copy link
Contributor Author

MIT license is perfect. Good choice.

Thanks

On Sep 19, 2014, at 12:26 AM, Jeremy Felt notifications@github.com wrote:

Thanks for the PR, @mirmillo! This sounds sane. I'm going to test it out a bit over the next week and then hopefully merge.

We're in the middle of a license transition to MIT. (see #346) Can you confirm whether you're ok licensing your contribution as MIT? Thanks!


Reply to this email directly or view it on GitHub.

@EHLOVader
Copy link
Contributor

It may be worth noting that I also took steps in my branch to silence some of the warnings from GPG. I am not sure if apt-key does this already but it may be worth it to limit the amount of red shown in the shell on start.

@jeremyfelt
Copy link
Member

@EHLOVader - As of this moment, no more red in the gpg stuff. :)

Thanks again @mirmillo!

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

Successfully merging this pull request may close these issues.

3 participants