Fedora Linux Legacy Blog

Saturday, July 26, 2008

How To Install Adobe Flash Player 10 in Fedora

Adobe had release the latest flash player version 10. If you currently have a lower version, it is adviseable to install the latest release as it fixes some issues with the lower version.

Install Flash Player 10

Step One

Using Fedora, it is important to uninstall the lower Flash Player version. To remove old flash player

# rpm -qa flash*

# rpm -e flash-lower-version.rpm

Step Two

Download Flash Player 10 rpm for linux from here. Alternatively, install it direct using rpm package installer

# rpm -ivh http://download.macromedia.com/pub/labs/flashplayer10/flashplayer10_install_linux_070208.i386.rpm

If you choose to download the latest Flash Player 10, launch rpm package installer to install your downloaded file like so

# rpm -ivh flashplayer10_install_linux_070208.i386.rpm

Step Three

Close and start your browser. Go to flash-enabled websitesand test Flash Player 10 Beta.

It works out right like a charm. All is done.

How To Add and Install Alternative Liberation Fonts

Fedora project endorses liberation fonts. Fedora encourages to install liberation fonts as one of alternative linux fonts that also comes with Fedora installer images. By default X installation, liberation fonts are installed by default.

The Liberation Fonts are intended to be replacements for the three most commonly used fonts on Microsoft systems namely Times New Roman, Arial, and Courier New. If you wish to have these fonts into your system, read on.

To install liberation fonts, simply launch yum to do so

# yum -y install liberation-fonts

All is done.

Friday, July 25, 2008

Digg it: Top 1 Supercomputer is powered by Fedora

Fedora is stable linux distro around which offers the latest, razor-sharp and bleeding edge linux applications and softwares around the OS world. Yes, Fedora is stable and is good alternative on server setup.

Inviting you to quick digg Fedora's super empowering the #1 super computer of the world.

Digg Here

Thanks

How To Send System Message To FTP Clients via TCP Wrapper

From recent posts, granting access (allow and deny) restrictions to particular services is a good additional security practice anybody could use of nowadays. There are some system admins that prefer sending system message or account status when denying access to particular clients or hosts.

Sending service message or service system status to particular hosts or group of hosts can lessen on-site technical phone calls during scheduled system maintenance works while making connecting clients informed and be reminded of your service message.

Send System Message to FTP Clients via TCP Wrapper

Step One

Backup and modify /etc/hosts.allow to reflect the below similar lines. Assuming that VsFTPd daemon service is running as current FTP server.

vsftpd: 83.83.83.83 : twist /bin/echo "220 %h FTP account has expired, please renew."

vsftpd: 192.168.100.100 : twist /bin/echo "220 %h has been banned, go away!"

vsftpd: 192.168.100.10 : twist /bin/echo "220 %h We are on scheduled maintenance, try later. Thanks"

The above instructs TCP wrapper to deny access to

83.83.83.83

192.168.100.100

192.168.100.10

Each has separate log message to be sent to the connecting clients.

Save and exit.

No restart is needed from any daemon services. Portmap and Rpcbind daemon services are not required to be enabled from this setup.

Step Two

Verify changes with your host access restrictions via TCP wrapper. Using a separate linux host

# telnet domain.com 21

# ftp domain.com

Alternatively, from a separate windows host, launch your FTP client software and verify the message by connecting to domain.com as an example.

A similar output would be

Trying domain.com...
Connected to domain.com
Escape character is '^]'.
220 We are on scheduled maintenance, come back later.
Connection closed by foreign host.

This would work out right from RedHat, CentOS, White OS and Fedora boxes.

All is done

Intel Switches From Ubuntu To Fedora For Mobile Linux

An anonymous reader writes

"According to a report on heise, Intel is switching from using Ubuntu to the Fedora Project for the second version of the Intel supported Mobile & Internet Linux Project Moblin, citing a desire to use RPM package management."

Intel Switches From Ubuntu To Fedora For Mobile Linux

An anonymous reader writes

"According to a report on heise, Intel is switching from using Ubuntu to the Fedora Project for the second version of the Intel supported Mobile & Internet Linux Project Moblin, citing a desire to use RPM package management."

How To Create Separate SSH Log File for Specific SSH Clients

By default, OpenSSH dumps log messages to /var/log/secure authentication log file. The need to log particular host or group of IP address to separate SSH log file is needed at times to further log SSH details for further record and monitoring.

Create Separate SSH Log File for Particular SSH Client Log Attempts

Here's how to log particular SSH client to separate SSH log file.

Step One

Create the separate SSH log file

# touch /var/log/abusive.log

and make sure it is readable and writable by root.

# chmod 600 /var/log/abusive.log

