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

api: Explain security constraints of ATTR_AUTHORITY_OVERRIDE #9281

Merged
merged 2 commits into from Jun 22, 2022

Conversation

ejona86
Copy link
Member

@ejona86 ejona86 commented Jun 15, 2022

Half of the text was copied from NameResolver.getServiceAuthority().
However, that method can't perform I/O (which would block) so more text
was appropriate here to mention the implications of having a remote
service provide the authority.

I noticed the text was lacking while discussing #9266.

Half of the text was copied from NameResolver.getServiceAuthority().
However, that method can't perform I/O (which would block) so more text
was appropriate here to mention the implications of having a remote
service provide the authority.

I noticed the text was lacking while discussing grpc#9266.
@ejona86 ejona86 requested a review from temawi June 15, 2022 16:12
@@ -40,6 +40,11 @@ public final class EquivalentAddressGroup {
* However, if the channel has overridden authority via
* {@link ManagedChannelBuilder#overrideAuthority(String)}, the transport will use the channel's
* authority override.
*
* <p>The authority <strong>must</strong> be from a trusted source, because if the authority is
* tampered with RPCs may be sent to attackers which may leak sensitive user data. If the
Copy link
Contributor

Choose a reason for hiding this comment

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

"tampered with, RPCs may be..."

@ejona86 ejona86 enabled auto-merge (squash) June 22, 2022 19:52
@ejona86 ejona86 merged commit 69abec5 into grpc:master Jun 22, 2022
@ejona86 ejona86 deleted the eag-authority branch June 23, 2022 21:26
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants