feat(ipc): add opt-in admission and authorization - #21
Merged
Merged
Conversation
Bind trusted caller identity to IPC sessions, authorize ingress and each delivery, and support connection revocation. Release workspace version 9.4.0. Closes #20
This branch was successfully deployed
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
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.
IPC clients currently share the same listener without an application admission or authorization boundary. This adds opt-in policies that bind server-established identity to a connection and expose it to typed handlers. Existing listener entry points retain their behavior.
Policies admit connections asynchronously and authorize requests, discovery, exact and pattern subscriptions, and each outgoing notification. Recipient memoization remains separate from authorization. Revocation removes routes, cancels transport activity, and skips queued IPC messages that have not begun dispatch.
Emergent can use these hooks to map live child PIDs to primitives and enforce declared capabilities. That application policy remains in Emergent.
Closes #20. Supports Govcraft/emergent#24.
Release: 9.4.0 across all four workspace crates.
Validation: