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

Handle unknown PB data from encrypted messages #1581

Merged
merged 1 commit into from Jun 22, 2018
Merged

Handle unknown PB data from encrypted messages #1581

merged 1 commit into from Jun 22, 2018

Conversation

ManfredKarrer
Copy link
Member

bisq-network/bisq-common#25 , bisq-network/bisq-p2p#11 and bisq-network/bisq-core#122

  • Use ProtobufferException for
    CoreNetworkProtoResolver.fromProto(PB.NetworkEnvelope proto)
  • Add raw PB data in case if an exception
  • log error if the encrypted data contains unknown PB data

Note: We should refactor the resolvers with checked exceptions instead
of the ProtobufferRuntimeException, but for the moment we leave that to
not add too much complexity/risk for that release.

- Use ProtobufferException for
CoreNetworkProtoResolver.fromProto(PB.NetworkEnvelope proto)
- Add raw PB data in case if an exception
- log error if the encrypted data contains unknown PB data

Note: We should refactor the resolvers with checked exceptions instead
of the ProtobufferRuntimeException, but for the moment we leave that to
not add too much complexity/risk for that release.
@ManfredKarrer ManfredKarrer requested a review from sqrrm June 22, 2018 09:28
Copy link
Member

@sqrrm sqrrm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@ManfredKarrer ManfredKarrer merged commit 0cc4f7b into bisq-network:master Jun 22, 2018
@ManfredKarrer ManfredKarrer deleted the protobuffer-exception-handling branch June 26, 2018 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants