Mixnet: Use max_message_size
and max_path_length
for Sphinx encoding
#104
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've defined two parameters:
max_message_size
andmax_mix_path_length
, but we haven't used it for Sphinx encoding because thepysphinx
library didn't support those parameters.Now that I modified the
pysphinx
to accept those parameters (instead of using hard-coded parameters), we can pass those parameters topysphinx
.As a reminder,
max_message_size
.max_mix_path_length
.pysphinx
raises an exception.