all 50 comments

sorted by: hot top controversial new old
[–] 47 points 2 years ago (1 child)

I have no idea what is going on but this looks good. I agree with you guys. Upvoted.

  • source
  • hideshow 2 child comments
  • [–] 31 points 2 years ago (3 children)

    Cool. Does ACL support also depend on the filesystem?

  • source
  • hideshow 6 child comments
  • [–] 12 points 2 years ago (10 children)

    Yes. Some filesystems straight up do not support ACL of any kind (eg: fat32)

  • source
  • parent
  • hideshow 11 child comments
  • [–] 11 points 2 years ago (1 child)

    Fat32 doesn't support regular file permissions either, right? I was under the impression that it was permissionless.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 2 years ago (1 child)

    You are entirely correct, it has no permission system to speak of

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (9 replies)
  • [–] 26 points 2 years ago (2 children)

    Technically, this is also possible by creating extra groups, but this kind of access control presumably exists because the old-school method can be a pain to administer. Choosing group names can also be an "interesting" secondary challenge.

    i.e. Dude's not going to be best pleased if they ls -l and see the group on the file is xyzgroup-but-not-dude even if it is with good reason. (Shouldn't have deleted the database, dude.)

  • source
  • hideshow 4 child comments
  • [+] 21 points 2 years ago
    [–] 19 points 2 years ago (1 child)

    Does anybody use ACL without regretting it?

  • source
  • hideshow 2 child comments
  • [–] 18 points 2 years ago*

    Cool, I didn't know ACLs were a widely available thing but the infographic explains pretty well! Sounds really useful when granular controls are needed, but I could also imagine it being a huge pain in environments already built out and scripted around regular permissions. Still as always, options are good and an ounce of planning is worth a pound of troubleshooting.

    I do low-key hate seeing a directory named "dir" and a group named "me" though. That's chaotic neutral shit at the very least.

  • source
  • [–] 17 points 2 years ago (1 child)

    Confusing. You set a mask for a user and somehow it propagated down to a group and then you change permission on that group suddenly it applies to the user? Either something is wrong here or ACL permissions make absolutely zero sense. It is 5 billion times easier to use normal permissions to set these things up.

  • source
  • hideshow 2 child comments
  • [–] 12 points 2 years ago* (last edited 2 years ago) (1 child)

    I think it's like this: what used to be group in regular permissions output is a union of group and ACL mask in ACL output. Mask sets the upper limit of what ACL can do, so if mask is rw- then it's impossible to set a r-x ACL permission because allowing execution is not allowed.

    This seems to be more geared towards enterprise environment where it could be complicated to cleanly define groups, since you can only give access to one you might run into a problem where dept. A needs access to that directory but also person G from dept. B and person K from dept. C.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 15 points 2 years ago (1 child)

    ACL Access-Control Lists

    Access Control List Access Control Lists?

  • source
  • hideshow 2 child comments
  • [–] 10 points 2 years ago (2 children)

    That's all fine and dandy, but why does it say rxw on the left?

  • source
  • hideshow 4 child comments
  • [–] 10 points 2 years ago (2 children)

    Permissions are listed as "user", "group", "other". I.e. the user who made the file, the group of the user who made the file (usually just their name as a group), and everyone else. In this case the rxw is for the user.

    For chmod, you can also represent these as binary numbers: 111 would mean having all 3, 101 would mean having read and write, etc. These binary numbers then get turned back into regular numbers (7 in the first example, since it's 111) for chmod. Giving a file "chmod 777" means the user, group, and other all have full permissions on the file. "chmod 700" gives the creator full control, but no one else can view, modify, or execute the file.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 6 points 2 years ago (1 child)

    I feel bad for you because you were just trying to help.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 2 years ago

    🤷‍♂️ They're just internet points, lemmy doesn't notify about up/downvotes so I will only see it if people respond. Either way it's hopefully still useful to someone else looking at the post who isn't familiar with basic permissions or acl

  • source
  • parent
  • [–] 7 points 2 years ago (1 child)
  • [–] 3 points 2 years ago (1 child)

    The only thing you need to know about file acls is not to use them. Similar thing can be said for Network ACLs to be honest.

  • source
  • hideshow 2 child comments
  • [–] 4 points 2 years ago (1 child)

    I've been a network engineer for five years at three companies and not a one has used switch or router based ACL's. It's all in the FW appliance.

  • source
  • parent
  • hideshow 2 child comments
  • [–] -1 points 2 years ago (1 child)

    Network ACLs are my bane. Someone long ago decided we needed to "isolate" the network, so they put ACLs everywhere and so now 50% of my teams time is spend fucking with ACLs :/ It's awful.

  • source
  • parent
  • hideshow 2 child comments
  • [+] 1 point 2 years ago
    [–] 1 point 2 years ago