EAK Just Debian Guru Page :) Just another Linux weblog

2Jun/09Off

Centos 5 Multimedia Howto

Step 1: Add the Rpmforge Repo

rpm -Uhv http://apt.sw.be/redhat/el5/en/i386/RPMS.dag/rpmforge-release-0.3.6-1.el5.rf.i386.rpm

Step 2: Add the Macromedia Repo

rpm -Uhv http://linuxdownload.adobe.com/adobe-release/adobe-release-i386-1.0-1.noarch.rpm

Step 3: Install Multimedia Applications

yum -y install libdvdcss libdvdread libdvdplay libdvdnav lsdvd mplayerplug-in mplayer mplayer-gui compat-libstdc++-33 flash-plugin gstreamer-plugins-bad gstreamer-plugins-ugly

Step 4: Installing w32Codecs in order to play everything under the Sun.

wget www1.mplayerhq.hu/MPlayer/releases/codecs/mplayer-codecs-20061022-1.i386.rpm ; rpm -ivh mplayer-codecs-20061022-1.i386.rpm

wget www1.mplayerhq.hu/MPlayer/releases/codecs/mplayer-codecs-extra-20061022-1.i386.rpm; rpm -ivh mplayer-codecs-extra-20061022-1.i386.rpm

Kaynak:http://www.sklav.com/?q=node/2

Filed under: Desktop Comments Off
2Jun/09Off

Installing VirtualBox on a PAE Kernel System

Asagidaki islemleri yapmadan once bunlari yuklememiz gerekiyor yoksa kernel modul derlenmesi sirasinda sorunlar cikabilmektedir.

yum install kernel-devel
yum groupinstall "Development Tools"

Sonrada asagidaki adimlari uyguluyoruz.
I recently got stuck while trying to install Headless Virtualbox on a Centos 5.2 server per the directions at Howtoforge here. The RPM failed with the error that it couldn’t find the kernel source. I thought I had already installed kernel-devel, and confirmed that I did. The instructions were to define the KERN_DIR variable like so:

$ export KERN_DIR=/usr/src/kernels/2.6.18-92.1.22.el5-i686/
$ /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module [ OK ]
Removing old VirtualBox netflt kernel module [ OK ]
Removing old VirtualBox kernel module [ OK ]
Recompiling VirtualBox kernel module [ OK ]
Starting VirtualBox kernel module [FAILED]
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)

dmesg shows this:

vboxdrv: disagrees about version of symbol struct_module

Interesting!

After several missteps, it turns out there is a separate development rpm for the PAE kernel:

$ yum install kernel-PAE-devel

After that installs, we are good:

$ export KERN_DIR=/usr/src/kernels/2.6.18-92.1.22.el5-PAE-i686/
$ /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module [ OK ]
Removing old VirtualBox netflt kernel module [ OK ]
Removing old VirtualBox kernel module [ OK ]
Recompiling VirtualBox kernel module [ OK ]
Starting VirtualBox kernel module [ OK ]

Kaynak:http://systembash.com/content/installing-virtualbox-pae-kernel-centos/

2Jun/09Off

Installing the NVIDIA driver On Centos 5

The nvidia driver is not included with CentOS/RHEL 5 so we will need to use a 3rd party repository. Here we will be using the ATrpms repository.

1. Load up a terminal window if you are in the graphic interface.

2. Switch to the root user by entering the command “su -” (without the quotes) and typing in your root password

3. Edit the file /etc/yum.conf. Using nano we type the command “nano -w /etc/yum.conf”

4. If you have already configured yum to use the ATrpms repository then append “*nvidia-graphics*” to the end of the “includepkgs” line and skip the next setup. Otherwise continue on.

5. Add the following to the bottom of this file:

[atrpms]
name=EL $releasever - $basearch - ATrpms
baseurl=http://dl.atrpms.net/el$releasever-$basearch/atrpms/stable
gpgkey=http://ATrpms.net/RPM-GPG-KEY.atrpms
gpgcheck=1
enabled=1
exclude=*kmdl*i586*
includepkgs=*nvidia-graphics*

