search

keybase / keybase-issues

A single repo for managing publicly recognized issues with the keybase client, installer, and website.
901 stars 37 forks source link

Keybase client disagrees with website on twitter/reddit proofs #1145

Open dlowe-net opened 9 years ago

dlowe-net commented 9 years ago

On the website, it shows that I have failed to validate against twitter or reddit, but if I attempt to prove again, the keybase command line client says that I have already proven.

ghost commented 9 years ago

I tried to keybase id dlowe you but it didn't show your Twitter/Reddit either. Also, your HTTP-Proof fails (File not found)

maxtaco commented 9 years ago

I'll take look

maxtaco commented 9 years ago

The server only rechecks every 6 hrs or so, but the client checks right away. That explains the divergence between the two views on your HTTP proof.

As for reproving, does the client give you the option to "overwrite"? If so, I would use that, that's basically what you want. You need to revoke the previous signature and generate a new one. Sorry if the terminology is confusing.

Oneiroi commented 9 years ago

I can confirm reddit proofs are presently failing;

Attempted a new one today via the command line tool;

proof is live here: https://www.reddit.com/r/KeybaseProofs/comments/2jf27n/my_keybase_proof_redditdbusby_keybaseoneiroi_s37l/

... Check Reddit now? [Y/n] Y warn: Didn't find the posted proof. Check Reddit again now? [Y/n] Y warn: Didn't find the posted proof. Check Reddit again now? [Y/n] Y warn: Didn't find the posted proof. Check Reddit again now? [Y/n]

Here's the error when running keybase id oneiroi

✖ "dbusby" on reddit: https://www.reddit.com/r/KeybaseProofs/comments/2jf27n/my_keybase_proof_redditdbusby_keybaseoneiroi_s37l/ (failed with code 205)

If this is a HTTP resp, 205 == reset content perhaps reddit is throttling checks for proofs?

maxtaco commented 9 years ago

This proof is truncated. There was an earlier issue on this.

Oneiroi commented 9 years ago

@maxtaco I see your comments per: https://github.com/keybase/keybase-issues/issues/953

The proof was issued via the command line tool keybase prove reddit

...

Please click on the following link to post to Reddit:

The content is from the resulting link of the 0.6.1 client

I've manually put the proof in place now

dlowe-net commented 9 years ago

This issue only addresses a situation in which a) A proof was attempted via the keybase command line client, b) the proof failed, and c) attempting to reprove generates a message that "You have already proved x", even though it failed. I understand what's going on now, but it's really confusing. As a short fix, the confirmation shouldn't imply a successful proof. The best thing would be if the reproving confirmation just shouldn't happen unless a the previous proof was successful.

malgorithms commented 9 years ago

hmm, @Oneiroi what browser handled the link for you?

Oneiroi commented 9 years ago

@malgorithms Chrome; though I think this may be more of a terminal issue where the link was only partially detected as a link for the "Open link" dialogue; copy pasting the link into the browser was fine; I then took the body content from the new post form and edited the original with the content.