Provide a way for helpers to behave maliciously inside the test infrastructure #1195
Comments
akoshelev
added a commit
to akoshelev/raw-ipa
that referenced
this issue
Jul 26, 2024
This change implements private-attribution#1195 by providing a means for unit tests to intercept send requests that send circuit-specific data between MPC helpers. This change also updates the existing unit tests for malicious `reshare` and `reveal` protocols to showcase the API and test it in real scenarios. In both cases, using it, led to significant reduction in code redundancy. The key improvement is that now tests are not required to re-implement the basic protocol to inject additive attacks. It can now be done outside the circuit being tested. The support for sharding exists at the API level, but no actual implementation allows intercepting traffic between shards. There is currently not a lot of sharded protocols, so this can be postponed until later.
akoshelev
added a commit
that referenced
this issue
Jul 30, 2024
* Interface for test infrastructure to inspect streams This change implements #1195 by providing a means for unit tests to intercept send requests that send circuit-specific data between MPC helpers. This change also updates the existing unit tests for malicious `reshare` and `reveal` protocols to showcase the API and test it in real scenarios. In both cases, using it, led to significant reduction in code redundancy. The key improvement is that now tests are not required to re-implement the basic protocol to inject additive attacks. It can now be done outside the circuit being tested. The support for sharding exists at the API level, but no actual implementation allows intercepting traffic between shards. There is currently not a lot of sharded protocols, so this can be postponed until later. * Fix clippy issues * Feedback
akoshelev
added a commit
to akoshelev/raw-ipa
that referenced
this issue
Aug 5, 2024
This change implements private-attribution#1195 by providing a means for unit tests to intercept send requests that send circuit-specific data between MPC helpers. This change also updates the existing unit tests for malicious `reshare` and `reveal` protocols to showcase the API and test it in real scenarios. In both cases, using it, led to significant reduction in code redundancy. The key improvement is that now tests are not required to re-implement the basic protocol to inject additive attacks. It can now be done outside the circuit being tested. The support for sharding exists at the API level, but no actual implementation allows intercepting traffic between shards. There is currently not a lot of sharded protocols, so this can be postponed until later.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, whenever we want to reproduce malicious behaviour, we reimplement the protocol and run additive attacks manually. There does not seem to be a need to do that, because we can just instruct the test infrastructure to corrupt bits before sending them out to the other helpers.
The text was updated successfully, but these errors were encountered: