The issue appears at the final step of the blame() function, where the participant finally verifies the recovered secret share, with the associated commitment. The order was incorrect: if the verification succeeds, that means the share was correct with respect to the commitment and then the complaint maker is the one who should be blamed.
Also adds a check for invalid share correctly encrypted (the previous case was only checking wrong encryption)
closes #22
The issue appears at the final step of the
blame()function, where the participant finally verifies the recovered secret share, with the associated commitment. The order was incorrect: if the verification succeeds, that means the share was correct with respect to the commitment and then the complaint maker is the one who should be blamed.Also adds a check for invalid share correctly encrypted (the previous case was only checking wrong encryption)