Protocol definition about convergence HOT 5 CLOSED

I've started a wiki page drawing them up: https://github.com/moxie0/Convergence/wiki/Notary-Protocol
It's not complete yet though.

from convergence.

I just added a description of all the most common replies a notary can give to that wiki page.

@moxie0, Why exactly the fingerprint list is signed? The SSL connection to the notary should take care of the need to sign the fingerprint list, or am I missing something here?
Sorry if it is inappropriate to ask that question here but it seems like the best place.

from convergence.

Awesome, thanks @cless :)

from convergence.

@ewanm89 and @cless, that's a really excellent protocol writeup, thanks for taking the time to put it together.

@cless, you're correct, the signature is somewhat superfluous, since SSL should take care of integrity. And currently, the client does not even check the signature. The idea is that having a signature in the response makes it easier to prove that a notary could have "lied." Essentially, if a notary starts acting badly, it's easier to demonstrate this with a signature in the response than with a packet capture. We're clearly not enforcing it yet, and we can always take it out if it seems unnecessary, but I thought it prudent to start with it as a placeholder.

from convergence.

Yeah, took some sifting through the code to even start to figure it out, only wondering whether we should add what a 404 return is ;), but anyone who has any idea should know that, but then they should know 503 and 200 also.

Being explicit for the 200 is fine though.

from convergence.