Video summary
The video begins by focusing on the directory of Michelle, a new employee in the manufacturing department who has inherited files with existing permissions from her predecessor. The primary goal is to review these files and adjust their access rights using specific commands to ensure security and appropriateness. For instance, a shell script named Backup files.sh allows Michelle to read, write, and execute it, while other group members can read and run it. Since there is no legitimate reason for individuals outside the manufacturing group to execute this backup script, the recommendation is to remove all permissions for others using either symbolic or numeric methods.
Next, the discussion shifts to a file called Complaints.ext, which is used by employees to submit suggestions via a web interface. Access to this file must be restricted so that only members of the manufacturing group can write to it, and no one outside the group should have any access. Additionally, other employees within the group should not be able to read the complaints of their colleagues to maintain privacy. The tutorial demonstrates how to achieve this by eliminating permissions for others and limiting group access to write-only capabilities, illustrating both symbolic notation and its numeric equivalent.
The video then covers several scenarios involving public files and sensitive data. Files intended for a website are made readable by everyone, while a program reading from a confidential data file containing employee information is restricted so that only Michelle can access it. The presenter also highlights a file with illogical permissions where the owner has read-only access but others have full read-write privileges, identifying this as an error likely caused by incorrect numeric settings. In such cases, the best practice is to revert to standard options where the user has read and write access, the group has read-only access, and others have no access at all.
In conclusion, setting file permissions requires a thoughtful decision-making process that starts with understanding the specific function of each file. Once the purpose of a file is clear, one must determine exactly who needs to access it and what level of access is necessary. By answering these questions regarding the file's role and the identity of its users, administrators can confidently set the correct permissions using either symbolic or numeric commands to maintain a secure and functional environment.
Read the full video transcript
In a previous video, we had set up our
company's users into three groups, each
of which had access to the directories
of their group members.
Now, we want to focus on one person's
directory, Michelle from manufacturing.
She was hired to replace the former head
of manufacturing, and she inherited all
of their files with their permissions.
We'll go through these files and see
which permissions need to change and the
commands used to change them.
Backup files.sh is a shell script, a
program for backing up files. Michelle
can read, write, and execute the script.
The other people in her group can read
and run the program, as can everyone
else.
Is there any reason that people outside
the manufacturing group should be able
to run that script? Probably not. So, we
want to remove all permissions for
other.
Here are several ways to do it
symbolically.
And here is how to set the permissions
numerically.
Complaints.ext text is a file where
manufacturing employees can write their
complaints or suggestions via a
web-based program.
There's no reason anyone outside the
group should be able to access the file,
but we also do not want anyone other
than Michelle to be able to read other
people's complaints.
We want to eliminate access by other and
allow the group to write only.
Here are several methods to do this
symbolically.
And notice on the third one when I say G
equals and don't follow it by anything
that means to eliminate all the
permissions for the group.
And here's how to set the same
permissions numerically.
These two files will go on the website,
so they should be readable by everybody.
Notice that you can specify as many
files as you want with one chod command.
And again, here's the numeric setting.
Finally, we have a file that doesn't
need any changes.
InfoCard.pdf
contains an infographic about
manufacturing and it should be readable
by anybody.
These two files go together. Make unit
report is a program that reads
information from the units produced.dat
file.
The data file contains some confidential
information about the employees as well
as the numbers for how many units were
produced.
That's why nobody except Michelle can
access the data file or run the program.
No changes needed here.
However, if Michelle decides later that
she wants anyone else to be able to run
the program, she'll need an advanced
feature to allow that. And we'll talk
about that in another video.
Finally, this last file which has user
feedback about the company products.
These permissions make absolutely no
sense. I cannot think of a reasonable
situation where the owner has readonly
access. The group has none, but everyone
else can read and write a file.
This looks like someone got their
numeric chod settings wrong.
The best thing to do is to go with
standard options read and write for the
user and read only for group and other.
And again at the left you see how to do
it symbolically. On the right the
numeric setting.
This is the kind of decision making that
you go through when setting permissions.
When setting permissions on a file, you
need to ask yourself, what does this
file really do?
And once you know that, you can ask
yourself who needs access to the file
and exactly how much access do they
need?
And once you've answered those
questions, you'll know which permissions
to set.