Was the operation successful? Explain.

File Permissions
Visualize and Change the File Permissions.
a. Navigate to /home/analyst/lab.support.files/scripts/.



[analyst@secOps ~]$ cd lab.support.files/scripts/

b. Use the ls -l command to display file permissions.



[analyst@secOps scripts]$ ls -l

total 60

-rwxr-xr-x 1 analyst analyst 190 Jun 13 09:45 configure_as_dhcp.sh

-rwxr-xr-x 1 analyst analyst 192 Jun 13 09:45 configure_as_static.sh

-rwxr-xr-x 1 analyst analyst 3459 Jul 18 10:09 cyberops_extended_topo_no_fw.py

-rwxr-xr-x 1 analyst analyst 4062 Jul 18 10:09 cyberops_extended_topo.py

-rwxr-xr-x 1 analyst analyst 3669 Jul 18 10:10 cyberops_topo.py

-rw-r--r-- 1 analyst analyst 2871 Apr 28 11:27 cyops.mn

-rwxr-xr-x 1 analyst analyst 458 May 1 13:50 fw_rules

-rwxr-xr-x 1 analyst analyst 70 Apr 28 11:27 mal_server_start.sh

drwxr-xr-x 2 analyst analyst 4096 Jun 13 09:55 net_configuration_files

-rwxr-xr-x 1 analyst analyst 65 Apr 28 11:27 reg_server_start.sh

-rwxr-xr-x 1 analyst analyst 189 Dec 15 2016 start_ELK.sh

-rwxr-xr-x 1 analyst analyst 85 Dec 22 2016 start_miniedit.sh

-rwxr-xr-x 1 analyst analyst 76 Jun 22 11:38 start_pox.sh

-rwxr-xr-x 1 analyst analyst 106 Jun 27 09:47 start_snort.sh

-rwxr-xr-x 1 analyst analyst 61 May 4 11:45 start_tftpd.sh

c. The touch command is very simple and useful. It allows for the quick creation of an empty text file. Use the command below to create an empty file in the /mnt directory:



[analyst@secOps scripts]$ touch /mnt/myNewFile.txt

touch: cannot touch '/mnt/myNewFile.txt': Permission denied



[analyst@secOps ~]$ ls -l /mnt

total 4

drwxr-xr-x 2 root root 4096 Mar 3 11:13 second_drive



[analyst@secOps ~]$ ls -ld /mnt

drwxr-xr-x 3 root root 4096 Mar 3 15:43 /mnt

d. The chmod command is used to change the permissions of a file or directory. As before, mount the /dev/sdb1 partition on the /home/analyst/second_drive directory created earlier in this lab:



[analyst@secOps scripts]$ sudo mount /dev/sdb1 ~/second_drive/

e. Change to the second_drive directory and list the contents of it:



[analyst@secOps scripts]$ cd ~/second_drive

[analyst@secOps second_drive]$ ls -l

total 20

drwx------ 2 root root 16384 Mar 3 10:59 lost+found

-rw-r--r-- 1 root root 183 Mar 3 15:42 myFile.txt

f. Use the chmod command to change the permissions of myFile.txt.



[analyst@secOps second_drive]$ sudo chmod 665 myFile.txt

[analyst@secOps second_drive]$ ls -l

total 20

drwx------ 2 root root 16384 Mar 3 10:59 lost+found

-rw-rw-r-x 1 root root 183 Mar 3 15:42 myFile.txt

The chmod command takes permissions in the octal format. In that way, a breakdown of the 665 is as follows:
6 in octal is 110 in binary. Assuming each position of the permissions of a file can be 1 or 0, 110 means rw- (read=1, write=1 and execute=0).
Therefore, the chmod 665 myFile.txt command changes the permissions to:
Owner: rw- (6 or 110 in octal)
Group: rw- (6 or 110 in octal)
Other: r-x (5 or 101 in octal)
g. The chown command is used to change ownership of a file or directory. Issue the command below to make the analyst user the owner of the myFile.txt:



[analyst@secOps second_drive]$ sudo chown analyst myFile.txt

[sudo] password for analyst:

[analyst@secOps second_drive]$ ls -l

total 20

drwx------ 2 root root 16384 Mar 3 10:59 lost+found

-rw-rw-r-x 1 analyst root 183 Mar 3 15:42 myFile.txt

[analyst@secOps second_drive]$

h. Now that analyst is the file owner, try appending the word ‘test’ to the end of myFile.txt.



[analyst@secOps second_drive]$ echo test >> myFile.txt

[analyst@secOps second_drive]$ cat myFile.txt

Yes. Analyst is the owner of the file and the permissions are still set to 665 as before. The permissions as they are, allow the owner and users in the analyst group to make changes to the file.