6. Save the file. In nano you press Ctrl-X, answer yes to the “Save modified buffer” question and then press enter on the file name to write.

7. If you have not previously setup ATrpms execute the following command:

rpm --import http://ATrpms.net/RPM-GPG-KEY.atrpms

8. Now execute the following command:

yum install nvidia-graphics169.07 nvidia-graphics169.07-kmdl-`uname -r`

9. Reboot your system and you will be using the nvidia driver.
Troubleshooting

Normally after installing the nvidia driver with the steps above your xorg.conf file should have automatically been updates to use the newer driver. If this did not happen or for some reason it has reverted then, as root, enter the following command:

nvidia-xconfig

This will switch you back to the nvidia driver.

Kaynak :http://www.linlap.com/wiki/configuring+a+nvidia+graphics+chip+for+centos+and+rhel+5

Filed under: Donanim Comments Off
14Apr/09Off

Whois aplication with python – ew.py test

Program Text dosya icindeki domain listesini sirayla whois cekerek bitis tarihlerini gostermektedir , iler leyen zamanda domain sahiplerine mail atmasinida planliyorum.
domainfile=open ('eakdomain.txt')

Dosyayi indirmek icin tiklayin bakim

Filed under: Programlama Comments Off
5Apr/09Off

Using iptables to rate-limit incoming connections


The iptables firewall has several useful extension modules which can be used to in addition to the basic firewall functionality. One of the more interesting of these extensions is the "recent" module which allows you to match recent connections, and perform simple throttling on incoming connections.

We've previously described keeping SSH access secure by limiting which users can connect, or just firewalling access so that only a small list of trusted IP addresses can connect. In most cases this is sufficient to protect your system.

However there are times when you have to allow arbitary incoming connections, when you are travelling for example.

In these situations you can open up your system to allow incoming connections and be the target of a dictionary attack - literally a machine trying to connect and login over and over again using usernames and passwords from a dictionary.

These attempts will be logged in your /var/log/auth.log file like this:

sshd[x]: Illegal user admin from aa.bb.cc.dd
sshd[x]: Illegal user test from aa.bb.cc.dd
sshd[x]: Illegal user guest from aa.bb.cc.dd

In this situation you can create a collection of firewalling rules which will deny access from remote clients who attempt to connect "too many" times.

If you have an existing firewall in place, using iptables, then adding the rules is very straightforward.

The way the recent module works is fairly straightforward, you basically add IP addresses to a list, which can then be used in the future to test connection attempts against. This allows you to limit the number of connections against either a number of seconds, or connection attempts. In our example we'll do both.

An example is probably the simplest way to illustrate how it works. The following two rules will limit incoming connections to port 22 to no more than 3 attemps in a minute - an more than that will be dropped:

iptables -I INPUT -p tcp --dport 22 -i eth0 -m state --state NEW -m recent --set

iptables -I INPUT -p tcp --dport 22 -i eth0 -m state --state NEW -m recent --update --seconds 60 --hitcount 4 -j DROP

The --state flag takes a comma seperated list of connection states as an argument, by using "--state NEW" as we did we make sure that only new connections are managed by the module.

The --set parameter in the first line will make sure that the IP address of the host which initiated the connection will be added to the "recent list", where it can be tested and used again in the future i.e. in our second rule.

The second rule is where the magic actually happens. The --update flag tests whether the IP address is in the list of recent connections, in our case each new connection on port 22 will be in the list because we used the --set flag to add it in the preceeding rule.

Once that's done the --seconds flag is used to make sure that the IP address is only going to match if the last connection was within the timeframe given. The --hitcount flag works in a similar way - matching only if the given count of connection attempts is greater than or equal to the number given.

Together the second line will DROP an incoming connection if:

* The IP address which initiated the connection has previously been added to the list and
* The IP address has sent a packet in the past 60 seconds and
* The IP address has sent more than 4 packets in total.

You can adjust the numbers yourself to limit connections further, so the following example will drop incoming connections which make more than 2 connection attempts upon port 22 within ten minutes:

iptables -I INPUT -p tcp --dport 22 -i eth0 -m state --state NEW -m recent \
--set

