-
Notifications
You must be signed in to change notification settings - Fork 37
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
Unable to prove twitter / github #682
Comments
I'll take a look, thanks.... |
Can you send me the output of Thanks.... |
There's something funky about your key, for some reason we're not recognizing your subkeys... Looking further into it.... |
Thanks. FWIW, I've changed primary UIDs in the past, not sure if that could impact things. |
Your subkey has the "critical flag" set on one of its subpacket signatures. Never knew about that feature! I'll have a fix in about 3 hours, gotta run out for a bit. |
Awesome, thanks! On Thu, May 1, 2014 at 12:17 PM, Maxwell Krohn notifications@gh.neting.ccwrote:
|
Honestly, I'm not quite sure if it's been fixed, since I can't reproduce your problem without your secret key. However, it might be fixed? The first thing I'd try is a twitter proof again. If that doesn't work, you might have to reupload your key and try it again. Let me know, and thanks for your patience! |
Success! Thanks for the quick work! |
EXCELLENT. So relieved it worked! Thank you for the helpful feedback. |
First ran into this problem when attempting to verify my public key via the web UI, but was able to overcome that through CLI
keybase push
.However ran into this again when attempting to prove twitter and github. For reference, I'm https://keybase.io/djhalliday. When running
keybase prove twitter
, here's the output / error:The text was updated successfully, but these errors were encountered: