# make server.key -> then Enter the password

#make server.crt

# cp server.key /etc/pki/tls/private

# vi /etc/httpd/conf.d/ssl.conf

here change the Parameters
SSL Certificate File & SSL Certificate Key

# service httpd restart

Testing the SSL: https://systimanx.com -> It ask the certificate Key to verify.
]]> http://lakshmichandrakanth.wordpress.com/2008/03/03/fedore-apache2-ssl-enable-hints/feed/ 0 lakshmichandrakanth http://lakshmichandrakanth.wordpress.com/2008/02/27/how-to-setup-nis-for-a-linux-network/ http://lakshmichandrakanth.wordpress.com/2008/02/27/how-to-setup-nis-for-a-linux-network/#comments Wed, 27 Feb 2008 21:11:00 +0000 lakshmichandrakanth http://lakshmichandrakanth.wordpress.com/2008/02/27/how-to-setup-nis-for-a-linux-network ]]> Introduction

The NIS system works by designating one (or more) machine in the network as a NIS server, and the rest as NIS clients. The server acts as the central repository for all user names, passwords, and groups. The data is replicated from the regular /etc/passwd file to NIS databases that are normally DBM format.

When a client needs to check the password of someone who is trying to log in, it sends the request to the server, and the server comes back with the result (correct password or not).

Setting up the Server

Installing the software

On the server, you need to install a package called ypserv. This can be done by urpmi on Mandrake, or apt-get on Debian.

Setting the NIS Domain Name

After installing the above package, you have to select and set a NIS Domain Name that will be used by both the server and the client. On some systems you can do so by running the domainname command. On others, you can just add it to a configuration file.

On Mandrake, you need to edit the file: /etc/sysconfig/network and add the following line to it:

NISDOMAIN=somename

Where somename is a name that you choose for the NIS Domain Name for your network.

Initializing NIS files

Then you have to convert the existing passwd, group and shadow files that contain user information and password to the NIS DBM format. You can do this using the following command:

/usr/lib/yp/ypinit -m

Updating the NIS files

From now on, every time you add a user, delete a user, you have to update the NIS database. You can do this using the command:

make -C /var/yp

If you want, you can setup a cron job to run every hour or every day and update the database for you automatically if it detects a change.

Starting the NIS server

Now you have to start the NIS server by entering the following command:

/etc/init.d/ypserv start

The server is now ready to handle authentication requests from the clients.

Setting up the Client machines

Installing the software

On the client, you need the yp-tools package, which depends on the ypbind package.

Configuring the software

First you must setup the NIS Domain Name. See above for how this is done.

Then, you must edit the /etc/yp.conf file, and point it to the appropriate server and domain name. Remember that the domain name must be the same that you set for the server. For example, add the following line:

domain somedomain server somehost

Modifying nsswitch.conf

The /etc/nsswitch.conf file lists the order for how lookups for various things are done, such as DNS lookup, user authentication, and the like. In order to make lookups for user authentication faster, change the following section in this file from:

passwd:     files nisplus nisshadow:     files nisplus nisgroup:      files nisplus nis

To the following:

passwd:     nis files nisplusshadow:     nis files nisplusgroup:      nis files nisplus

Deleting the existing users

If this system had local users before you install NIS, then it is a good idea to delete those users from the local machine before proceeding, provided that they have been added to the server. You can use the administration GUI that comes with your distribution to do this, or the userdel command.

Starting the NIS service

Start the NIS client service by entering:

/etc/init.d/ypbind start

Conclusion

Assuming you have done the above steps correctly, you can now handle all client authentication by using NIS.

This process ultimately looks for the default boot device and reads the boot program from the boot block which is located on the 1-15 blocks of boot device. The boot block contains the ufs file system reader which is required by the next boot processes.

The ufs file system reader opens the boot device and loads the secondary boot program from /usr/platform/`uname –i`/ufsboot ( uname –i expands to system architecture type)

The boot program above loads a platform specific kernel along with a generic solaris kernel. The kernel initialize itself and load modules which are required to mount the root partition for continuing the booting process.

The booting process undergoes the following phases afterwards :
1) init phase
2) inittab file
3) rc scripts & Run Level

INIT phase : Init phase is started by the execution of /sbin/init program and starts other processes after reading the /etc/inittab file as per the directives in the /etc/inittab file .
Two most important functions of init are
a) It runs the processes to bring the system to the default run level state ( Run level 3 in Solaris , defined by initdefault parameter in /etc/inittab )
b) It controls the transition between different run levels by executing appropriate rc scripts to start and the stop the processes for that run level.
/etc/inittab file

This file states the default run level and some actions to be performed while the system reaches up to that level. The fields and their explanation are as follows

:S3:3:wait:/sbin/rc3 > /dev/console 2>&1 < /dev/console

S3 denotes a identification if the line
3 is run level
wait is action to be performed
/sbin/rc3 is the command to be run.
So the fields in the inittab are Identification : run level : action : process.The complete line thus means run the command /sbin/rc3 at run level 3 and wait until the rc3 process is complete.The action field can have any of the following keywords:
Initdefault : default run level of the system
Respawn : start and restart the process if it stops.
Powerfail : stop on powerfail
Sysinit : start and wait till console in accessible .
Wait : wait till the process ends before going on to the next line.

