add optional gRPC max message size limit to trillian logserver and logsigner#3801
Merged
mhutchinson merged 2 commits intogoogle:masterfrom Aug 5, 2025
Merged
Conversation
…gsigner Signed-off-by: Firas Ghanmi <fghanmi@redhat.com>
Signed-off-by: Firas Ghanmi <fghanmi@redhat.com>
mhutchinson
approved these changes
Aug 5, 2025
Contributor
|
/gcbrun |
fghanmi
added a commit
to securesign/trillian
that referenced
this pull request
Aug 5, 2025
…gsigner (google#3801) * add optional gRPC max message size limit to trillian logserver and logsigner Signed-off-by: Firas Ghanmi <fghanmi@redhat.com> * update CHANGELOG.md Signed-off-by: Firas Ghanmi <fghanmi@redhat.com> --------- Signed-off-by: Firas Ghanmi <fghanmi@redhat.com>
fghanmi
added a commit
to securesign/trillian
that referenced
this pull request
Aug 5, 2025
…gsigner (google#3801) (#427) * add optional gRPC max message size limit to trillian logserver and logsigner * update CHANGELOG.md --------- Signed-off-by: Firas Ghanmi <fghanmi@redhat.com>
himaschal
pushed a commit
to digicert/trillian
that referenced
this pull request
Jan 23, 2026
…gsigner (google#3801) * add optional gRPC max message size limit to trillian logserver and logsigner Signed-off-by: Firas Ghanmi <fghanmi@redhat.com> * update CHANGELOG.md Signed-off-by: Firas Ghanmi <fghanmi@redhat.com> --------- Signed-off-by: Firas Ghanmi <fghanmi@redhat.com>
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
2 participants
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.
Description
This change introduces a new optional flag
--max_msg_size_bytesto both Trillian logsigner and logserver.When set to a positive value, the flag enables a gRPC server-side limit on the size of incoming messages using
grpc.MaxRecvMsgSize(). This provides a safeguard against resource exhaustion and potential denial-of-service (DoS) attacks caused by overly large client requests.If the flag is unset or set to 0, no message size limit is enforced, preserving backward compatibility with existing deployments.
This change is non-breaking by design and is disabled by default.
Checklist