Thursday, April 30, 2009

Mandriva Linux 2009 Spring released

Mandriva has announced the launch of the final version of Mandriva Linux 2009 Spring (codename Pauillac). This new version comes with a host of improvements and changes, as always. Fun fact: this is the first release reported to us by Anne Nicolas instead of Adam Williamson. For those that keep score.

The Mandriva Linux 2009 Spring comes in the flavour of your choice, KDE, GNOME or LXDE, in more than 70 languages. There's the Free edition (100% open source software) in 2 DVDs for 32 and 64 architecture and the One edition (installable live CD, available in KDE and GNOME versions). Major updates includes KDE 4.2.2, GNOME 2.26, Xorg server 1.6, Linux kernel 2.6.29, Xfce 4.6, Qt Creator 1, Tcl/Tk 8.6, syslinux 3.75, and much more.

Mandriva Linux 2009 Spring comes with an improvement in boot time. The tools of Mandriva Control Center have also been optimised. Network center now supports advanced network configuration together with additional pre-configured Internet providers, integration with new network devices and support for different wireless regulatory domains. msev, the Mandriva security framework, has been also redesigned.

The ext4 file system is now supported in the stable version and proposed during installation. Last update of syslinux comes with the HDT module (Hardware Detection Tool), which brings you a way to detect all your hardware before booting your system.

You can take the 2009 Spring tour, read the Release notes and Errata, and of course, download.

Source

Tuesday, April 28, 2009

Firefox 3.0.10 fixes critical vulnerability


The Mozilla developers have announced the release of version 3.0.10 of their open source Firefox web browser. The security and stability release addresses a critical security vulnerability introduced in Firefox 3.0.9.

The vulnerability is a regression which in some cases caused frequent crashes. Users running the HTML Validator add-on were particularly affected, although other users also experienced the crashes. The problem was due to memory corruption, similar to problems identified as security vulnerabilities in the past.

More details about the release can be found in the release notes. Firefox 3.0.10 is available to download, or Firefox users can use the Firefox update service by selecting Help, then Check For Updates.

Source

Saturday, April 25, 2009

Testing Red Alert 2 with wine

I had unsuccessful attempt to run (old) Red Alert 2 game with sound using wine 1.x.x. After ignoring to test it for a few months due to my busy work, yesterday I decided to try it again. It worked. My wine version is 1.1.17. My Red Alert 2 is Yuri's Revenge with no-cd patch. Below is how I set wine to make sound works. The graphics setting is just an additional setting to set virtual destop to make the game runs in a window (and not in full screen as default).

Audio Setting
Run winecfg to change audio setting for wine.


Click on the Audio tab. Make sure PulseAudio (recent wine support PulseAudio driver) and OSS driver checked and in DirectSound section make sure Hardware Acceleration is set to Emulation. And then click OK button to save the settings.

Graphics Settings
Click on Graphics tab and check Emulate a virtual desktop setting and set Desktop size to 800 x 600 or 1024 x 768.

Now it's ready to be run. See screenshots below.




Monday, April 13, 2009

postfix can't connect to MySQL

I got this error in syslog when postfix was trying to connect to MySQL:

Apr 13 17:34:53 webmail postfix/smtpd[6726]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
Apr 13 17:34:53 webmail postfix/smtpd[6726]: NOQUEUE: reject: RCPT from rv-out-0506.google.com[209.85.198.233]: 451 4.3.0 : Temporary lookup failure; from= to= proto=ESMTP helo=

I got a reference to MySQL database in my main.cf which triggered the error:

local_recipient_maps = mysql:/etc/postfix/sql-recipients.cf

From the error it was obvious postfix couldn't connect to MySQL. Email from outside wouldn't be received properly by dbmail. I checked MySQL service and it was running and I could log into MySQL manually. I found a solution after googling a bit. The cause was in file /etc/postfix/master.cf. I got smtp service of postfix to run chroot'ed (see y below).

#service type private unpriv chroot wakeup maxproc command + args
smtp inet n - y - - smtpd

So I changed the line to:

#service type private unpriv chroot wakeup maxproc command + args
smtp inet n - n - - smtpd


Voila!. It worked. See log below:

