Skip to content

docs: clarify host function access control in security.md - #1799

Merged
jprendes merged 2 commits into
hyperlight-dev:mainfrom
JM00NJ:patch-1
Sep 8, 2026
Merged

docs: clarify host function access control in security.md#1799
jprendes merged 2 commits into
hyperlight-dev:mainfrom
JM00NJ:patch-1

Conversation

@JM00NJ

@JM00NJ JM00NJ commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

The previous wording implied that #[host_function] declarations
in guest code control which host functions a guest can access.
This is not the case; all functions registered via sandbox.register()
are callable by any guest in that sandbox.

This PR clarifies:

  • The actual access boundary is sandbox.register(), not #[host_function]
  • #[host_function] is compile-time syntactic sugar, not a security boundary
  • Multi-tenant embedders should use separate sandboxes per trust level

Follows up on security advisory discussion.

Clarify the registration process for host functions in the sandbox and emphasize the importance of access control for untrusted guests.

Signed-off-by: commSync <51642194+JM00NJ@users.noreply.github.com>
@jprendes
jprendes enabled auto-merge (squash) September 8, 2026 10:14
@jprendes

jprendes commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

I think this needs a rebase? I'm not sure why it didn't auto merge

@jprendes
jprendes merged commit 78e5f03 into hyperlight-dev:main Sep 8, 2026
49 checks passed
@jprendes

jprendes commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Thanks for your contribution @JM00NJ !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants