Freshnet.org

Munin 1.2.5-1 for Debian Sarge

Munin the monitoring tool surveys all your computers and remembers what it saw. It presents all the information in graphs through a web interface. Its emphasis is on plug and play capabilities. After completing a installation a high number of monitoring plugins will be playing with no more effort.

Using Munin you can easily monitor the performance of your computers, networks, SANs, applications, weather measurements and whatever comes to mind. It makes it easy to determine “what’s different today” when a performance problem crops up. It makes it easy to see how you’re doing capacity-wise on any resources.

Backport from SID here

Honeyd 1.5b for Debian Sarge

Honeyd is a small daemon that creates virtual hosts on a network. The hosts can be configured to run arbitrary services, and their personality can be adapted so that they appear to be running certain operating systems. Honeyd enables a single host to claim multiple addresses - I have tested up to 65536 - on a LAN for network simulation. Honeyd improves cyber security by providing mechanisms for threat detection and assessment. It also deters adversaries by hiding real systems in the middle of virtual systems.

backport from SID here

Monitoring Apache’s VirtualHost with Munin

Munin is a monitoring tool that “surveys all your computers and remembers what it saw. It presents all the information in graphs through a web interface” using the excellent RDDTool
Munin configuration is beyond the scope of this paper, please refer to documentation on Munin site.
The default munin plugins use the apache mod_status module, that stores data from all the virtual hosts, like in picture below

Obviously it can be more interesting to have separate data for each virtual host.
Bjørn Ruberg wrote a munin plugin for this, using a quite old apache module, mod_watch.

There is no debian package for this module.
Lurking around I have found the source and it’s easy to install on Debian

apt-get install apache-dev
tar -zxvf mod_watch318.tgz
cd mod_watch-3.18
make install-dynamic

NB With apache2 you need mod_watch4

***************************************************************
How to build mod_watch for Apache 2.0

To build a DSO version of mod_watch for Apache 2.0, first
verify the configuration at the top of the Makefile.dso then
type:

make -f Makefile.dso build
make -f Makefile.dso install

To build a static version of mod_watch for Apache 2.0:

cd (path to)/apache_2.0.44
mkdir -p modules/com/snert
mv (path to)/mod_watch-4.2 modules/com/snert/watch
./buildconf
./configure \
–enable-watch \
… (your other configuration options) …
make install

***************************************************************

Edit /etc/apache/modules.conf
and add the line in it:

LoadModule watch_module /usr/lib/apache/1.3/mod_watch.so

Now edit /etc/apache/httpd.conf
Add:

<IfModule mod_watch.c>
# Allows the URL used to query virtual host data:
#
# http://www.snert.com/watch-info
#
<Location /watch-info>
SetHandler watch-info
Order allow,deny
Allow from hostname
</Location>


# Intended for debugging and analysis of shared memory
# hash table and weenie files:
#
# http://www.snert.com/watch-table
#

<Location /watch-table>
SetHandler watch-table
Order allow,deny
Allow from hostname
</Location>

<Location /watch-list>
SetHandler watch-list
Order allow,deny
Allow from hostname
</Location>


</IfModule>

Change hostname with the munin-node host ip (tipical localhost)

Stop & start apache

/etc/init.d/apache stop && /etc/init.d/apache start

Test from command line that all works correctly

./mod_watch.pl -f ifRequests,ifDocuments http://www.freshnet.org/watch-list/
65236
11851
14:59.59
SERVER

And now install the plugin

cp mod_watch /usr/share/munin/plugins/
cd /etc/munin/plugins
ln -sf /usr/share/munin/plugins/apache_watch apache_watch_bytes
ln -sf /usr/share/munin/plugins/apache_watch apache_watch_documents
ln -sf /usr/share/munin/plugins/apache_watch apache_watch_requestes

Finally restart munin-node

/etc/init.d/munin-node restart

Et voilà the result A graph for each virtual host

Monitorare Virtual Host di Apache con Munin

Munin è uno splendido framework che permette di monitorare le prestazione dei vostri server e metterle in forma grafica tramite l’ottimo RDDTool
Per la configurazione di Munin vi rimando al sito o a questo tutorial in italiano
Nel particolare, apache viene monitorato tramite il modulo mod_status, che però restituisce i risultato per l’intero Apache
come nell’immagine seguente

Può essere più utile invece avere i dati divisi per ogni singolo Virtual Host

Bjørn Ruberg ha scritto un plugin per munin che fa questo, sfruttando un modulo di apache un po vecchiotto, mod_watch, che purtroppo non viene più distribuito.

Cercando un po’ in giro si trova però il sorgente ed è abbastanza semplice installarlo in debian

