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

sockets created by socketpair_syscall should not bind to any address #278

Open
qianxichen233 opened this issue Jun 27, 2024 · 0 comments
Open

Comments

@qianxichen233
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant