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
Current implementation of socketpair created two sockets and bind an unique address to each of them. But this is not the desired behavior according to standard: "One way in which the use of socketpair() differs from creating a pair of connected sockets manually is that the sockets are not bound to any address. This can help us avoid a whole class of security vulnerabilities, since the sockets are not visible to any other process". The sockets returned by socketpair should behave like a pipe, without binding to any address.
Why this behavior
This is a misbehavior issue and rewritten needs to be done on socketpair to match the desired behavior.
The text was updated successfully, but these errors were encountered:
Description
Current implementation of socketpair created two sockets and bind an unique address to each of them. But this is not the desired behavior according to standard: "One way in which the use of socketpair() differs from creating a pair of connected sockets manually is that the sockets are not bound to any address. This can help us avoid a whole class of security vulnerabilities, since the sockets are not visible to any other process". The sockets returned by socketpair should behave like a pipe, without binding to any address.
Why this behavior
This is a misbehavior issue and rewritten needs to be done on socketpair to match the desired behavior.
The text was updated successfully, but these errors were encountered: