Overview: Information technology professionals often deal with issues related to

Question

Overview: Information technology professionals often deal with issues related to file permissions, security, and logs.

This milestone will allow you to work with these important skills, which you will likely need in the field. Prompt: For this milestone, you will complete several tasks assigned by your manager within the *NIX environment.

Specifically, the following critical elements must be addressed in this milestone:

III. File Permissions, Security, and Logs In this section, you will investigate three trouble tickets that you have received regarding some issues that have arisen related to the UNIX accounts of three employees.

A. Issues with UNIX Accounts: For each issue listed, find the problem (document this by taking a screenshot of the incorrect configuration and a screenshot of the error message within the corresponding log file) and document the corrective actions to resolve each problem.

1. Employee 1 (Bob): Contacted by the Information Assurance (IA) Department and informed that his account is in violation of company policy and that his password is visible in plain-text. His account was locked. Incorrect configuration (screenshot): Error message in log (screenshot): Corrective actions (typed response)?

2. Employee 2 (Frank): Unable to log into his UNIX account. He receives the error message “su: failed to execute /dev/null: Permission denied.” Incorrect configuration (screenshot): Error message in log (screenshot): Corrective actions (typed response)?

3. Employee 3 (Henry): Reports that he receives the following error message when he logs into his UNIX account: “warning: cannot change directory to /home/henry: Permission denied” followed by the error “-bash: /home/henry/.bash_profile: Permission denied”. Oddly, his command prompt is different from what he usually sees as well. What is wrong (typed response)? Corrective actions (typed response)? B. Correct Permissions: You received a trouble ticket indicating that the SLASH/data directory is no longer readable. Correct the permissions to user read/write/execute, group read/write, and world read. Perform an ls -la of the SLASH/data directory and take a screenshot of the output. Paste the screenshot here:

C. Reading Log Files: You must check the last few lines of output of a few important log files. Tail the last 5 lines of the messages log file and the last 5 lines of the secure log file. Screenshot the output from both tail commands. Paste the screenshot here: Work Verification: Take a screenshot (or multiple screenshots if needed) that captures the output of the pwd and history commands. Paste these screenshots here:

Explanation / Answer

1)the problem is because UNIX PASSWORD SYNC is not set properly.if it not sets properly plain text password will be visible in debugging logs

Global

Unix password sync=yes

2)The problem is with permission to /dev

Change permission as below

# chmod a+x /dev

# chmod a+r /dev

3)Try the command and check permission for the root

ls -la filename.

The problem is with root don't have permission

So change permission to root .

B)chmod 764 filename.

C)tail -n 5 message log

Tail -n 5 secure log

Related Questions

Navigate

• Browse (All)
• Browse O
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.