Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gmw_and failing occasionally in parallel case with party_count>2 #211

Open
YuwanXiao opened this issue Aug 20, 2020 · 0 comments
Open

gmw_and failing occasionally in parallel case with party_count>2 #211

YuwanXiao opened this issue Aug 20, 2020 · 0 comments
Labels

Comments

@YuwanXiao
Copy link

Bug report

under Branch 197_GMW
commit dbd50b9

bug detail:

  1. gmw_and fails under parallel tests.
  2. but works for parallel with party_count=2

reproduce:

  1. can run the demos/GMW_demo test to do a simple check .
    it might be easier to reproduce with input changing to all 1 in demo test line 30.
    inputs[i+1].push(1); //Math.floor((Math.random() * maxValue))

  2. update test suite protocol.json with party_count>2 to test.
    need to run several since the bug happens occasionally.

related file:
jiff/lib/client/protocols/gmw_bit/ (IO.js and gmw.js)
and commit merge ot listen into lib

failed try outs:

  1. add op_id in IO.js line25 to
    op_id: op_id
    or op_id: op_id+'-'+tag
    do not make difference
    var message_to_send = {tag: 'OT', party_id: to_party, message: msg, op_id : op_id encrypted: true};

  2. update function generate_op_id_ot with unique seed in counter file
    do not make difference.

it seems the opId is unique when we resolve msg in ot_receive file.

since the parallel fails on >2. it may be involved with op_id matching in ot send and receive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

2 participants