From 47ff51009fa05d83bb67cd5db16829ab4c0081d7 Mon Sep 17 00:00:00 2001 From: Andrew Clayton Date: Wed, 9 Aug 2023 18:22:46 +0100 Subject: Wasm: Add support for directory access. Due to the sandboxed nature of WebAssembly, by default WASM modules don't have any access to the underlying filesystem. There is however a capabilities based mechanism[0] for allowing such access. This adds a config option to the 'wasm' application type; 'access.filesystem' which takes an array of directory paths that are then made available to the WASM module. This access works recursively, i.e everything under a specific path is allowed access to. Example config might look like "access" { "filesystem": [ "/tmp", "/var/tmp" ] } The actual mechanism used allows directories to be mapped differently in the guest. But at the moment we don't support that and just map say /tmp to /tmp. This can be revisited if it's something users clamour for. Network sockets are another resource that may be controlled in this manner, for example there is a wasi_config_preopen_socket() function, however this requires the runtime to open the network socket then effectively pass this through to the guest. This is something that can be revisited in the future if users desire it. [0]: Reviewed-by: Alejandro Colomar Signed-off-by: Andrew Clayton --- src/nxt_application.h | 2 ++ 1 file changed, 2 insertions(+) (limited to 'src/nxt_application.h') diff --git a/src/nxt_application.h b/src/nxt_application.h index ff3ec562..64866db6 100644 --- a/src/nxt_application.h +++ b/src/nxt_application.h @@ -99,6 +99,8 @@ typedef struct { const char *request_init_handler; const char *request_end_handler; const char *response_end_handler; + + nxt_conf_value_t *access; } nxt_wasm_app_conf_t; -- cgit