Apr 13 18:03:02 webmail postfix/smtpd[7039]: connect from rv-out-0506.google.com[209.85.198.239]
Apr 13 18:03:03 webmail sqlgrey: grey: domain awl match: updating 209.85.198(209.85.198.239), gmail.com
Apr 13 18:03:03 webmail postfix/smtpd[7039]: B3246A3075: client=rv-out-0506.google.com[209.85.198.239]
Apr 13 18:03:04 webmail postfix/cleanup[7042]: B3246A3075: message-id=<23c8d5620904130314j7f4c619di57c7d8c0d217ed62@mail.gmail.com>
Apr 13 18:03:04 webmail postfix/qmgr[7033]: B3246A3075: from=, size=2277, nrcpt=1 (queue active)
Apr 13 18:03:05 webmail postfix/smtpd[7046]: connect from webmail.myfakedomain.net[127.0.0.1]
Apr 13 18:03:05 webmail postfix/smtpd[7046]: 26BBFA3076: client=rv-out-0506.google.com[209.85.198.239]
Apr 13 18:03:05 webmail postfix/cleanup[7042]: 26BBFA3076: message-id=<23c8d5620904130314j7f4c619di57c7d8c0d217ed62@mail.gmail.com>
Apr 13 18:03:05 webmail postfix/qmgr[7033]: 26BBFA3076: from=, size=2751, nrcpt=1 (queue active)
Apr 13 18:03:05 webmail postfix/smtpd[7046]: disconnect from webmail.myfakedomain.net[127.0.0.1]
Apr 13 18:03:05 webmail dbmail/lmtpd[20480]: Message:[serverchild] serverchild.c,PerformChildTask(+349): incoming connection from [127.0.0.1] by pid [20480]
Apr 13 18:03:05 webmail postfix/lmtp[7043]: B3246A3075: to=, relay=127.0.0.1[127.0.0.1]:10025, delay=2, delays=0.96/0.01/0/1, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=01032-05, from MTA([127.0.0.1]:10026): 250 2.0.0 Ok: queued as 26BBFA3076)
Apr 13 18:03:05 webmail postfix/qmgr[7033]: B3246A3075: removed

Wednesday, April 8, 2009

CUPS: Unable to open device and permission denied

I use CUPS for my printer system and I got this error:

Unable
to open device "
hal:///org/freedesktop/Hal/devices/usb_device_3f0_217_00SGKGB09615_if0_printer_noserial": Permission denied

How to solve this problem? The settings of the printer was correct and was just a permission problem. Googling a bit, I found this site.

These steps what I did to solve it:
1. cd /usr/lib/cups/backend
2. chmod 700 hal (previously 755)
3. chmod 700 usb (previously 755)

For step 2 and 3, I found out that you have to change the mod to 700 although the file hal and usb has 'rwx' on them on the 'user' part. The culprit was the 'group' and the 'other' part of the permission. They should be chmod'ed to 0. On my system, the 'group' and 'other' part of both files was 5 (r-x) previously.

I hope this saves some people's time of head scratching.

Wednesday, April 1, 2009

clamav detects conficker

Taken from http://www.clamav.net/2009/01/29/conficker-aka-downadup/

Some of you may have heard of a current major outbreak of a virus known as Downadup that has been reported at http://news.bbc.co.uk/1/hi/technology/7842013.stm and http://news.bbc.co.uk/1/hi/technology/7832652.stm. It has been estimated that move than 9 million PCs are infected across the world.

ClamAV detects Downadup, also known as Conficker, as Worm.Downadup. Once on a system it downloads components that ClamAV detects as members of the Trojan.Downloader- family of signatures.

The virus primarily exploits MS08-067; it can also spread through USB sticks. Since the virus is not spread by email we don’t expect to see much activity in our core user-base, which tends to use ClamAV to scan emails. We are, nevertheless, keeping an eye out for it through freshclam’s statistics gathering system – we are yet to see any obvious spike of activity from it. If we hear anything we’ll let you know.


Renew letsencrypt ssl certificate for zimbra 8.8.15

 Letsencrypt certs usually consists of these files: 1. cert.pem 2. chain.pem 3. fullchain.pem 4. privkey.pem I am not going to discuss about...