Comments (6)
Hey - I'm @charles-dyfis-net's successor.
We use gocryptfs in a similar way to @kdrobnyh above, where a handful of programs (under different users) are given access to directories through gocryptfs which starts as root, but drops privileges and runs as a specific (non-root) user which accesses the underlying storage as that uid. The reason to have a specific storage-access user is to simplify deployment while maintaining isolation between users(/services) - this is on NFS where the NFS server is being managed by end users.
Hope this helps explain our usage, & thanks for taking us into account.
Note: updated description to be more clear. thanks Charles.
from gocryptfs.
(To expand a little from my increasingly-outdated memory, the goal was not just simplifying deployment -- a lot of this in the original design was about sandboxing; subtree A, using gocryptfs key A, and exporting content from a specific subtree of the shared for use only by account A, was also used as a security control, ensuring that a compromise of service account A couldn't be used to read data associated with service accounts B, C or D, despite only requiring the customer/user to set up one account on their NFS server; because all these services are creating new data, mkdir
is of course essential)
from gocryptfs.
Hello,
on my end, the crypted folder is owned by user1. I decrypted and mounted the folder using root and force_owner as user2.
What I experience is the following (as user2):
- I can read existing files.
- I can rename existing files.
- I can edit existing files.
- I can delete existing files and folders
- I CANNOT create new files.
My version of gocryptfs is v2.4.0.
Edit: As a temporary solution, one could use bindfs to first mount the crypted folder as user2.
from gocryptfs.
Ugh, -force_owner
looks like a mess right now. I guess #340 made it inconsistent, because that only affected the code paths that create new files.
I'm not sure what behavoir we want, though.
@kdrobnyh what do you want to do with -force_owner
/ why do you use it?
@charles-dyfis-net same question for you. Would it be OK that -force_owner
implies read-only? Or should the files be created as root-owned?
from gocryptfs.
I no longer own the project that was making use of gocryptfs here. To my recollection this would be a no-go; but I've pinged my successor so he can jump in here.
from gocryptfs.
Thanks for your reply!
I have several programs running under different users inside rootless docker containers, so I give those programs access by mounting with -force_owner
. I can't really mount each of the folders separately from under the corresponding users, because those users do not formally exist in the host system (they exist only as subuid/subgid).
from gocryptfs.
Related Issues (20)
- Test failures on Fedora 39: TestFileHoleCopy, TestAccessVirtualDirIV HOT 1
- Encrypted folder does not unmount when user logs out from KDE (SDDM)
- Fedora Silverblue deletig folder content! HOT 8
- I can't access the contents of my encrypted files HOT 3
- Feature request: export files directly to disk (without FUSE mount) HOT 2
- chown not working in mounted sub-folder HOT 3
- Unimplemented opcode OPCODE-52 (STATX) HOT 4
- QEMU's x86-64-v3 virtual CPU benchmark for the collection HOT 5
- 2.4.0 Fails to build on M1 Sonoma 14.3 HOT 2
- directory init and masterkey arg
- xattrs support missing from reverse mode HOT 1
- Small performance regression in x/crypto XChaCha20 implementation HOT 2
- Error mounting via fstab under Debian 12.5 HOT 9
- avoid shelling out to logger binary HOT 4
- [Question] Is using the same config for multiple filesystems a bad idea? HOT 1
- Listing plain text names with encrypted names HOT 5
- question regarding GOCRYPTFS_BAD_NAME behavior in case of file content corruption HOT 1
- hard restart has broken my disc HOT 3
- Install gocryptfs through conda
- REPRODUCIBLE: gocryptfs reverse generating files that gocryptfs can't decrypt? HOT 9
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gocryptfs.