You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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))
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:
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};
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.
The text was updated successfully, but these errors were encountered:
Bug report
under Branch 197_GMW
commit dbd50b9
bug detail:
reproduce:
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))
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:
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};
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.
The text was updated successfully, but these errors were encountered: