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

Connection establishment with DNS name may create socket in the wrong namespace #62

Closed
m-ronnblom opened this issue Mar 21, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@m-ronnblom
Copy link
Collaborator

If the application switches to a certain namespace, and attempts to establish a connection (e.g., calls xcm_connect()) with a XCM address that contains a DNS hostname, the socket creation may be delayed until the xcm_finish() call. (The socket can't be created until it's know if the name resolves to a IPv4 or IPv6 address.)

If the application at the time of xcm_finish() has switched to some other network namespace, the socket will be created in the wrong namespace (i.e., the current namespace and not the original xcm_connect() namespace). This behavior violates the API description.

@m-ronnblom m-ronnblom added the bug Something isn't working label Mar 21, 2022
@m-ronnblom m-ronnblom changed the title Connection establishment DNS name may create socket in the wrong namespace Connection establishment with DNS name may create socket in the wrong namespace Mar 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant