From 483fcde3c971b8a3f27664b5b147e50b95098c49 Mon Sep 17 00:00:00 2001 From: Antonio SJ Musumeci Date: Sun, 30 Nov 2025 22:32:56 -0600 Subject: [PATCH] technical_behavior_and_limitations.md --- mkdocs/docs/faq/technical_behavior_and_limitations.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/mkdocs/docs/faq/technical_behavior_and_limitations.md b/mkdocs/docs/faq/technical_behavior_and_limitations.md index 4e72225e..f5b4eac6 100644 --- a/mkdocs/docs/faq/technical_behavior_and_limitations.md +++ b/mkdocs/docs/faq/technical_behavior_and_limitations.md @@ -231,7 +231,8 @@ side `default_permissions` option and leaving it to the FUSE server. When default permissions is enabled the kernel will do the entitlement checks and only allow requests through which have been allowed. When not enabled it is the responsibility of the FUSE server, -in this case mergerfs, to do that. +in this case mergerfs, to do whatever is necessary to manage +entitlements. Prior to mergerfs v2.42.0 it would enable `default_permissions` but also leveraged the uid and gid available in each FUSE request. The