Friday, July 27, 2007

Security Update : BIND

Slackware security team has released an update to BIND package to fix security vulnerability that affect several version of BIND. In this release, Pat and his team release an update for Slackware 8.1 and above (until 12.0). What an effort to support Slackware 8.1 up to now not worthy

Here's the changelog for the stable tree:

Thu Jul 26 15:51:42 CDT 2007
patches/packages/bind-9.4.1_P1-i486-1_slack12.0.tgz:
Upgraded to bind-9.4.1_P1 to fix security issues.
The default access control lists allow remote attackers to make recursive queries in BIND9 versions 9.4.0 through 9.4.1.
The query IDs in BIND9 prior to BIND 9.4.1-P1 are cryptographically weak.
For more information on these issues, see:
http://www.isc.org/index.pl?/sw/bind/bind-security.php
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2925
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2926
(* Security fix *)

Wednesday, July 25, 2007

More Security Updates

After Firefox, now Thunderbird and Seamonkey who gets an update. Mostly the fixes are the same as the Firefox as they shared most of their engine together. It appears that Pat has already fix the broken link on the Stable Changelog. Now it has already pointed to the correct file big grin so if you miss some updates in July 19, grab them now.

One note about the release note of the Thunderbird and Seamonkey updates is that the URL is not working, as they use capital naming on the anchor name. And it seems that the link will be cut when this blog is published, so please have a look on the original URL:
http://www.mozilla.org/projects/security/known-vulnerabilities.html

Tue Jul 24 12:40:16 CDT 2007
patches/packages/mozilla-thunderbird-2.0.0.5-i686-1.tgz:
Upgraded to thunderbird-2.0.0.5. Since Thunderbird shares the browser engine with Firefox it is susceptible to similar vulnerabilities. This update fixes the same issues fixed in the recent Firefox patch.
For more information, see:
http://www.mozilla.org/projects/security/known-vulnerabilities.html#thunderbird
(* Security fix *)

patches/packages/seamonkey-1.1.3-i486-1_slack12.tgz:
Upgraded to seamonkey-1.1.3. This is presumably a security update, but the details on the net have been sparse. So far nothing has appeared at the usual URL, but I would treat this as a security update unless it is announced as otherwise.
For more information (if/when it appears), see:
http://www.mozilla.org/projects/security/known-vulnerabilities.html#seamonkey
(* Security fix *)

Saturday, July 21, 2007

Coming Soon : Aggregator

A discussion in id-slackware mailing list was talking about a possibility to have a blog aggregator, using some kind of applications which can grab RSS/XML feed from other blog and save it on the database and then displays them on single page. Examples are Planet OpenSuSE Indonesia or Planet Ubuntu Indonesia. We are planning to have Planet Slackware Indonesia. We have several options here:
- Using slackware.linux.or.id as the main domain or
- Use new domain

Some people have been willing to donate for the domain and hosting, but i still prefer that we use what's already available and reduce redundancy. So, what do you think? Should we have http://slackware.linux.or.id/planet or should we buy a new domain, like http://planet.slackware-id.org or http://planet.slackware.or.id?

Other options is the application that we will use. We could have used PlanetPlanet or we could use a CMS and then installs a plugin which can works as an aggregator. WordPress and many other CMS have support them and all you have to do is just download and install the plugins.

We are still discussing it, so please be patients for now big grin

Saturday, July 14, 2007

Indonesian Slackware Mailing List

Yesterday, i created a new Indonesian Slackware Mailing list called id-slackware using GoogleGroups. There has been a same account in YahooGroups, but it's not quite effective and sometimes there are spams in it, so in order to have better discussion about Slackware, i decided to create a new mailing list and here you are. It's intended for Indonesian people, since the language that we use will be Indonesian, but we do not restrict the membership to Indonesian people only. If you wish to join the list, please feel free to do so.

With better management, i hope the discussion in this mailing list can help many Slackware users in Indonesia. The number of members is increasing every day, so join us also big hug

Monday, July 9, 2007

Everything Back to Normal

So after i download the latest kernel, 2.6.22, i compiled it on my new Slackware on my desktop and after i reboot, everything works normal again (my sound card and ethernet are detected again). This is a great step and i'm starting to configure my desktop to have the configuration as my laptop does, so i'm installing applications that i will need in the present and future. I start with the most common application, such as Firefox, OpenOffice.org, Adobe Acrobat, Mplayer (Thanks to Alien's package) and also doing some cosmetics (changing the icons, adding new splash screen, modifying shortcuts in KDE, etc). I know this is not a one day activities, so i think i should stop now or i won't be sleeping since playing with Linux, mostly Slackware (for me) is a very interesting activities heheh

Kernel 2.6.22 Released

Finally, i have been waiting for this release since i want to compile a vanilla kernel from source for my Slackware. I have some problem with the huge kernels included in the default installation since it cannot detect my soundcard and ethernet card. Probably changing to generic will solve it, but as i already used to compile kernels, it would be better if i try out the latest kernel also (fresh from the oven).

What i don't understand is this text from Linus:
Woo-hoo. I'm sure somebody will report a "this doesn't compile, and I have a new root exploit" five minutes after release, but it still feels good ;)
i'm pretty sure that Linus wouldn't release a buggy kernel as it's being used by lots of people around the world big grin

Friday, July 6, 2007

Installing Slackware 12.0 On My Desktop

Today i decided to try a fresh installation of Slackware 12.0 on my desktop. I have prepared an empty partition (10 GB) for this new installation since i brought a new HD for my desktop. The installation was quick, even though i choose most of the packages (i used expert menu for the installation which let me choose which packages i wanted to install manually).

After the installation was finished, i rebooted and this is when the nightmare comes. I had a kernel panic!!! I remember that i used the generic kernels which requires an initrd, but i don't think the installation has made it for me, so that's the reason. I tried to boot using the CD and mount the root partition and use chroot to change the root directory to make an initrd and i was success. But the problem didn't end there. I still had the kernel panic, so finally i decided to use huge kernel and it worked. It loads my system and i'm able to create a regular users.

Next, i tried to start the KDE and it worked, but my mouse didn't work, so i tried to setup the mouse, but failed. So i changed my mouse to USB (actually it's a USB mouse, but since there's an adapter which convert it to PS/2, i used it, but i guess this is the reason why it didn't work out, so i unplug it) and it worked big grin