apt-get install apache-dev
tar -zxvf mod_watch318.tgz
cd mod_watch-3.18
make install-dynamic

NB Se usate apache due allora dovete usare mod_watch4

***************************************************************
How to build mod_watch for Apache 2.0

To build a DSO version of mod_watch for Apache 2.0, first
verify the configuration at the top of the Makefile.dso then
type:

make -f Makefile.dso build
make -f Makefile.dso install

To build a static version of mod_watch for Apache 2.0:

cd (path to)/apache_2.0.44
mkdir -p modules/com/snert
mv (path to)/mod_watch-4.2 modules/com/snert/watch
./buildconf
./configure \
–enable-watch \
… (your other configuration options) …
make install

***************************************************************

Modifichiamo /etc/apache/modules.conf
e aggiungiamo la riga:

LoadModule watch_module /usr/lib/apache/1.3/mod_watch.so

Poi editiamo /etc/apache/httpd.conf

<IfModule mod_watch.c>
# Allows the URL used to query virtual host data:
#
# http://www.snert.com/watch-info
#
<Location /watch-info>
SetHandler watch-info
Order allow,deny
Allow from hostname
</Location>


# Intended for debugging and analysis of shared memory
# hash table and weenie files:
#
# http://www.snert.com/watch-table
#

<Location /watch-table>
SetHandler watch-table
Order allow,deny
Allow from hostname
</Location>

<Location /watch-list>
SetHandler watch-list
Order allow,deny
Allow from hostname
</Location>


</IfModule>

Dove chiaramente hostname va sostituito con un host a vostra scelta (tipicamente localhost)

Stop & start apache (restart a volte non basta )

/etc/init.d/apache stop && /etc/init.d/apache start

Possiamo verificare da riga di comando che tutto funzioni

./mod_watch.pl -f ifRequests,ifDocuments http://www.freshnet.org/watch-list/
65236
11851
14:59.59
SERVER

Ora installiamo il plugin

cp mod_watch /usr/share/munin/plugins/
cd /etc/munin/plugins
ln -sf /usr/share/munin/plugins/apache_watch apache_watch_bytes
ln -sf /usr/share/munin/plugins/apache_watch apache_watch_documents
ln -sf /usr/share/munin/plugins/apache_watch apache_watch_requestes

Come ultima cosa riavviamo munin-node

/etc/init.d/munin-node restart

Il risultato finale ci mostrerà, ad esempio, le richieste divise per singolo virtualhost

March 8th, 2007 | 1 Comment

Bello avere degli amici ;)

[09:59:17] AndyCapp: secondo te ha senso andare ad InfoSecurity o meglio stare a casa a dipingere ?
[09:59:28] UserFormalyKnowAsSecurityGuru: acquarelli, acquarelli

Postfix, amavis, *bcc double email problem

In our main.cf we have an always_bcc=pippo line.
The behaviour we’re seeing is that when a user sends a mail to a user the recipient in bcc get two responses.
Same stuff with recipient_bcc_maps

What is happening is that the ‘always_bcc=pippo’ is running twice.
The ‘always_bcc’ is handled through Postfix’s cleanup service.
The cleanup service is running twice on the same email, once with Postfix before amavisd, and once
again after amavisd.
What you might want to do is remove the ‘always_bcc’ (and or ‘recipient_bcc_maps’) from the ‘main.cf’ and setup a seperate cleanup service specifically for the ‘always_bcc’ parameter (and/or recipient_bcc_map).
This cleanup service will be used for the second postfix smtp server.

For example:
cleanupAF unix n - n - 0 cleanup
-o always_bcc=pippo
-o recipient_bcc_maps=hash:/etc/postfix/recipient_bcc

127.0.0.1:10025 inet n - n - - smtpd (after filter
smtp server)
-o cleanup_service_name=cleanupAF

Now only the reinjection after the filter will use the *bbc options.

NB We have also tested this scenario on postfix+clamsmtp: it works

Driver ATI e Ubuntu Edgy

Se avete scaricato gli ultimi driver prorietari ATI per Linux la procedura di installazione vi dara questo errore

./ati-driver-installer-8.29.6.run –buildpkg Ubuntu/edgy
Creating directory fglrx-install
Verifying archive integrity… All good.
Uncompressing ATI Proprietary Linux Driver-8.29.6……………………………………….
-e ===============
-e ATI Technologies
Linux Driver Installer/Packager
-e ===============
./ati-installer.sh: 176: Syntax error: Bad substitution
Removing temporary directory: fglrx-install

La soluzione, semplice ma poco intuitiva

sudo ln -sf /bin/bash /bin/sh
./ati-driver-installer-8.29.6.run –buildpkg Ubuntu/edgy
sudo ln -sf /bin/dash  /bin/sh