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

Wrap netty accept/connect ops with doPrivileged #22572

Merged
merged 4 commits into from
Jan 13, 2017

Conversation

Tim-Brooks
Copy link
Contributor

This is related to #22116. netty channels require socket connect and
accept privileges. Netty does not currently wrap these operations
with doPrivileged blocks. These changes extend the netty channels
and wrap calls to the relevant super methods in doPrivileged blocks.

This is related to elastic#22116. netty channels require socket `connect` and
`accept` privileges. Netty does not currently wrap these operations
with `doPrivileged` blocks. These changes extend the netty channels
and wrap calls to the relevant super methods in doPrivileged blocks.
@Tim-Brooks
Copy link
Contributor Author

This change should prevent removing socket permissions from core being blocked by Netty's release cycle.

@Tim-Brooks Tim-Brooks added :Distributed Coordination/Network Http and internode communication implementations and removed :Core/Infra/Core Core issues without another label labels Jan 12, 2017
Copy link
Contributor

@s1monw s1monw left a comment

Choose a reason for hiding this comment

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

LGTM

@s1monw s1monw self-assigned this Jan 13, 2017
Copy link
Member

@jasontedor jasontedor left a comment

Choose a reason for hiding this comment

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

LGTM.

@jasontedor
Copy link
Member

The change looks good to me, but I wonder if we should just get rid of the blocking implementation?

@Tim-Brooks Tim-Brooks merged commit f4270f9 into elastic:master Jan 13, 2017
@Tim-Brooks Tim-Brooks deleted the netty_privilege_pipeline branch January 13, 2017 20:27
@s1monw
Copy link
Contributor

s1monw commented Jan 13, 2017

The change looks good to me, but I wonder if we should just get rid of the blocking implementation?

++ to get rid of blocking @tbrooks8 do you wanna take a look at this in a different PR?

@Tim-Brooks
Copy link
Contributor Author

Yes. I can do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Coordination/Network Http and internode communication implementations >enhancement v6.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants