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

Enable Data Contract Serialization for Remoting Exceptions #629

Merged
merged 9 commits into from
Nov 9, 2023

Conversation

Pr1ynka
Copy link
Contributor

@Pr1ynka Pr1ynka commented Nov 6, 2023

We want to discontinue usage of binary formatter based serialization because of security implications. With this change we will switch to data contract based based serialization for remoting exceptions.
More information: https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-reliable-services-exception-serialization

@Pr1ynka Pr1ynka requested a review from a team as a code owner November 6, 2023 11:58
Copy link
Member

@K-Cully K-Cully left a comment

Choose a reason for hiding this comment

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

I believe there should be changes to the proxy factory creation as well https://github.com/microsoft/Omex/blob/main/src/Services.Remoting/Client/OmexServiceProxyFactory.cs

src/Hosting.Services.Remoting/HostBuilderExtensions.cs Outdated Show resolved Hide resolved
Copy link
Member

@K-Cully K-Cully left a comment

Choose a reason for hiding this comment

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

The change looks fine, but I'd suggest adding some additional tests to the public/internal APIs that consume these to validate the behaviour.

@Pr1ynka Pr1ynka merged commit 27610b5 into main Nov 9, 2023
5 checks passed
@Pr1ynka Pr1ynka deleted the fix/enableDataContractSerialization branch November 9, 2023 11:11
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.

3 participants