Step Two

Modify /etc/hosts.allow and append a similar line shown below

sshd: 83.83.83.83 : spawn /bin/echo `/bin/date` from %h %u >> /var/log/abusive.log

Alternatively, you can log a group of hosts to separate SSH log file

sshd: *.google.com : spawn /bin/echo `bin/date` from %h %c >> /var/log/abusive.log

To group SSH clients to particular log gile

sshd: *.yahoo.com : spawn /bin/echo `bin/date` from %h %c >> /var/log/yahoo-ssh.log

Save and exit. Noticed that we use the SPAWN tcp wrapper operator to log every hosts under google.com and dump the corresponding date of SSH login attempt to /var/log/abusive.log SSH log file.

Now, to log to separate SSH log file and completely deny particular host under google.com domain, simply

sshd: *.google.com : spawn /bin/echo `bin/date` from %h %c >> /var/log/abusive.log : deny

Save and exit.

No need to restart any services like SSH or XInet .

Supported Parameter Expansions

Below is a list of supported expansions:

%a — The client's IP address.

%A — The server's IP address.

%c — Supplies a variety of client information, such as the username and hostname, or the username and IP address.

%d — The daemon process name.

%h — The client's hostname (or IP address, if the hostname is unavailable).

%H — The server's hostname (or IP address, if the hostname is unavailable).

%n — The client's hostname. If unavailable, unknown is printed. If the client's hostname and host address do not match, paranoid is printed.

%N — The server's hostname. If unavailable, unknown is printed. If the server's hostname and host address do not match, paranoid is printed.

%p — The daemon process ID.

%s — Various types of server information, such as the daemon process and the host or IP address of the server.

%u — The client's username. If unavailable, unknown is printed.

Monitoring Separate SSH Log File

# tailf /var/log/abusive.log

Log File

Similar SSH log lines from /var/log/abusive.log would be

Fri Jul 25 10:26:52 WAT 2008 from hostname.google.com

The above should work out right with RedHat, CentOS, Fedora, White OS distros.

All is done.

How To Allow and Deny SSH Access To Selected Hosts and IP Addresses

With default OpenSSH installation, SSH allows access to any clients. This retriction can be configured to allow SSH access only to certain hosts and IP addresses to decrease unauthorized SSH login attempts to known and particular computer hosts and IP addresses only.

SSH Access Restrictions via TCP Wrapper

Step One

1. Backup and modify /etc/hosts.allow

# nano -w /etc/hosts.allow

Allow and Deny SSH Access to Specific Hosts / IP Addresses

To allow SSH access to IP address 83.83.83.83 , modify /etc/hosts.allow to reflect the below lines

sshd: 83.83.83.83

Access will be granted if both pairs represent a match. TCP wrappers should allow access if a matching SSH protocol and an IP address 83.83.83.83 is present from the requesting connection.

To allow SSH access to all hosts and/or subdomain(s) that is part of the parent domain yahoo.com

sshd: .yahoo.com

To grant SSH access to multiple IP address, simply append multiple address as shown

sshd: 83.83.83.83 127.0.0.1 83.83.83.84 192.168.1.1

To allow SSH access to starting IP address

sshd: 192.168.

To allow SSH access with network IP netmask

sshd: 192.168.1.0/255.255.255.0

To use asterisk (*) from /etc/hosts.allow

sshd: *.yahoo.com

To specify a large set of IP addresses and known hosts from a file

sshd: /etc/allowed.txt

To specify multiple hosts and IP addresses with excemption using except TCP wrapper operator

sshd: .yahoo.com EXCEPT search.yahoo.com

To allow access to everyone under .yahoo domain except 83.83.83.83

sshd: *.yahoo.com EXCEPT 83.83.83.83

To specify multiple SSH access restriction with multiple lines

sshd: 111.111.111.111

sshd: 222.222.222.222

If the above access lists rules appears inside /etc/hosts.allow, TCP wrappers allows the request. If the above lines appears from /etc/hosts.deny, TCP wrappers deny the request.

Step Two

To deny any other ssh access except from the ones listed from /etc/hosts.allow, backup and modify /etc/hosts.deny file

ALL: sshd

Save and exit.

All is done.

The GNU/Linux operating system is blessed to have sound partition management tools like GParted which are very easy to use. However, when it comes to the management of 'virtual partitions' known as volumes, things are quite different. There is Linux Volume Management, or LVM for short, however it can only really be used from the command line...

Subscription

Categories

Get Fedora

Recent Posts

Blog Archive

Saturday, July 26, 2008

Friday, July 25, 2008

Thursday, July 24, 2008

Search

Make Money

Live Traffic

Recent Referrer

Sponsors