lix blog

While Apple Computers decided to violate users rights once more, ceasing the capability to synchronise PIM (personal information management) data locally with OS X Mavericks 10.9 (argueing they should store their data in their iCloud. – Bwahahahaha!1!!) there are too many PIM solutions for GNU/Linux users, whereas none of them are really feasible for users who want to switch to Free Software.

While many complain that there are too few GNU/Linux Desktop users and Linus Torvalds claims this to be his “personal failure” the GNU/Linux community fails to offer a seamless integration of GUI (graphical user interface) PIM into their OS. (Which is really sad, as fiddling around with SoGo-connector, lightning etc. does not offer a sustainable solution…)

So here is my solution:
Get DAViCal, install it on your server and get mutt, pycarddav and khal for your desktop(s), get a Jolla and you will have a beautiful and seamless PIM solution using the “good olde command line”.

Debian 7.0 “Wheezy” has just been released. \o/

After many months of constant development, the Debian project is proud to present its new stable version 7.0 (code name Wheezy).

This new version of Debian includes various interesting features such as multiarch support, several specific tools to deploy private clouds, an improved installer, and a complete set of multimedia codecs and front-ends which remove the need for third-party repositories.

– ————————————————————————-
Debian Security Advisory DSA-2670-1 security@debian.org
http://www.debian.org/security/ Yves-Alexis Perez
May 11, 2012 http://www.debian.org/security/faq
– ————————————————————————-

Package : wordpress
Vulnerability : several
Problem type : remote
Debian-specific: no
CVE ID : CVE-2011-3122 CVE-2011-3125 CVE-2011-3126 CVE-2011-3127
CVE-2011-3128 CVE-2011-3129 CVE-2011-3130 CVE-2011-4956
CVE-2011-4957 CVE-2012-2399 CVE-2012-2400 CVE-2012-2401
CVE-2012-2402 CVE-2012-2403 CVE-2012-2404
Debian Bug : 670124

Several vulnerabilities were identified in WordPress, a web blogging
tool. As the CVEs were allocated from releases announcements and
specific fixes are usually not identified, it has been decided to
upgrade the WordPress package to the latest upstream version instead
of backporting the patches.

This means extra care should be taken when upgrading, especially when
using third-party plugins or themes, since compatibility may have been
impacted along the way. We recommend that users check their install
before doing the upgrade.

For the stable distribution (squeeze), those problems have been fixed in
version 3.3.2+dfsg-1~squeeze1.

For the testing distribution (wheezy) and the unstable distribution
(sid), those problems have been fixed in version 3.3.2+dfsg-1.

We recommend that you upgrade your wordpress packages.

Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: http://www.debian.org/security/

Mailing list: debian-security-announce@lists.debian.org

Source

… any suggestions?

Here’s a simple script to install on a server to keep the GeoIP db updated.

Source code for file (e.g.) get_latest_GeoIP.sh

#!/bin/bash
# getting the latest GeoLiteCity database from maxmind
host=$(hostname -s)
stamp=`date +"%m%Y"` # getting current month & year for GeoLiteCity filename
if [ -f "/usr/share/GeoIP/GeoLiteCity_"$stamp".dat" ]; then
  last=`date -r /usr/share/GeoIP/GeoLiteCity_"$stamp".dat +"%m%Y"`
else
  last=0000
fi
if [ ! -f "/usr/share/GeoIP/GeoLiteCity_"$stamp".dat" ] || [ "$stamp" != "$last" ]; then # if current file doesn't exist or current file wasn't modified in the current month
  wget -O "/usr/share/GeoIP/GeoLiteCity.dat.gz" http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz
  if [ ! -s "/usr/share/GeoIP/GeoLiteCity.dat.gz" ]; then
    rm /usr/share/GeoIP/GeoLiteCity.dat.gz
    exit 1
  else
    rm /usr/share/GeoIP/GeoLiteCity.dat
    gunzip /usr/share/GeoIP/GeoLiteCity.dat.gz
    if [ -f "/usr/share/GeoIP/GeoLiteCity_"$stamp".dat" ]; then
      rm /usr/share/GeoIP/GeoLiteCity_"$stamp".dat
    fi
      mv /usr/share/GeoIP/GeoLiteCity.dat "/usr/share/GeoIP/GeoLiteCity_"$stamp".dat"
      ln -s "/usr/share/GeoIP/GeoLiteCity_"$stamp".dat" /usr/share/GeoIP/GeoLiteCity.dat
      echo "Report: GeoIP Database "$stamp" has been updated on "$host". - Enjoy!"
  fi
fi
exit

… now just install a cronjob, that checks withn the first days of the month, whether there is a fresh GeoIP db to fetch.

22 3 1-10 * * ~/get_latest_GeoIP.sh > /dev/null 2>&1

On my Nagios Server I use twitter to send status alerts. It works nicely with Identica & Twitter.

The setup is easy. First install twidge with

root@host:~# apt-get install twidge

Then write a twidgerc file with the according twidge configuration

nagios@host:~# vi /etc/nagios3/twidgerc
[DEFAULT]
oauthaccesstoken: %(serverbase)s/oauth/access_token
oauthauthorize: %(serverbase)s/oauth/authorize
oauthdata: [("user_id","XXXXXX"),("screen_name","YOUR_SCREENNAME"),("oauth_verifier","XXXXXX"),("oauth_token","XXXXXX"),("oauth_token_secret","XXXXXX"),("oauth_callback_confirmed","true")]
oauthrequesttoken: %(serverbase)s/oauth/request_token
sendmail: /usr/sbin/sendmail
serverbase: https://api.twitter.com
shortenurls: yes
urlbase: %(serverbase)s/1

Make sure the file is readable by Nagios user. (!)

nagios@host:~# chown nagios /etc/nagios/twidgerc

Then add the following lines to /etc/nagios3/conf.d/contacts_nagios2.cfg (on GNU/Linux Debian).

define contact{
contact_name twitter
alias Twitter
service_notification_period 24x7
host_notification_period 24x7
service_notification_options w,u,c,r
host_notification_options d,r
service_notification_commands notify-service-by-twitter
host_notification_commands notify-host-by-twitter
email twitteraccount_to_contact
}

… and add “twitter” to the members in the contactgroup (in the same file).

members root,nagiosadmin,twitter

Then add these lines to etc/nagios3/commands.cfg:

define command {
command_name notify-service-by-twitter
command_line echo "#Nagios $NOTIFICATIONTYPE$ $HOSTNAME$($SERVICEDESC$) is $SERVICESTATE$" | twidge -c /etc/nagios3/twidgerc update
}
define command {
command_name notify-host-by-twitter
command_line echo "#Nagios $HOSTSTATE$ alert for $HOSTNAME$" | twidge -c /etc/nagios3/twidgerc dmsend $CONTACTEMAIL$
}

Nagios will tweet the service notifications and send a directmessage to the according user with the host notification.
Here’s an example:

=^.^= Lx