Jump to content

Talk:Socialist millionaire problem

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Rename variables

[edit]

There is currently a clash with p (the prime) and p the calculated value.

I think changing the calculated value p -> m and q -> n would make sense.

A concern then would be that h, m, and n are too similar, in which case I recommend changing h -> g (the generator). This would also be consistent with the diffie-hellman page and the Primitive_root_modulo_n page where primitive roots are denoted as g.

Lastly, g and gamma are already there and might be changed to d and delta ?

Cciollaro (talk) 03:17, 8 July 2014 (UTC)[reply]

Clarify what an attacker can do

[edit]
An active attacker, capable of arbitrarily interfering with Alice and Bob's communication (a man-in-the-middle) cannot learn more than a passive attacker, and cannot affect the outcome of the protocol other than to make it fail.

What does make it fail mean here?

Alice and Bob wish to learn if x = y without allowing either party to learn anything else about the other's secret value.

It would help to be clear on what the outcomes for Alice and Bob are. They initiate this procedure and get a result. What are the possible results? Is it binary, just equals or not equals, or is there also a "unable to determine" result they can discern? If it's binary, then failure is presumably causing them to get the not equals response, because it's the equals response that they will respond to by sharing secrets. 70.116.69.206 (talk) 19:00, 1 April 2013 (UTC)[reply]

Counter Example

[edit]

The statement ending with "This proves correctness." is a bit misleading, what in fact it proves is that x equals y is one solution to ; however since is a generator mod , (x-y)=0 is not the only solution. As illistrated below:

Alice Multiparty Bob
Message
Random
Public Message
Random

Secure

Secure
Insecure exchange

Let
Insecure exchange

Secure
Each tests whether equals , which passes. Even though does not equal .


199.34.4.20 (talk) 19:57, 17 November 2014 (UTC)[reply]

Infact all a Mallory in the middle need do is choose such that , then regardless of Alice and Bob's Choices of Mallory's messages would appear to be the same as respectively.
199.34.4.20 (talk) 22:10, 17 November 2014 (UTC)[reply]

update above counter example to match the current page's terminology

Alice Multiparty Bob
1 Message
Random
Public Message
Random
2 Test Secure Test
3 Test Secure Test
4
5 Insecure exchange
6 Secure
7 Test Test
8 Test Test
both Alice and Bob compare step 6 results to step 8 and see that 11 matches; however this is a false positive because Alice's message 3 does not match Bob's mesage 14.

Notes:

  • the counter example above comes from since
  • The newly rewritten final statment "Because of the random values stored in secret by the other party, neither party can force and to be equal unless equals , in which case . This proves correctness", is now just a blatant misunderstanding of the mathematics behind this algorithm. Any of the following will force a false positive given :
    • ... well you get where I'm going here, use the commutative property of the exponents to get then , where the existance of is guaranteed due to the properties of being a generator

199.34.4.20 (talk) 22:36, 29 March 2016 (UTC)[reply]

I believe you're applying the modulo too early. Here I reproduce your list along with my understanding of why your arguments don't apply.

Given :

  • — Not possible because the unit is not a generator.
  • — Not possible because of testing. This rules out an exponent equaling zero or a multiple of the group order.
  • — Ditto
  • — Ditto
  • — Ditto
  • — This is exactly what you're looking for, so doesn't pose a problem.
  • — The product can only be equal to zero if one of the factors already is. It can only equal a multiple of the prime order of the group if either factor already is. Both cases are ruled out by earlier testing.
  • — Ditto
  • — Ditto
  • — Ditto
  • — Ditto
  • — Ditto
  • — Ditto
  • — Ditto
  • — Since this is only possible when which is what you're looking for.
  • — Ditto
  • — Ditto
  • — Ditto
  • — Ditto

This still leaves the possibility that the difference between and is any multiple of the group order , I'm not sure whether/how that is handled in the protocol.

--2A02:1810:2586:B400:24A6:D6B8:F671:DD2B (talk) 16:37, 11 May 2020 (UTC)[reply]
Ideally, there should be additional tests to ensure that , , and are coprime to , but AFAIK, this is not possible with the partial knowledge, as the integer factorization of is not known in general. But checking that for the smallest prime factors of and ditto for and restricting the size of and could avoid the issue.
With your counter-example, the issue comes from the fact that is divisible by 2 (thus is not coprime to ) and that is too large in the context of your counter-example ( has a large prime factor common with : 11). With that, is divisible by , which yields the issue. Vincent Lefèvre (talk) 01:30, 25 December 2018 (UTC)[reply]

Clarify initial state

[edit]

Article currently says "Let Alice and Bob fix a prime number p". Does "fix" mean that they agree upon the number? How? Out of band? Through previous communications? Is this "fix" subject to attack? For example can a Man In The Middle convince Alice that P=7 while convincing Bob that P=5? Have Alice and Bob verified each other's identities, and if so, how? Article needs more detail about the initial state, assumptions, and what if anything has come before. 68.110.104.114 (talk) 18:25, 20 November 2014 (UTC)[reply]

Yes "fix" does mean that they both agree upon a number to use beforehand, usually way out of band and static for all communications as is in the case of OTR which uses a well-known nothing up my sleeve number defined as group 5 in RFC 3526
FFFFFFFF FFFFFFFF C90FDAA2 2168C234 C4C6628B 80DC1CD1
29024E08 8A67CC74 020BBEA6 3B139B22 514A0879 8E3404DD
EF9519B3 CD3A431B 302B0A6D F25F1437 4FE1356D 6D51C245
E485B576 625E7EC6 F44C42E9 A637ED6B 0BFF5CB6 F406B7ED
EE386BFB 5A899FA5 AE9F2411 7C4B1FE6 49286651 ECE45B3D
C2007CB8 A163BF05 98DA4836 1C55D39A 69163FA8 FD24CF5F
83655D23 DCA3AD96 1C62F356 208552BB 9ED52907 7096966D
670C354E 4ABC9804 F1746C08 CA237327 FFFFFFFF FFFFFFFF

and 199.34.4.20 (talk) 19:30, 4 April 2016 (UTC)[reply]

Poorly writte

[edit]

Article uses variable it never introduces, namely alpha and beta. In general, the article feels like it was written as a blob of cut & paste errors.