Linux

48193 readers

1789 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

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Question: restricting users? (lemmy.world)

submitted 1 year ago by Hedgehawk@lemmy.world to c/linux@lemmy.ml

15 comments fedilink hide all child comments

I haven't really used Linux, but I feel it might be useful for a potential project. Is it possible, and how doable is it, to have a password locked admin account and an open user account which is heavily restricted on what they can do? As in, not even browse files. Preferrably only desktop access where they can launch the apps placed there. Which Linux would be the best for this while still being on the easier side to figure out? I do understand tech somewhat well and quite enjoy problem solving, so doesn't need to be ELI5 territory.

you are viewing a single comment's thread
view the rest of the comments

[–] Hedgehawk@lemmy.world 3 points 1 year ago (2 children)

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?

[–] vidarh@lemmy.world 7 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] Hedgehawk@lemmy.world 4 points 1 year ago (1 children)

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.

[–] vidarh@lemmy.world 6 points 1 year ago

If it's not connected to the internet, that certainly does take away a significant cause of problems. Good luck

[–] drugo@sh.itjust.works 3 points 1 year ago

Correct, users that are not explicitly configured as sudoers are limited both in files they can access and commands they can run.