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

Firewall: Send a read-only/non-capturable buffer to the TCP/IP stack. #49

Merged
merged 1 commit into from
Nov 1, 2024

Conversation

hlef
Copy link
Collaborator

@hlef hlef commented Nov 1, 2024

The firewall currently sends a writable and capturable frame buffer capability to the TCP/IP stack. This is bad because the TCP/IP stack can keep the capability and alter the buffer at a later point when we re-use it. Not sure what the exact impact is, but it sounds like the TCP/IP may be able to use this to add endpoints to the firewall table.

The firewall currently sends a writable and capturable frame buffer
capability to the TCP/IP stack. This is bad because the TCP/IP stack can
keep the capability and alter the buffer at a later point when we re-use
it. Not sure what the exact impact is, but it sounds like the TCP/IP may
be able to use this to add endpoints to the firewall table.

Signed-off-by: Hugo Lefeuvre <[email protected]>
@hlef hlef requested a review from davidchisnall November 1, 2024 00:58
Copy link
Contributor

@davidchisnall davidchisnall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ooops, I thought we were doing that already.

@davidchisnall davidchisnall merged commit af597ab into main Nov 1, 2024
2 checks passed
@davidchisnall davidchisnall deleted the hlefeuvre/perms-firewall-frame-buffer branch November 1, 2024 08:28
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

Successfully merging this pull request may close these issues.

2 participants