kreyren/Zernit
1
0
Fork 0
Code Issues 129 Pull Requests Releases Activity

Custom userland #173

New Issue
Open
opened 2020-08-21 03:39:54 +02:00 by Kreyren · 2 comments
Kreyren commented 2020-08-21 03:39:54 +02:00 (Migrated from github.com)
Copy Link

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[bot] commented 2020-08-21 03:39:56 +02:00 (Migrated from github.com)
Copy Link

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!

Links: app homepage, dashboard and code for this bot.

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.
👍 2
Uniminin commented 2020-08-21 07:17:52 +02:00 (Migrated from github.com)
Copy Link

This is great

This is great
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kreyren/Zernit#173
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?