[20:16] <Chris____> Hi. I've been waiting almost 30 hours for my gpg key to show up on keyserver.ubuntu.com. Is that normal? I followed the instructions at http://packaging.ubuntu.com/html/getting-set-up.html#create-your-gpg-key
[20:17] <teward> Chris____: did you upload your key to there?
[20:17] <Chris____> teward: Yes, I ran `$ gpg --send-keys --keyserver keyserver.ubuntu.com <KEY ID>` like the instructions in the link say to do
[20:18] <teward> that should've shown up instantly, then, what's the key ID?  (I'm just running a search on it)
[20:21] <Chris____> 2039A298
[20:30] <teward> hm.  that's definitely an interesting issue.  It probably should have been there by now, you're right.
[20:31] <Chris____> I also tried uploading the ASCII-armored version at keyserver.ubuntu.com, but I get "unexpected POST request"
[20:52] <teward> Chris____: just finished talking to Canonical sysadmins, they indicated this is a known issue as a result of attempting to mitigate against a crit-levvel vuln
[20:53] <teward> they indicated you could "try again" with the upload, and it's down to 'timing' and 'luck' because otherwise you'll get upload failures
[20:55] <Chris____> Ok. Well, I appreciate the information. Is there a bug report I can track?
[20:57] <teward> Chris____: i don't have a bug tracking link for the mitigation status, sorry.  the issue upstream with the SKS Keyserver software doesn't have a fix, yet, but that's trackable at https://bitbucket.org/skskeyserver/sks-keyserver/issues/60/denial-of-service-via-large-uid-packets
[20:57] <teward> and what Canonical SAs are saying is "Try again, it'll eventually be accepted"
[20:57] <teward> they're working on a fix though, just no tracker or ETA for it yet
[20:58] <Chris____> Ok. Thanks for your help teward.
[20:58] <teward> yep.