RC scripts & Run Levels
Rc scripts performs the following functions :
a) They check and mount the file systems
b) Start and stop the various processes like network , nfs etc
c) Perform some of the house keeping jobs.
System goes in to one of the following run level after booting depending on default run level and the commands issued for changing the run level to some other one.
0 Boot prom level ok> or > prompt in Sun.
1 Administrative run level . Single user mode
2 Multiuser mode with no resource sharing .
3 Multiuser level with nfs resource sharing
4 Not used
5 Shutdown & power off (Sun 4m and 4u architecture )
6 Reboot to default run levelS s Single user mode user logins are disabled.

Broadly speaking the running system can be in any of the folloing state
Single user – Minimum processes running , user logins disabled and root password is required to gain access to the shell .
Multiuser – All system processes are running and user logins are permitted

Run level of a desired state is achieved by a number of scripts executed by the rc program the rc scripts are located in /etc/rc0.d , /etc/rc1.d , /etc/rc2.d , /etc/rc3.d & /etc/rcS.d directories .

All the files of a particular run level are executed in the alphanumeric order .Those files beginning with letter
S starts the processes and those beginning with
K stops the processes.

Installation

Obtain Jakarta Tomcat from http://jakarta.apache.org/. Tomcat is all in Java, download the binary version containing the class files. The lastest supported version of Jakarta Tomcat is 4.1.x.
Move or copy the file into the /usr/local directory:
jakarta-tomcat-4.1.31.tar.gz /usr/local
-or-
mv jakarta-tomcat-4.1.31.tar.gz /usr/local
Change user to root user using the su command.
Change directory to the /usr/local where you moved or copied the jakarta-tomcat compressed file to cd /usr/local/.
Use the tar command to untar the file for the compressed file:
-zxvf jakarta-tomcat-4.1.31.tar.gz
(If the tar command does not support gunzip for a .gz file, issue a gunzip command before the tar command.)
gunzip jakarta-tomcat-4.1.31.tar.gz
tar -xvf jakarta-tomcat-4.1.31.tar
For simplicity, create a symbolic link as follows:
-s /usr/local/ jakarta-tomcat-4.1.31 /usr/local/tomcat
Create a JAVA_HOME variable that points to the Java SDK installation and export it:

JAVA_HOME=
export JAVA_HOME

Starting and Stopping the Tomcat Daemon

The Tomcat daemon is started and stopped by running a shell script as follows:

To start the Tomcat daemon, use bash-2.03# /usr/local/tomcat/bin/startup.sh.
To stop the Tomcat daemon, use bash-2.03# /usr/local/tomcat/bin/shutdown.sh.

Troubleshooting Jakarta Tomcat Service

Check the log files in /usr/local/tomcat/logs and see if there is any useful information there.
Check the /var/adm/messages.

Below are some common error messages that can occur:

“ERROR: java.net.BindException: Address already in use:8080”

Ensure that nothing else is listening on port 8080:

netstat -na grep 8080

If no other program is using it then you should not get any results.

“ERROR: The JAVA_HOME environment variable is not defined correctly.
This environment variable is needed to run this program.
NB: JAVA_HOME should point to a JDK not a JRE”

Ensure the JAVA_HOME variable is pointing to the correct location. It must point to the JAVA SDK installation package such as j2sdk1.4.2x.

Use the echo $JAVA_HOME command to check its value.

The result should be /usr/java/j2sdk1.4.2_05.

Verifying and Testing Installation

verify that the daemon is running, type bash-2.03# ps –ef grep tomcat.
result is similar to the following:

/usr/java/j2sdk1.4.2_05/bin/java – … =/usr/local/jakarta-tomcat

a Web browser on the local server and go to the following URL:

http://localhost:8080

This should direct one to the Tomcat main page.

ddns-update-style interimignore client-updates

subnet 192.168.1.0 netmask 255.255.255.0 {

  # The range of IP addresses the server  # will issue to DHCP enabled PC clients  # booting up on the network

  range 192.168.1.201 192.168.1.220;

  # Set the amount of time in seconds that  # a client may keep the IP address

 default-lease-time 86400; max-lease-time 86400;

  # Set the default gateway to be used by  # the PC clients

  option routers 192.168.1.1;  # Don't forward DHCP requests from this  # NIC interface to any other NIC  # interfaces

  option ip-forwarding off;

  # Set the broadcast address and subnet mask  # to be used by the DHCP clients

 option broadcast-address 192.168.1.255; option subnet-mask 255.255.255.0;

  # Set the DNS server to be used by the  # DHCP clients

 option domain-name-servers 192.168.1.100;

  # Set the NTP server to be used by the  # DHCP clients

  option nntp-server 192.168.1.100;

  # If you specify a WINS server for your Windows clients,  # you need to include the following option in the dhcpd.conf file:

 option netbios-name-servers 192.168.1.100;

  # You can also assign specific IP addresses based on the clients'  # ethernet MAC address as follows (Host's name is "laser-printer":

 host laser-printer {     hardware ethernet 08:00:2b:4c:59:23;    fixed-address 192.168.1.222;  }}## List an unused interface here#subnet 192.168.2.0 netmask 255.255.255.0 {