iptables -I INPUT -p tcp --dport 22 -i eth0 -m state --state NEW -m recent \
--update --seconds 600 --hitcount 2 -j DROP

If you wish to test these rules you can script a number of connection attempts from an external host with the netcat package.

The following script attempts to connect to the IP address 192.168.1.1 5 times. The first couple of attempts you should see a welcome banner such as "SSH-2.0-OpenSSH_3.8.1p1 Debian-8.sarge.4" - after that the script will hang as it's packets are dropped and no response is sent:

#!/bin/bash

for i in `seq 1 5` ; do
echo 'exit' | nc 192.168.1.1 22 ;
done

There's a lot of documentation on the netfilter/iptables firewall, and it's available modules which you can find in the Netfilter Extension HOWTO.

This HOWTO contains documentation on many different modules, along with examples. A recommended read if you're interested in Linux firewalling.

If you wish to experiment with rules and testing it's worth remembering how to remove all active rules. The following commands will flush your iptables filewall, and remove all currently active rules:

iptables -F
iptables -X

Filed under: Guvenlik, Sunucu Comments Off
1Apr/09Off

Downloading an Entire Web Site with wget

If you ever need to download an entire Web site, perhaps for off-line viewing, wget can do the
job—for example:

$ wget \
     --recursive \
     --no-clobber \
     --page-requisites \
     --html-extension \
     --convert-links \
     --restrict-file-names=windows \
     --domains website.org \
     --no-parent \
         www.website.org/tutorials/html/

This command downloads the Web site www.website.org/tutorials/html/.

The options are:

  • --recursive: download the entire Web site.
  • --domains website.org: don't follow links outside website.org.
  • --no-parent: don't follow links outside the directory tutorials/html/.
  • --page-requisites: get all the elements that compose the page (images, CSS and so on).
  • --html-extension: save files with the .html extension.
  • --convert-links: convert links so that they work locally, off-line.
  • --restrict-file-names=windows: modify filenames so that they will work in Windows as well.
  • --no-clobber: don't overwrite any existing files (used in case the download is interrupted and
    resumed).

Alintidir[http://www.linuxjournal.com/content/downloading-entire-web-site-wget]
[ad#co-1]

Filed under: Desktop Comments Off
18Mar/096

Bypassing Video playback problems in Compiz Fusion / Beryl

Gstreamer

That’s the default Ubuntu player, used by Totem. To correctly visualize you video files with Totem proceed as follows:

1) Open a terminal and enter:

gstreamer-properties

2) Move to the Video tag.
3) In default video plugin select “X Window System (without Xv)”.
4) Click on try to verify if it works fine.
5) Close this window, problems solved.

Filed under: Desktop 6 Comments
17Feb/091

How to read debian.eakcorp.net on rss reader

hi,

i using liferea rss reader for rss, describes the use of images liferea I hope preparing here is your putting benefits.[ad#ad-1]

Filed under: Desktop 1 Comment
9Feb/090

Debian web site

Debian kullanimi sirasinda faydasini gordugum ve goreceginize inandigim web siteleri.

debian.org
http://www.debianhelp.org/
http://www.debianhelp.co.uk/
http://www.debianadmin.com/
http://www.debian-administration.org/

[ad#ad-1]

Filed under: Uncategorized No Comments
9Feb/090

Blocking a DNS DDOS using the fail2ban package

[ad#ad-1]
Are you tired of getting multi-thousand line emails from the logcheck package that contain multiple reports of denied queries from named? If so this article will show how you can reject these DDOS attempts via the fail2ban package.

apt-get install fail2ban

mkdir /var/log/named
chmod a+w /var/log/named

Next, edit /etc/bind/named.conf.local and add the following lines

logging {
channel security_file {
file "/var/log/named/security.log" versions 3 size 30m;
severity dynamic; print-time yes; };
category security { security_file; };
};

now to set up fail2ban. Edit the /etc/fail2ban/jail.conf file and change from:

[named-refused-udp]
enabled  = false to:true
[named-refused-tcp]
enabled  = false to true

Then restart fail2ban in the usual manner,

/etc/init.d/fail2ban restart

read more article for click