true multiuser capability #15
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 5 commits
September 26, 2019 02:21
home dir for each user and one additional transfer dir where every user has write privileges
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As it was, one could define a multitude of users, albeit they always shared just one directory and could therefore read, modify and delete each other files. This merge reqest addresses this: If there is a file user.passwd available, it is analyzed and for each user found a private home dir is created so that other users can only see the files but not there content - consequently they can neither modify or delete files in other users private home directory. Additionally, one dir named transfer is created - acting as shared or exchange folder : inside this folder, all authenticated users can read, modify and delete all files