Currently the GNU userland seems very limited in terms of managing since it seems to have a very limited options for permission management in terms of user and user groups.
The issue
GNU userland only allows permission Read, Write, Executable with option for files, directories, symlinks and sockets set for specific user and usergroup and other users/usergroups.
Expected
Allow permission to be set for multiple users and user groups with more options in terms of file attributes:
Readable
Writable
Executable
Removable
Symlinkable
Change location of the file
Mountable
User/Usergroup can change permission
Implemented limitation to who and how can set the permission.
More to be added on demand
Option to snitch to the selected user/usergroup if they try to change pathname on specific permission that they don't have the permission to.
i.e user Jef tries to edit /etc/passwd file -> Allow this to be used as a logic trigger i.e informing administrator about this behavior or suspending the user.
Currently it's also next to impossible to contribute in File System Hierarchy 3.0 which should be made easier on our userland and the standard should be presented in user-friendly (possibly interactive) way so that the community is educated about which pathname should be used for what.
Relevants
Currently GNU userland is very good to be used for a verbal communication i.e /usr/share is universal share which is expected to be implemented in our userland as well.
Currently the GNU userland seems very limited in terms of managing since it seems to have a very limited options for permission management in terms of user and user groups.
### The issue
GNU userland only allows permission Read, Write, Executable with option for files, directories, symlinks and sockets set for specific user and usergroup and other users/usergroups.
### Expected
Allow permission to be set for multiple users and user groups with more options in terms of file attributes:
- Readable
- Writable
- Executable
- Removable
- Symlinkable
- Change location of the file
- Mountable
- User/Usergroup can change permission
- Implemented limitation to who and how can set the permission.
- More to be added on demand
Option to snitch to the selected user/usergroup if they try to change pathname on specific permission that they don't have the permission to.
i.e user `Jef` tries to edit /etc/passwd file -> Allow this to be used as a logic trigger i.e informing administrator about this behavior or suspending the user.
Currently it's also next to impossible to contribute in File System Hierarchy 3.0 which should be made easier on our userland and the standard should be presented in user-friendly (possibly interactive) way so that the community is educated about which pathname should be used for what.
### Relevants
Currently GNU userland is very good to be used for a verbal communication i.e `/usr/share` is `universal share` which is expected to be implemented in our userland as well.
Issue-Label Bot is automatically applying the label feature_request to this issue, with a confidence of 0.77. Please mark this comment with 👍 or 👎 to give our bot feedback!
Issue-Label Bot is automatically applying the label `feature_request` to this issue, with a confidence of 0.77. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: [app homepage](https://github.com/marketplace/issue-label-bot), [dashboard](https://mlbot.net/data/RXT0112/Zernit) and [code](https://github.com/hamelsmu/MLapp) for this bot.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently the GNU userland seems very limited in terms of managing since it seems to have a very limited options for permission management in terms of user and user groups.
The issue
GNU userland only allows permission Read, Write, Executable with option for files, directories, symlinks and sockets set for specific user and usergroup and other users/usergroups.
Expected
Allow permission to be set for multiple users and user groups with more options in terms of file attributes:
Option to snitch to the selected user/usergroup if they try to change pathname on specific permission that they don't have the permission to.
i.e user
Jeftries to edit /etc/passwd file -> Allow this to be used as a logic trigger i.e informing administrator about this behavior or suspending the user.Currently it's also next to impossible to contribute in File System Hierarchy 3.0 which should be made easier on our userland and the standard should be presented in user-friendly (possibly interactive) way so that the community is educated about which pathname should be used for what.
Relevants
Currently GNU userland is very good to be used for a verbal communication i.e
/usr/shareisuniversal sharewhich is expected to be implemented in our userland as well.Issue-Label Bot is automatically applying the label
feature_requestto this issue, with a confidence of 0.77. Please mark this comment with 👍 or 👎 to give our bot feedback!Links: app homepage, dashboard and code for this bot.
This is great