How is .. (dot dot) resolved in bash when cwd is a symlink to a directory
-L logical mode: symlinks are not resolved
-L logical mode: symlinks are not resolved
Was changing ownership of everything to root the right thing to do?
I’m trying to fully grasp the concept of setuid and setgid, and I’m not quite sure in what way permissions are actually elevated. Let me provide an example:
I want to find list of all suid binaries. I use the command
We have a directory and want to protect that from remove and rename, but we need to be able to rename, remove and create contents. What we can do?
If I have two users called john and sally. Both are part of the users group. john creates a directory with permissions 775. sally then puts a file there with 644 permissions.
I’ve been assigned to lock down all /var/log files so that they cannot be read except by the root user. I’ve been stumped by the /var/log/boot.log file. It seems that after every boot the file no matter what what previous permission state gets set to 644 permissions.
Context: I am making an in-browser control panel that gives me one button access to a library of scripts (.sh and .php) that I’ve written to process various kinds of data for a project. It’s a “one stop shop” for managing data for this project.
I.e. what I want is the Linux equivalent of Windows Public/Pictures.
In Linux, what does the d mean in the first position of drwxr-xr-x? And what are all of the possible letters that could be there, and what do they mean? I’m trying to learn more about the Linux file permissions system, and I’d like to see a list of the character meanings for the first … Read more