RH302 Practice Questions

Do the following steps as:

1.vi /etc/security/time.conf

login;*;user15|user16;Sa0000-2400

2.vi /etc/pam.d/login

accountrequiredpam_time.so

For Time based authentication, we should configured in /etc/security/time.conf

Syntax of /etc/security/time.conf

services;ttys;users;times

services

is a logic list of PAM service names that the rule applies to.

ttys

is a logic list of terminal names that this rule applies to.

users

is a logic list of users to whom this rule applies.

times

the format here is a logic list of day/time-range entries the days are specified by a sequence of two character entries, MoTuSa for example is Monday Tuesday and Saturday. Note that repeated days are unset MoMo = no day, and MoWk = all weekdays bar Monday. The two character combinations accepted are

Mo Tu We Th Fr Sa Su Wk Wd Al

the last two being week-end days and all 7 days of the week respectively. As a final example, AlFr means all days except Friday.

pam_time modules checks the file /etc/security/time.conf for authentication. So, we should call the pam_time modules in /etc/pam.d/login.

Do the following steps as:

1.vi /etc/hosts.deny

sshd:ALL EXCEPT .example.com

or

1.vi /etc/hosts.deny

sshd:ALL

2.vi /etc/hosts.allow

sshd:.example.com

We can secure the services using tcp_wrappers. There are main two files, /etc/hosts.allow and /etc/hosts.deny.

There will be three stage access checking

- Is access explicitly permitted? Means permitted from /etc/hosts.allow?

- Otherwise, Is access explicitly denied? Means denied from /etc/hosts.deny?

- Otherwise, by default permit access if neither condition matched.

To deny the services we can configure /etc/hosts.deny file using ALL and EXCEPT operation. Pattern of /etc/hosts.allow and /etc/hosts.deny file is:

Demon_list:client_list:options

In Client list can be either domain name or IP address.

Do the following steps as:

1.ftp ftp://server1.example.com

2.Login as an anonymous and download the file.

3.Copy the file in /var/www/html if you downloaded in another location.

4.service httpd restart

5.Test using links: links http://station?.example.com

Check the SELinux context of index.html file, should like this:

-rw-r--r-- root root system_u:object_r:httpd_sys_content_t /var/www/html/index.html

If SELinux Context is mismatched, use the restorecon –R /var command

Do the following steps as:

1.vi /etc/hosts.deny

ALL:.cracker.org EXCEPT trusted.cracker.org

We can secure the services using tcp_wrappers. There are main two files, /etc/hosts.allow and /etc/hosts.deny.

There will be three stage access checking

-Is access explicitly permitted? Means permitted from /etc/hosts.allow?

- Otherwise, Is access explicitly denied? Means denied from /etc/hosts.deny?

- Otherwise, by default permit access if neither condition matched.

To deny the services we can configure /etc/hosts.deny file using ALL and EXCEPT operation. Pattern of /etc/hosts.allow and /etc/hosts.deny file is:

Demon_list:client_list:options

In Client list can be either domain name or IP address.

Do the following steps as:

1.vi /etc/httpd/conf/httpd.conf

ServerNamestation?.example.com

DocumentRoot /var/www/station?

DirectoryIndexindex.html

ServerAdminwebmaster@example.com

2.Create the directory and index page on specified path. (Index page can download fromftp://server1.example.comat exam time)

Check the SELinux context of index page , should like this:

-rw-r--r-- root root system_u:object_r:httpd_sys_content_t /var/www/html/index.html

If SELinux Context is mismatched, use the restorecon –R /var command

3.service httpd start|restart

4.chkconfig httpd on

Do the following steps as:

1.vi /etc/sysconfig/network

GATEWAY=192.168.0.254

OR

vi /etc/sysconf/network-scripts/ifcfg-eth0

DEVICE=eth0

BOOTPROTO=static

ONBOOT=yes

IPADDR=192.168.0.?

NETMASK=255.255.255.0

GATEWAY=192.168.0.254

2.service network restart

You should know about the /etc/inittab file, where default runlevel will define. And Much more runlevel specific Scripts are called here.

Actually that problem will occur if you don’t specify the default runlevel.

Reboot the system

Boot the System on single user mode.

Except for a normal boot of Linux, single-user mode is the most commonly used option. This is the system maintenance mode for experienced Linux administrators. It allows you to perform clean backups and restores to any partitions as needed from local hardware. It also allows you to run administration commands, recover or repair password and shadow password files, run filesystem checks, and so forth.

vi /etc/inittab and Write

id:runlevel:initdefault:

Standard Runlevels in RedHat Enterprise Linux

Runlevel

Description

0

Halt

1

Single-user mode, for maintenance (backups/restores) and repairs

2

Multiuser, without networking

3

Multiuser, with networking

4

Unused

5

X11, defaults to a GUI login screen. Logins bring the user to a GUI desktop.

6

Reboot (never set initdefault in /etc/inittab to this value!)

1. vi /etc/resolv.conf

Write : nameserver 192.168.0.254

Do the following steps as:

Quotas are used to limit a user's or a group of users' ability to consume disk space. This prevents a small group of users from monopolizing disk capacity and potentially interfering with other users or the entire system. Disk quotas are commonly used by ISPs, by Web hosting companies, on FTP sites, and on corporate file servers to ensure continued availability of their systems.

Without quotas, one or more users can upload files on an FTP server to the point of filling a filesystem. Once the affected partition is full, other users are effectively denied upload access to the disk. This is also a reason to mount different filesystem directories on different partitions. For example, if you only had partitions for your root (/) directory and swap space, someone uploading to your computer could fill up all of the space in your root directory (/). Without at least a little free space in the root directory (/), your system could become unstable or even crash.

You have two ways to set quotas for users. You can limit users by inodes or by kilobyte-sized disk blocks. Every Linux file requires an inode. Therefore, you can limit users bythe number of files or by absolute space. You can set up different quotas for different filesystems. For example, you can set different quotas for users on the /home and /tmp directories if they are mounted on their own partitions.

Limits on disk blocks restrict the amount of disk space available to a user on your system. Older versions of Red Hat Linux included LinuxConf, which included a graphical tool to configure quotas. As of this writing, Red Hat no longer has a graphical quota configuration tool. Today, you can configure quotas on RHEL only through the command line interface.

1. vi /etc/fstab

/dev/hda11/dataext3defaults,usrquota 1 2

2. Either Reboot the System or remount the partition.

Mount –o remount /dev/hda11 /data

3. touch /data/aquota.user

4. quotacheck –ufm /data

5. quotaon -u /data

6. edquota –u user1 /data

and Specified the Soft limit and hard limit on opened file.

To verify either quota is working or not:

Soft limit specify the limit to generate warnings to users and hard limit can’t cross by the user. Use the quota command or repquota command to monitor the quota information.