21
Question: restricting users?
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 14 Oct 2023
21 points (100.0% liked)
Linux
48008 readers
897 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Yeah, Linux was built as a multi-user system, so user and group permissions have always been a core aspect of it. The "password locked admin account" is just the
rootuser, although you should maybe leave that as a "failsafe" account and create a separate user withsudoer permissions. Every file and folder in Linux has an owner and read/write/execute permissions for the owner, members of its group, and others. By default, users are limited to their own home folder (/home/username, where folders like Documents are stored) and a handful of world-writable locations (like/tmp) If you need more specific permissions, ACLs are also available. Or SELinux.The biggest difference regarding distribution choice is that some distros ship with SELinux enabled, while most don't. For everything else there's not much difference, so maybe start with Debian for its community support/resources?
Thanks for the advice! The premission stuff sounds perfect. So by default, basic account can't really mess anything up, even if it's a tech literate person using it?
In theory if there are no security holes, a user account can only mess up its own account.
Note that what steps you want to take will really depend on who these users are and what you want to achieve. There's a vast chasm between allowing in, say, friends or colleagues, vs. letting random people on the internet access it. The latter will mean someone will intentionally look for exploits, which means e.g. regularly applying security updates becomes far more pressing.
If you are letting in random strangers, I'd look into only giving them access within a separate container or ideally virtual machine per user as an extra precaution unless what you're making available is very stripped down.
From past experiences, the worst I'm expecting is kids that think they know what hacking is because of some whacky Tiktok or Youtube video they saw. So there may be some intention to mess with things, it's just not very likely they truly know what they're doing. There won't be internet involved, hopefully.
I like the idea of a separate container or the like, will need to look into it, thanks.
If it's not connected to the internet, that certainly does take away a significant cause of problems. Good luck