## A method for two parties to verify if they share a common secret without revealing that secret if they don’t.

We didn’t cover zero knowledge proofs in the Security Engineering course I did last semester. But part way into the course I needed a way for two people, A and B to verify that some number they each know is infact the same number N in the case that they don’t have a trusted arbitrator and they don’t want to reveal the number they each know to the other person unless the other person has the same number.

I don’t think this is exactly a zero knowledge proof situation by it seems closely related. The motivating situation for this was a web application that set some cookies and I wanted to know if one of these cookies set was unique per user or unique per some other setting (but the web application doesn’t allow just anyone to create a new account, so I couldn’t determine this on my own). In the case that it was unique per user then I don’t want to tell anyone what my value for this cookie is because then they may be able to hijack my session.

So a method I thought of was that each person reveals one bit of the number to the other person at a time.

I’ll try to formalise this a bit more.

I’ll call this number the message. is the message knows, is the message knows. and arrange that they each know some message and arrange that they wish to verify if . If then and must each know that that is the case and if then and must also know (after conducting the verification) that this is the case, but do not wish to let the other one know what their message was.

and meet letting be the entity that begins the verification. Each message is first encoded into a binary representation using an agreed upon method. then tells what the 1st bit of is (denoted ). now verifies this bit with . If , tells the second bit of . If , randomly selects a bit (ie. randomly selects either 0 or 1) and tells that random bit instead, and flags that . As soon as either or flags that they subsequently always report a random bit regardless of whether the last bit reported to them was correct or not.

We could use an end of message token to indicate the end of the message. Of course this method isn’t perfect because if one’s random stream of bits matches what the other expects then one thinks that but the other thinks that .

Another problem is if both parties have determined that then when do they stop sending random bits to each other? If both parties are happy to reveal the length of their message then there is no problem. Otherwise both parties can keep sending random bits until they feel that the the message space they have opened up is large enough and they don’t mind revealing that the length of their message is less than the bit number they are up too.

Here’s an example. A’s number is 0110. B’s number is 0110 and they want to check if they share the same number.

A -> B: 0 (B expects this) B -> A: 1 (A expects this) A -> B: 1 (B expects this) B -> A: 0 (A expects this) A -> B: $ (B expects this) (not needed if they first agree on revealing the message length)

Another case A knows 0110, B knows 0010.

A -> B: 0 (B expects this) B -> A: 0 (A does not expect this, so A concludes A_M != B_M, and subsequently sends randomness) A -> B: Rand(0,1) (two cases) A sent 0 (B does not expect this, so B also concludes A_M != B_M, and subsequently sends randomness) ... continues until the end of M or until one party stops sending randomness. A sent 1 (B expects this, but A hasn't revealed anything as they made a random selection) B -> A: 0 (A doesn't know if B is sending randomness or not) if they agreed upon a message length, (A knows that A_M != B_M, but B thinks that A_M == B_M) (but A has only revealed 1 bit of A_M to B (because B doesn't know if A was sending A_M or randomness after the 1st bit), and B hasn't revealed anything of B_M to A (because A doesn't know if B was sending randomness))# (the probability of this happening is z) or, no message length agreed upon, A keeps sending randomness and B will detect this (because B is expecting the end of stream token and didn't get it), so they both know that A_M != B_M.

This is not very formal and I’m confident I’ve missed some details or left some a bit fuzzy, I only really wanted to explain the general concept.

# To be honest I’m not so sure if this is correct. Rather than me going around in circles unable to solve the math, and just abandoning this post, I’ll just leave it be and post with this uncertainty.