Docs: surface serialization security guidance on the remoting security page#8177
Merged
Aaronontheweb merged 2 commits intoApr 23, 2026
Conversation
…y page The `allow-unregistered-types = false` setting added in v1.5.66 was only documented in the serialization page. This adds it as a visible layer on the network security page as well, without duplicating the full content. Changes: - remoting/security.md: expand Security Layers from 3 to 4, adding Serialization Safety; add a dedicated Serialization Security section between Untrusted Mode and VPNs explaining the fallback risk and the HOCON setting; improve prose throughout (mTLS benefits, programmatic validation intro, startup validation, TLS optional/recommended lists) - serialization/serialization.md: rewrite the Disabling Default Serializer Fallback prose to drop inline-header bullet list; fix grammar in the polymorphic serializer section; update cross-reference link to point to the new section on the remoting security page Closes the follow-up requested in akkadotnet#8173.
4 tasks
Aaronontheweb
added a commit
that referenced
this pull request
Apr 24, 2026
…y page (#8177) The `allow-unregistered-types = false` setting added in v1.5.66 was only documented in the serialization page. This adds it as a visible layer on the network security page as well, without duplicating the full content. Changes: - remoting/security.md: expand Security Layers from 3 to 4, adding Serialization Safety; add a dedicated Serialization Security section between Untrusted Mode and VPNs explaining the fallback risk and the HOCON setting; improve prose throughout (mTLS benefits, programmatic validation intro, startup validation, TLS optional/recommended lists) - serialization/serialization.md: rewrite the Disabling Default Serializer Fallback prose to drop inline-header bullet list; fix grammar in the polymorphic serializer section; update cross-reference link to point to the new section on the remoting security page Closes the follow-up requested in #8173.
This was referenced Apr 27, 2026
Merged
Closed
This was referenced May 21, 2026
Closed
Open
Open
This was referenced May 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Follow-up to #8173, which added the
allow-unregistered-types = falsesetting (v1.5.66+) and documented it in the serialization page. This PR makes that security guidance more visible on the remoting/network security page without duplicating the full content.serialization.mdserialization.mdto point to the new section on the remoting pageTest plan
dotnet docfx build ./docs/docfx.json --warningsAsErrors)serialization.mdresolves correctly to the new section