Technical requirements Tips for the exercisePractice exercise 1ExercisesExercise 1 resolution1. Configuring the time zone to GMT2. Allowing password-less login to the root user using SSH3. Creating a user named 'user' that can connect to the machine without a password4. The user 'user' should change their password every week, with 2 days' warning and 1 day of usage once expired5. The root user must be able to SSH as 'user' without a password, so that nobody can connect remotely as the root user using a password6. The user 'user' should be able to become root and execute commands without a password 7. When a user tries to log in over SSH, display a legal message about not allowing unauthorized access to this system8. SSH must listen on port 22222 instead of the default one9. Creating a group named 'devel'10. Making 'user' a member of 'devel'11. Storing user membership in a file called 'userids,' in a home folder for 'user'12. The user 'user' and root user should be able to connect to the localhost via SSH, without specifying the port, and default to compression for the connection13. Finding all man page names in the system, and putting the names into a file named 'manpages.txt'14. Printing usernames for users without a login, so they can be permitted access to the system, and printing the user ID and groups for each user15. Monitoring available system resources every 5 minutes without using cron, and storing them as /root/resources.log16. Adding a per-minute job to report the available percentage of free disk space and storing it in /root/freespace.log, so that it shows the filesystem and free space17. Configuring the system to only leave 3 days of logs18. Configuring log rotation for /root/freespace.log and /root/resources.log19. Configuring time synchronization against pool.ntp.org with fast sync20. Providing NTP server services for subnet 172.22.0.1/2421. Configuring system stats collection every minute22. Configuring the password length in the system for users to be 12 characters23. Creating a bot user called 'privacy,' which keeps its files only visible to itself by default24. Creating a folder named /shared that can be accessed by all users, and defaults new files and directories to still be accessible to users of the 'devel' group25. Configuring a network connection with IPv4 and IPv6 addressing named 'mynic,' using the provided data Ip6, as follows: 2001:db8:0:1::c000:207/64 g gateway 2001:db8:0:1::1 IPv4 192.0.1.3/24 gateway 192.0.1.126. Allowing the host to use a google hostname to reach www.google.com, and a redhat hostname to reach www.redhat.com 27. Reporting the files modified from those that the vendor distributed, and storing them in /root/altered.txt28. Making our system installation media packages available via HTTP under the path /mirror for other systems to use it as the mirror, and configuring the repository in our system. Removing the kernel packages from that mirror so that other systems (even ours) can't find new kernels. Ignoring the glibc packages from this repo to be installed without removing them29. As 'user,' make a copy of the /root folder in the /home/user/root/ folder, and keep it in sync every day, synchronizing additions and deletions30. Checking whether our system conforms to the PCI-DSS standard31. Adding a second hard drive of 30 GB to the system, but using only 15 GB to move the mirror to it, making it available at boot using compression and deduplication, and available under /mirror/mirror32. Configuring the filesystem to report at least 1,500 GB in size, to be used by our mirrors33. Creating a second copy of the mirror under /mirror/mytailormirror and removing all packages starting with k*34. Creating a new volume in the remaining space (15 GB) of the hard drive and using it to extend the root filesystem35. Creating a boot entry that allows us to boot into emergency mode in order to change the root password36. Creating a custom tuning profile that defines the readahead to be 4096 for the first drive and 1024 for the second drive – this profile should also crash the system should an OOM event occur37. Disabling and removing the installed httpd package, and setting up the httpd server using the registry.redhat.io/rhel8/httpd-24 image