Cabrillo College


Objectives

In this lab you will learn how to assign permissions to files and directories to provide a measure of security and privacy to your files on a multiuser system.

Forum

If you get stuck, have a question or want to share something you learned with this lab then use the CIS 90 Forum at http://simms-teach.com/forum/viewforum.php?f=9

Procedure

Log on to a Unix machine so that you have a command line shell at your service. Be sure you are in your home directory to start this lab. Using the chgrp, and chmod commands, you will modify the permissions on files and subdirectories in your home directory.


  1. From your home directory, type the ls -l command.
    Who owns these files? To which group do they belong?
    How can you distinguish file entries from directory entries?
  2. Do a long listing of the file, /home/rsimms/uhistory. Who owns it?
    Can you move the file to your home directory? Why or why not?
    Can you copy the file to your home directory? Why or why not?
  3. Now that you have copied the file uhistory to your home directory,
    who owns it? What are the permissions?
  4. Display the contents of the file uhistory on your screen.
    Now take away read permission using the command:
    chmod -r uhistory
    Try to display the contents of the file as you did above. Does it work?
  5. Now give read permission back but take away write permission:
    chmod 444 uhistory
    Verify the success of the above command.
  6. Take away execute (search) permission from the misc directory:
    chmod -x misc
    List the contents of the misc directory using the ls command.
    Try to display the contents of the fruit file with the command:
    cat misc/fruit
    Try to change directories to misc.
  7. Give yourself back execute permission but take away read permission:
    chmod +x,-r misc
    Change your current directory to the misc directory.
    Try displaying the contents of the misc directory.
    Display the contents of the fruit file.
  8. Change back to your home directory and set the misc directory to full permissions:
    chmod 777 misc
  9. Set the permissions of your poems directory and its subdirectories so that you have full permissions as owner, but group and others have no write permission.
  10. Set all ordinary files under the poems directory to be read only for user, group, and others. We want everyone to read our poetry, but no one should modify it, including ourself.
    See if you can do this using a minimum number of commands. (hint: use filename expansion characters).
  11. Change the permissions of your bin directory so that you have full permission, group has read and execute, and all others have no permissions.
  12. Set the executable files under bin to have the following permissions:
    -r-xr-x---
    disallowing others outside the group from executing our commands.
  13. Change the group id of the following directories: class/labs, and class/exams to be users:
    chgrp users class/labs class/exams
  14. For the class directory set the permissions to 710.
    For the labs subdirectory, set permissions to 530.
    For the exams subdirectory, take away all permissions from group and others, leaving full permission for owner.
  15. Make all ordinary files under class/labs and class/exams be:
    read-write for owner
    read-only for group and
    no permission for others.
  16. For the edits directory, give yourself full permission, but no permission for group or others.
    For the ordinary files under edits, take away read permission from group, leaving everything else as it is.
  17. Add read permission for everyone to all the files in the misc directory.
  18. Run the umask command and note the three digit number displayed.
  19. Create an empty file called old and an empty directory called olddir:
    touch old; mkdir olddir
  20. Run the umask command giving it the argument: 000
    umask 000
  21. Create an empty file called new and an empty directory called newdir:
    touch new; mkdir newdir
  22. Look at the permissions of these four files you've created.
    Notice how they have changed. Can you figure out what umask is for?
  23. If you can't, try setting the umask to 777 and making a newer file.
    In any case, set your umask back to 002 with the command:
    umask 002

You have now finished this lab. To submit the results, enter the command:
submit