-
-
Notifications
You must be signed in to change notification settings - Fork 753
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
borg mount / borgfs security fix (1.1-maint) #4331
borg mount / borgfs security fix (1.1-maint) #4331
Conversation
3becd28
to
7eb1a36
Compare
Codecov Report
@@ Coverage Diff @@
## 1.1-maint #4331 +/- ##
============================================
+ Coverage 84.31% 84.4% +0.09%
============================================
Files 23 23
Lines 9421 9421
Branches 1607 1607
============================================
+ Hits 7943 7952 +9
+ Misses 1030 1023 -7
+ Partials 448 446 -2
Continue to review full report at Codecov.
|
34d86ee
to
3c4bcdb
Compare
3c4bcdb
to
695707e
Compare
…ckup#3903 "default_permissions" is now enforced by borg by default to let the kernel check uid/gid/mode based permissions. "ignore_permissions" can be given to not enforce "default_permissions". note: man mount.fuse explicitly tells about the security issue: default_permissions By default FUSE doesn't check file access permissions, ... This option enables permission checking, restricting access based on file mode. This option is usually useful together with the allow_other mount option. We consider this a pitfall waiting for someone to fall into and this is why we chose to change the default behaviour for borg.
695707e
to
1b277cb
Compare
fix is in 1.1.9 release. result of platform testing was at first that same fakeroot-caused test failures as on macOS in the past are now also seen on linux (due to the on-by-default permissions check). fixed all platforms by ignoring permissions checking for this test. |
platform testing will be done as part of release process.