You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: