opengpg keys help gives incorrect protocol in instructions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Launchpad itself |
High
|
Unassigned |
Bug Description
https:/
here, in the Publishing your key > Step 3, there is "You may need to add http://
Related branches
- Brad Crittenden (community): Approve (code) on 2011-02-04
-
Diff: 45 lines (+5/-4)3 files modifiedlib/lp/code/interfaces/branch.py (+2/-1)
lib/lp/code/interfaces/branchmergeproposal.py (+2/-2)
lib/lp/registry/help/openpgp-keys.html (+1/-1)
summary: |
- keyserver protocol error in introducting gpg + keyserver protocol error in introducing gpg |
Changed in launchpad: | |
status: | New → Incomplete |
Robert Collins (lifeless) wrote : | #2 |
Confirmed with IS, port 11371 is hkp.
Changed in launchpad: | |
importance: | Undecided → High |
status: | Incomplete → Triaged |
tags: | added: trivial |
Shuo (tycable) wrote : | #3 |
Thanks
If I set the following line in the ~/.gnupg/gpg.conf
keyserver http://
then I will receive nothing when I type "gpg --recv-keys <keyID>" in the terminal
and when I type "gpg --search-keys <keyID>"
it will tell me "this kind of server does not support this operation"
though I know I can type "gpg --recv-keys --keyserver keyserver.
but I want to type less
If the line I set is
keyserver hkp://keyserver
then all well
Do you normally use an http proxy on your network?
Yes, I have a http proxy, however, though I turn off the proxy, the http:// protocol does not work when using command line.
And, I find that in the setting of the Application > Accessories > Passwords and Encryption Keys ( Lucid ), it is also the hkp:// protocol.
So, I think it should be hkp://
Right?
Martin Pool (mbp) wrote : | #6 |
As far as I know or can tell, hkp is basically just a protocol on top of http. Whichever one you use, gpg will send the same request. I think the only difference is that a url starting with http:// defaults to port 80 whereas one with the hkp scheme defaults to port 11371.
Thus http://
I think if you include the port number in your configuration, or if you tell gpg to use your proxy, you should be fine.
Changed in launchpad: | |
status: | Triaged → Invalid |
Robert Collins (lifeless) wrote : | #7 |
Martin, Shuo was fairly clear that changing only http->hkp made it work, and openpgp will accept hkp, and hkp is the stated protocol. Reopening.
Changed in launchpad: | |
status: | Invalid → Triaged |
summary: |
- keyserver protocol error in introducing gpg + opengpg keys help gives incorrect protocol in instructions |
Martin Pool (mbp) wrote : | #8 |
Shuo, my question is, what happens if you put
keyserver http://
into your configuration?
think it will work. Changing to use hkp only makes it accidentally work because that changes the default port. However, the launchpad help already tells you to set the port.
Shuo (tycable) wrote : | #9 |
Oh, sorry, I just forget to type the port here, I've type port in my configuration.
I'm so sorry. I will be more carefully from now on.
I will describe the situation in detail now:
1 ) if I put
keyserver http://
or
keyserver http://
or
keyserver http://
in my configuration file, when I use the following command
gpg --search-keys F73D6274
I will receive the following message each time
gpg: searching for "F73D6274" from http server keyserver.
gpgkeys: this keyserver type only supports key retrieval
gpg: keyserver internal error
gpg: keyserver search failed: keyserver error
when I use another command
gpg --recv-keys F73D6274
I will receive
when it comes with keyserver http://
gpg: requesting key F73D6274 from http server keyserver.
gpgkeys: no key data found for http://
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
when keyserver http://
gpg: requesting key F73D6274 from http server keyserver.
gpgkeys: no key data found for http://
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
when keyserver http://
gpg: requesting key F73D6274 from http server keyserver.
gpgkeys: no key data found for http://
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
2 ) if I put
keyserver hkp://keyserver
in my configuration file, when I use the following command
gpg --search-keys F73D6274
I will receive the following message
gpg: searching for "F73D6274" from hkp server keyserver.
gpg: key "F73D6274" not found on keyserver
however, when I use another command
gpg --recv-keys F73D6274
I will receive
gpg: requesting key F73D6274 from hkp server keyserver.
gpg: key F73D6274: "Shuo Li (GnuPG-1.4.11) <email address hidden>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
And when I command gpg --recv-keys BEEE6764 ( This is Martin's keyID )
I will receive
gpg: requesting key BEEE6764 from hkp server keyserver.
gpg: key BEEE6764: public key "Martin Pool <email address hidden>" imported
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: next trustdb check due at 2018-01-27
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
I've checked what I had written, wish it no wrong.
Martin Pool (mbp) wrote : | #10 |
Shuo, can you please paste the output of
sudo sh -c 'echo $http_proxy'
and also tell me if you have a proxy set in ~/.gnupg/gpg.conf
Martin Pool (mbp) wrote : | #11 |
I think this is an instance of bug 712812
Shuo (tycable) wrote : | #12 |
Martin, the command returns a blank line.
Do you mean, I should have an http_proxy?
I don't need to have a proxy to access Launchpad.
And I don't set proxy in my gpg.conf.
Martin Pool (mbp) wrote : | #13 |
Shuo, you're quite right and I was confused. We do indeed need to say hkp rather than http in the instructions.
tags: | added: docs help |
Changed in launchpad: | |
assignee: | nobody → Curtis Hovey (sinzui) |
tags: | added: gpg |
Changed in launchpad: | |
status: | Triaged → In Progress |
Changed in launchpad: | |
milestone: | none → 11.02 |
Launchpad QA Bot (lpqabot) wrote : | #14 |
Fixed in stable r12332 <http://
tags: | added: qa-needstesting |
Changed in launchpad: | |
status: | In Progress → Fix Committed |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
Changed in launchpad: | |
assignee: | Curtis Hovey (sinzui) → nobody |
Why do you think that? whats happening when you try?