LibreOffice an Open Source Office Productivity suite a very good alternative to Microsoft office Products

LibreOffice an Open Source Office Productivity suite a very good alternative to Microsoft office Products or any other propriety office productivity suites.

LibreOffice is a office suite as famous Open Source Software being used widely for word processing. It  is a fork of OpenOffice.org  & developed by The Document Foundation in 2010. The LibreOffice suite is set of programs to do word processing, spreadsheets, slideshows, diagrams and drawings, maintain databases, and compose math formulas.

It is perfect alternative to any office productivity suite when it comes to word processing. LibreOffice announced new version of LibreOffice 4.2.2. People who uses Linux as operating system enjoys this office productivity suite as pre-installed application when they install various distributions of Linux on their computers.

We can easily install LibreOffice on: Continue reading “LibreOffice an Open Source Office Productivity suite a very good alternative to Microsoft office Products”

SETTING UP LINUX YUM REPOSITORY IN REDHAT/CENTOS

when we implement the REDHAT based servers, when we dont have the proper license we will be facing a lot of issues for installing the softwares. So to overcome the issue we need to setup the LOCAL REPOSITORY server. this  will eliminate the installation issues.Below i have explained how to setup the repo server step-by-step.

SETTING UP LOCAL REPOSITORY SERVER IN YOUR REDHAT/CENTOS:

PREREQUISITES:

1.HTTPD SERVER
2.CREATEREPO RPM

Continue reading “SETTING UP LINUX YUM REPOSITORY IN REDHAT/CENTOS”

Installing Nagios core on RHEL / CENTOS 5.x – RHEL / CentOS 6.x Fedora 15/16/17/18/19/20

What is Nagios

An enterprise-class monitoring and alerting solution that provides organizations with extended insight of their IT infrastructure before problems affect critical business processes.

Requirements

We require following things for Installing Nagios:
These are Just Pre-requisites. We need them to other things work …

1. Apache and PhP (php is optional)
2. gcc, glib, glibc-common, gd and gd-devel

Continue reading “Installing Nagios core on RHEL / CENTOS 5.x – RHEL / CentOS 6.x Fedora 15/16/17/18/19/20”

Authentication Server: Setting up FreeRADIUS in RHEL, CENTOS

Installing FreeRADIUS

  1. Head over to the FreeRADIUS site, http://www.freeradius.org/, and download the latest release.
    
       # cd /usr/local/src
       # wget ftp://ftp.freeradius.org/pub/radius/freeradius-1.0.0.tar.gz
       # tar zxfv freeradius-1.0.0.tar.gz
       # cd freeradius-1.0.0
      
  2. Configure, make and install:
    
        # ./configure
        # make
        # make install
       

    You can pass options to configure. Use ./configure –help or read the README file, for more information.

The binaries are installed in /usr/local/bin and /usr/local/sbin. The configuration files are found under /usr/local/etc/raddb.

If something went wrong, check the INSTALL and README included with the source. The RADIUS FAQ also contains valuable information.

3.2. Configuring FreeRADIUS

FreeRADIUS has a big and mighty configuration file. It’s so big, it has been split into several smaller files that are just “included” into the main radius.conf file.

There is numerous ways of using and setting up FreeRADIUS to do what you want: i.e., fetch user information from LDAP, SQL, PDC, Kerberos, etc. In this document, user information from a plain text file, users, is used.

Tip The configuration files are thoroughly commented, and, if that is not enough, the doc/ folder that comes with the source contains additional information.

Configuring FreeRADIUS

  1. The configuration files can be found under /usr/local/etc/raddb/
    
        # cd /usr/local/etc/raddb/
       
  2. Open the main configuration file radiusd.conf, and read the comments! Inside the encrypted PEAP tunnel, an MS-CHAPv2 authentication mechanism is used.
    1. MPPE [RFC3078] is responsible for sending the PMK to the AP. Make sure the following settings are set:
      
          # under MODULES, make sure mschap is uncommented!
          mschap {
            # authtype value, if present, will be used
            # to overwrite (or add) Auth-Type during
            # authorization. Normally, should be MS-CHAP
            authtype = MS-CHAP
      
            # if use_mppe is not set to no, mschap will
            # add MS-CHAP-MPPE-Keys for MS-CHAPv1 and
            # MS-MPPE-Recv-Key/MS-MPPE-Send-Key for MS-CHAPv2
            #
            use_mppe = yes
      
            # if mppe is enabled, require_encryption makes
            # encryption moderate
            #
            require_encryption = yes
      
            # require_strong always requires 128 bit key
            # encryption
            #
            require_strong = yes
      
            authtype = MS-CHAP
            # The module can perform authentication itself, OR
            # use a Windows Domain Controller. See the radius.conf file
            # for how to do this.
          }
          
    2. Also make sure the “authorize” and “authenticate” contains:
      
          authorize {
              preprocess
              mschap
              suffix
              eap
              files
          }
      
          authenticate {
      
               #
               #  MSCHAP authentication.    
               Auth-Type MS-CHAP {
                     mschap
                }
      
               #
               #  Allow EAP authentication.
               eap
           }
          
  3. Then, change the clients.conf file to specify what network it’s serving:
    
       # Here, we specify which network we're serving
       client 192.168.0.0/16 { 
            # This is the shared secret between the Authenticator (the 
            # access point) and the Authentication Server (RADIUS).
            secret          = SharedSecret99
            shortname       = testnet
        }
       
  4. The eap.conf should also be pretty straightforward.
    1. Set “default_eap_type” to “peap”:
      
            default_eap_type = peap
           
    2. Since PEAP is using TLS, the TLS section must contain:
      
          tls { 
              # The private key password
              private_key_password = SecretKeyPass77
              # The private key
              private_key_file = ${raddbdir}/certs/cert-srv.pem
              #  Trusted Root CA list
              CA_file = ${raddbdir}/certs/demoCA/cacert.pem
              dh_file = ${raddbdir}/certs/dh
              random_file = /dev/urandom
              }
          
    3. Find the “peap” section, and make sure it contain the following:
      
            peap {
              #  The tunneled EAP session needs a default
              #  EAP type, which is separate from the one for
              #  the non-tunneled EAP module.  Inside of the
              #  PEAP tunnel, we recommend using MS-CHAPv2,
              #  as that is the default type supported by
              #  Windows clients.
              default_eap_type = mschapv2
            }
            
  5. The user information is stored in a plain text file users. A more sophisticated solution to store user information may be preferred (SQL, LDAP, PDC, etc.).Make sure the users file contains the following entry:
    
       "testuser"      User-Password == "Secret149"