Launchpad itself

GPG Key Fingerprint Not Loading in Launchpad

Asked by Stonepost

Hello All,
   I created and registered my key with ubuntu keyserver around 5pm this evening, it is now 10:30 and still receiving the unable to inport key message. I noticed that the web services were read only for Launchpad until 11:30 UTC - which is 6:30pm EST. Has this effected / still effecting Launchpad web services, and would this effect Inporting of Key Fingerprints?

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Brad Crittenden
Solved:
Last query:
Last reply:
Revision history for this message
Stonepost (shawnmsaling) said : 		#1

Hello,
 It has been aprox 13 hrs since I have registered my key with ubuntu keyserver, I am still unable to register my key fingerprint, any assistance will be appreciated.

Revision history for this message
Stonepost (shawnmsaling) said : 		#2

I have registered with pgp key server (ldap://keyserver.pgp.com over 1 hr ago, attempted to register my fingerprint on her and still receiving:

"Launchpad could not import your OpenPGP key
Did you enter your complete fingerprint correctly? (Help with fingerprints) Is your key in the Ubuntu keyserver yet? You may have to wait between ten minutes (if you pushed directly to the Ubuntu key server) and one hour (if you pushed your key to another server). (Help with publishing keys) "

Anyone else having this issue?

Revision history for this message
Stonepost (shawnmsaling) said : 		#3

Hope these help

Result from checking against keyserver.ubuntu:
"gpg --keyserver keyserver.ubuntu.com -n --recv-keys 250e3a975ca2f41d27c1787a4495657bf2c34a57
gpg: requesting key F2C34A57 from hkp server keyserver.ubuntu.com
gpg: key F2C34A57: "Shawn M. Saling <email address hidden>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1"

Result from checking against pgp keyserver:
"gpg --keyserver ldap://keyserver.pgp.com -n --recv-keys 250e3a975ca2f41d27c1787a4495657bf2c34a57
gpg: requesting key F2C34A57 from ldap server keyserver.pgp.com
gpg: key F2C34A57: "Shawn M. Saling <email address hidden>" 1 new signature
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 2011-06-27
gpg: Total number processed: 1
gpg: new signatures: 1"

Revision history for this message
Alison Pitt (londonali1010) said : 		#4

I can't help with an answer...I'm looking for one myself. I also uploaded my key to the Ubuntu keyserver on the 28th (and confirmed that it's there!), and I have tried several times to import it into Launchpad over the last two days, and I'm stumped! There's also an open bug over here: https://bugs.launchpad.net/launchpad-foundations/+bug/514074 that hasn't been answered yet.

Revision history for this message
Stonepost (shawnmsaling) said : 		#5

Thanks Alison, its hard sometimes to attempt to filter through questions and bugs. I do appreciate the heads up.

Revision history for this message
Brad Crittenden (bac) said : 		#6

Hi Stonepost I am looking into this for you. I'll report back when I have some information.

Revision history for this message
Brad Crittenden (bac) said : 		#7

It looks like there is an issue with the keyserver. I'm going to file a request that it be investigated further.

Revision history for this message
Best Brad Crittenden (bac) said : 		#8

Stonepost:

It looks like you have copied down your fingerprint incorrectly. Above you wrote:

250e3a975ca2f41d27c1787a4495657bf2c34a57 when your fingerprint is actually
250e3a975ca2f41d27c1757a4495657bf2c34a57
                                               ^-- discrepancy

Please try again with the correct fingerprint.

Note your test using the gpg command-line worked because it only uses the last bit of the fingerprint, f2c34a57 in your case, so the typo in the preceding portion went unnoticed.

Revision history for this message
Stonepost (shawnmsaling) said : 		#9

Thanks, didn't even think to check that - such a little defect causing all kinds of havoc.

Revision history for this message
Stonepost (shawnmsaling) said : 		#10

Thanks Brad Crittenden, that solved my question.