So far, the main system has worked perfectly, but there are still some problems i had:
- Sound card is not detected, so my computer is mute for now
- Ethernet card is not detected, so i couldn't get online for now
- Kernel is not tunable (this is my personal problem, not related to Slackware)

Well, there are still a lot of homeworks to be done in the next few days, but for the beginning, it's quite OK, even though i have to deal with kernel panic (something i never had in the last two years) hehehehe

My suggestion for those who want to install Slackware 12.0: Use Huge kernels as it would make your life easier at the beginning. It's bloated (i know), but it's only for the start. When your system has been running well, try to tune the kernel to get better performance and remove unneeded modules.

Wednesday, July 4, 2007

Downloading Slackware 12.0 ISOs

Since last night (up to now), my computer is busy downloading Slackware 12.0 ISOs from GDS mirror. I have finished two of them (i only download the install disc) and in less than 15 minutes, i will have my third disc and i'm done downloading the ISOs and probably i should give my computer a little break after burning them into CD. I'm planning to install Slackware 12.0 on my desktop so i can see a fresh Slackware 12.0 installation, since my laptop already use Slackware-Current since two years ago and i never reinstall it.

Hopefully Ozzie will download the ISO as well into Indonesian Mirror and people will have faster access to the ISO rather than downloading from mirrors outside Indonesia.

Update (15:16): Download process is complete and now, i'm burning it to CD big grin

Tuesday, July 3, 2007

Slackware 12.0 Released

After nine months of full development, finally Slackware 12.0 is finally released by Patrick Volkerding. For those who have used Slackware before, then you might notice big changes in this release, such as fully kernel 2.6(.21.5) support, updated toolchain, enabled HAL on XFCE and KDE which enables users to have auto mounting features out-of-the-box of Slackware installation. This will make Slackware as a easy to use Linux distro for desktop users. Another big changes is the use of new Xorg 7.2.0 (Modular), Usage of GNU C Library 2.5, support for fully encrypted network connections with OpenSSL, OpenSSH, OpenVPN, and GnuPG, Apache 2 support, udev usage instead of hotplug for 2.6 kernels, updated development packages, such as Ruby, Python, PHP, Perl, SVN, CVS, Git, Mercurial, and many more. The list is more than what i wrote on this blog. For more detailed, please have a look on the official announcements. You might want to see what's in Slackware 12.0 by looking at the FILE LIST.

Upgrading for 11.0 is also very easily done by the use of updated pkgtool (and also looking at the CHANGES_AND_HINTS.TXT file), but it's strongly suggested that you do fresh installation, since huge changes there. Some people i knew tried to upgrade to -Current (now it's officially 12.0) and they had a disaster and end up with messed up system. Just do upgrades if you are used with Slackware before and willing to take the risk.

That's all for now, i'm downloading them......

Sunday, July 1, 2007

No TarBall?

I was looking for Linux version of Google Desktop and when i browsed their site, i couldn't find any package that can be installed on Slackware. They only provide with RPM and DEB files, which is mainly used by Fedora, SuSE, Mandriva, and Debian/Ubuntu. I wish they provide a .bin (like in the Picasa) or probably the tarball. Perhaps the solution for now is waiting for someone in LinuxPackages to upload the packages or try to convert it using rpm2tgz, which i doubt will work in this case (i have used this utility to convert OOo and Opera and both of them worked well, but i haven't tried that in Google Desktop). Any experience of converting Google Desktop's RPM to TGZ?? If you do, please let me know big grin

Testing NTOP

After following a workshop few weeks ago with Onno W. Purbo, i wanted to try to install several applications, including NTOP, MRTG, Snort, and some more. Today, i managed to install one of them, NTOP. The installation was quick enough, since i got a simple instructions from Internet.

To install NTOP, you will need several other application as the dependencies:
- RRDTool
- Libpcap
- graphiz (optional)
- swig (optional)

Of course you will need to install the development packages, such as GCC, Automake, and Autoconf (there are probably more but i only list three of them to make this post short). Because you will need a library that could make an output of an image, you probably want to install libpng and libjpeg also.

First of all, install the dependency packages: rrdtool, libpcap, and graphiz. I don't install graphiz, because i got an error message when i run make, so i skipped graphiz, but it's still working since it's not a mandatory package, but i will miss a great display that graphiz is good at.

Next is the installation of the main program, NTOP. Since i build it from source, i just type the usual command, except for the first time, i had to run autogen.sh. I got an error which the configure program couldn't find the rrdtool home, so i had to run ./configure with a new parameter --with-rrdtool-home=/usr/local/rrdtool-1.2.23 and it worked. That's all. NTOP is now installed and you can test it using this command:
/usr/local/bin/ntop -i eth0 -d -w 3000

This will start ntop as a daemon and runs at port 3000 on your web server (somebody told me that NTOP has it's own web server, so you don't need Apache for this, but it's still recommended to install Apache if you want a fully working web server). From this on, you can monitor your client's usage and where do they browse everyday. Since i installed this on my laptop, i wouldn't get much advantage, but at least i know how to install NTOP on Slackware. Just in case i will be working as SysAdmin in the future (please note that i'm still having fun with my current job) cool