this post was submitted on 30 Dec 2023
155 points (94.8% liked)

Asklemmy

44152 readers
1600 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy πŸ”

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Ruscal@sh.itjust.works 58 points 1 year ago (3 children)

sudo chmod 000 -R / is very fun way of braking your system and is not widely known πŸ™‚

[–] Suburbanl3g3nd@lemmings.world 8 points 1 year ago (2 children)
[–] utopianfiat@lemmy.world 14 points 1 year ago (1 children)

I imagine if you can mount from a busybox possibly

[–] grabyourmotherskeys@lemmy.world 8 points 1 year ago (2 children)

Then figure out the correct perms.

[–] CalicoJack@lemmy.dbzer0.com 13 points 1 year ago (3 children)

Eh, just hit it with the 777 and pray. Then swear at it some more.

[–] nixcamic@lemmy.world 4 points 1 year ago

I think you'll need to change passwd and shadow, maybe a few other files, but besides that it'll mostly work.

This is the traditional method.

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

Yeah that's the painful part. A backup would be key here

[–] intensely_human@lemm.ee 1 points 1 year ago

Worst case you boot up a virtual server with the same OS as your own and just go down the tree learning permissions, and it’s a deep dive learning experience.

[–] fossphi@lemm.ee 1 points 1 year ago

chroot in and then syncing the permissions from something like the equivalent of filesystem package in Arch for your distro should get you going

[–] oriond@lemmy.ml 2 points 1 year ago (3 children)

What does this do? nobody can read any file? would sudo chmod 777 fix it at least to a usable system?

[–] Ruscal@sh.itjust.works 11 points 11 months ago

The trick is that you loose access to every file on the system. chmod is also a file. And ls. And sudo. You see where it's going. System will kinda work after this command, but rebooting (which by a coincidence is a common action for "fixing" things) will reveal that system is dead.

[–] d3Xt3r@lemmy.nz 10 points 11 months ago

Yep. You could run chmod again to fix it (from a different OS / rescue USB), but that would leave all the permissions in a messy state - having everything set to 777 is incredibly insecure, and will also likely break many apps/scripts that expect more restrictive permissions. So the only way to fix this properly would be to reinstall your OS/restore from backups.

[–] Techlos@lemmy.dbzer0.com 4 points 1 year ago

How are you gonna run chmod when you don't have permissions to use it anymore?