http / https proof not functioning about proofs HOT 8 CLOSED

@oconnor663 The client gets a hint of where to look from the server and only looks there. The server tries both locations but only until it finds a success. I guess when it starts failing the server only rechecks from its hint.

@fhorlaville The simplest thing to do until we make this better is to just revoke/redo the domain proof.

This is the same issue as keybase/keybase-issues#2966

from proofs.

keybase id fhorlaville is failing too. In my logs (keybase -d id -s fhorlaville) I only see the attempt to hit https://www.tamsoftware.info/.well-known/keybase.txt

2017-05-03T18:56:13.853660-04:00 ▶ [DEBU keybase log.go:30] 10d - API GET https://www.tamsoftware.info/.well-known/keybase.txt: err=ERROR: 404 Not Found, status="404 Not Found", jsonBytes=0 [tags:ID2=i8-KmHlNgeHC,API=Y2kdgRTAIcDh]
✔ Proof for www.tamsoftware.info failed: 404 Not Found (code=240)

@mlsteele, do you know if there's a PVL-related reason we wouldn't also be hitting https://www.tamsoftware.info/keybase.txt?

from proofs.

Thanks a lot, @oconnor663 and @mlsteele , for your quick answers.
I will do as suggested. I will also take a look at the code doing this proof to see if I can offer a solution.
Would it be too much to ask which repo I should clone and look into?

Thanks,

Franck Horlaville
TAM Software

from proofs.

All the code you're running locally is in https://github.com/keybase/client. What went wrong in this case is server code though, which is not open source. In general the server tells clients where to look for a proof, and the clients do all the verification locally, but it was the where-to-look that was broken. (We might be able to get rid of this mechanism for web proofs in particular, since there are only a couple possible locations, but it's necessary for services like Facebook and Twitter, where we can't have clients crawling your entire post history every time they try to ID you.)

from proofs.

from proofs.

@fhorlaville I'm seeing Signature not found in body when I ID you. Is that consistent with what you're seeing?

The error is probably that the file at https://www.tamsoftware.info/.well-known/keybase.txt is an old proof, rather than the one that was generated when you proved the domain most recently. When I look at your sigchain, I see that your most recent proof for tamsoftware.info is at "seqno": 6, but the file you're hosting is "seqno": 2.

You'll probably want to re-prove the domain, and make sure you host the new file that gets generated during that flow.

from proofs.

from proofs.

Is there a problem which can be fixed in this repo?
Or should this be closed?

from proofs.