Use user permissions on socket handles#94
Open
hlef wants to merge 4 commits into
Open
Conversation
hlef
force-pushed
the
hlefeuvre/user-permissions-on-sockets
branch
from
July 3, 2026 16:46
5f3fe6d to
ac07f2c
Compare
Passing an invalid timeout capability currently crashes the network stack (which is really annoying as it triggers a reset). Signed-off-by: Hugo Lefeuvre <hugo.lefeuvre@ubc.ca>
hlef
force-pushed
the
hlefeuvre/user-permissions-on-sockets
branch
from
July 10, 2026 17:52
ac07f2c to
d7e8cef
Compare
Signed-off-by: Hugo Lefeuvre <hugo.lefeuvre@ubc.ca>
Similar to what we recently did in the allocator and in the message queue, we can use the three currently-unused bits at the bottom of sealed socket handles to store permissions. Having permissions on sockets allows us to encode the right to close a socket, send, or receive data. Signed-off-by: Hugo Lefeuvre <hugo.lefeuvre@ubc.ca>
hlef
force-pushed
the
hlefeuvre/user-permissions-on-sockets
branch
from
July 10, 2026 18:05
d7e8cef to
a3a98ca
Compare
This extends the HTTP server example to showcase socket and allocator capability permissions. We can also use that example later to showcase sub-quotas. Signed-off-by: Hugo Lefeuvre <hugo.lefeuvre@ubc.ca>
hlef
force-pushed
the
hlefeuvre/user-permissions-on-sockets
branch
from
July 10, 2026 19:02
a3a98ca to
8929e20
Compare
Collaborator
Author
|
Alright @davidchisnall, addressed all I could and created issues for everything else. Let me know what I broke in that process 🙂 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This addresses #91. While at it, it adds some missing documentation (which I realized while documenting the feature), and adds a missing check (which I found out while adding the permission checks).
This comes with a new example to showcase the use of least-privilege socket handles.