zac/zssg
1
0
Fork 0
Code Issues 3 Pull requests Projects Releases Packages Wiki Activity Actions

Fine-grained WASI access controls for plugins #2

New issue
Open
opened 2025-05-22 18:08:18 +00:00 by zac · 0 comments
zac commented 2025-05-22 18:08:18 +00:00
Owner
Copy link

It may be useful to expose something like filesystem or network access to a particular plugin, however it would be great if users could impose restrictions on what a plugin can access in those scenarios. Maybe this would just exist in the site configuration, but maybe zssg could support a kind of access control plugin for more advanced usecases.

Can extism support access controls?

It may be useful to expose something like filesystem or network access to a particular plugin, however it would be great if users could impose restrictions on what a plugin can access in those scenarios. Maybe this would just exist in the site configuration, but maybe zssg could support a kind of access control plugin for more advanced usecases. Can extism support access controls?
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: zac/zssg#2
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?