42196 items (42195 unread) in 81 feeds
FLOSSIndia
(18455 unread)
FLOSSSouthAsia
(8161 unread)
FLOSSAsia
(10754 unread)
Miscellaneous
(4825 unread)
possible SYN flooding on port 84. Sending cookies.
possible SYN flooding on port 82. Sending cookies.
possible SYN flooding on port 81. Sending cookies.

Negaraku Digg Style
Negaraku the local news aggregator I posted about some time back has gone through it’s evolution cycle and now emerged as a Digg clone.
Cloning other application is always a bad idea but in my book if you are able to provide something the competition doesn’t then the idea will work. In the case of Negaraku, the information is localized to Malaysia. Even Google sees localized data as one of it biggest hurdle.
The original aggregator was slow buggy thus the need to evolve. The new Digg styled site is way better the the original. The site appears to be faster when compared to the original aggregator. The layout is simple, uncluttered and colors easy on the eyes.
Submissions are still broken up into their own categories like politics, business,tech, politics and a few others. This helps users easily access their information of choice. Each category is also publish via RSS for easy access. Another benefit of going Digg style is that high rated submissions always show up first rescuing users from wasting their time combing though useless submissions.

Negaraku old aggregator
So what happen to the old aggregator? It’s still alive at news.negaraku.net .
In short I like Negaraku Digg Style. What do you think?
Source: Negaraku || news.negaraku.net
Tags: blog, Blogs, Malaysia, malaysian news, news, politicians, rss, rss aggregator

syslog is a standard for logging service in Linux, it usually run as daemon like syslogd or rsyslogd. Syslog daemon will be forward and store logs in /var/log directory, you may configure it to store at separate location if you want. (we will look into it later). And there is a major file that store majority of logs, which is messages. Therefore, you may want to monitor linux messages logs by tailing /var/log/message.
Logs entry may come from various services, applications, kernel as well as remote servers if you enabled your syslog daemon to accept remote logs submissions. Syslog protocol is now standardized within the Syslog working group of the IETF, and it is been defines in RFC 3164.
Rsyslog is an enhanced multi-threaded syslogd with a focus on security and reliability. I think newer linux distro already replace syslogd with rsyslogd. For more information you can check out the wikipedia.
In this post, I briefly explain the facility and log levels of syslog protocol, how to configure syslogd as well as rsyslogd to accept logs from remote and also how to send logs remotely.
Syslog categories logs into PRI which constructed by facility and severity/priority/log levels.
Facility defines the source of the log entries, what kind of services that send this logs. Lets look at Facility info that extracted from RFC 3164, each facility was been assign a numeric code.
Numerical Facility
Code
0 kernel messages
1 user-level messages
2 mail system
3 system daemons
4 security/authorization messages
5 messages generated internally by syslogd
6 line printer subsystem
7 network news subsystem
8 UUCP subsystem
9 clock daemon
10 security/authorization messages
11 FTP daemon
12 NTP subsystem
13 log audit
14 log alert
15 clock daemon
16 local use 0 (local0)
17 local use 1 (local1)
18 local use 2 (local2)
19 local use 3 (local3)
20 local use 4 (local4)
21 local use 5 (local5)
22 local use 6 (local6)
23 local use 7 (local7)
Severity is the log levels that defines how critical of the log entries, from 0 - 7, 0 indicates the most critical and 7 is for debugging purpose.
Numerical Severity
Code
0 Emergency: system is unusable
1 Alert: action must be taken immediately
2 Critical: critical conditions
3 Error: error conditions
4 Warning: warning conditions
5 Notice: normal but significant condition
6 Informational: informational messages
7 Debug: debug-level messages
PRI is a unique values constructed by facility and severity where severity takes 3 LSB (least significant bits) append with facility start from bit 4.
PRI = (facility << 3) + severity
<< indicates left shift which I borrow it from c++ programming language, when I do left shift N its like multiply with 2^N(two to the power of N). In this context, PRI formula can be written as
PRI = (facility * 2^3) + severity
PRI is important when you wanna send message to syslog, the default message PRI is user(1).notice(5) which the PRI value is 8 + 5 = 13. Meaning if you do not specified the PRI value, it will be treated as 13.
For common Linux distro, syslogd or rsyslogd should be started before you login to your system, you can verify that with ps.
ps aux| grep syslogd
Usually syslogd comes with distro does not configured to accept remote messages, unless -r is specified.
root 4232 0.0 0.0 13424 888 ? Sl Jul22 0:00 syslogd -m 0 -r
How to enable syslogd to accept remote message?
syslog will listening to UDP port 514 for messages sent remotely, but if your distro running rsyslogd, you can listen to TCP port and you may also need to specify the port number.
Different Linux distro may have different ways of configuration, let say if you are using Red hat based distro, your syslogd and rsyslogd configuration will be at /etc/sysconfig/syslog or /etc/sysconfig/rsyslog.
For the case of rsyslogd, change the SYSLOGD_OPTIONS in /etc/sysconfig/rsyslog from SYSLOGD_OPTIONS=”-m 0″ to SYSLOGD_OPTIONS=”-m 0 -r514″ for UDP and SYSLOGD_OPTIONS=”-m 0 -t514″ for TCP. For the case of syslogd, change it to SYSLOGD_OPTIONS=”-m 0 -r”.
After that, restart your syslog or rsyslog services, In Fedora or Red Hat, you may do this with root permission.
service syslog restart
Or you can just kill the syslogd process and start manually from console for testing.
rsyslogd -m 0 -r514
Syslog Configurations
syslog daemon includes a configuration files to specified which logs to keep and append it to which file based on the PRI stated above.
Below are the sample of /etc/rsyslog.conf
# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;authpriv.none;cron.none /var/log/messages
# The authpriv file has restricted access.
authpriv.* /var/log/secure
# Log all the mail messages in one place.
mail.* /var/log/maillog
# Log cron stuff
cron.* /var/log/cron
You defines what messages goes to what file like this:
facility.severity log_files
For example:
user.notice /var/log/user.notice
The line above indicates that, when I get syslog message with facility user and severity notice, it will be append to file /var/log/user.notice.
For more info, please check out here.
How to send message to syslogd?
For sending locally, we can use the logger command. Before you send the message to syslog, lets tail the message log.
tail -f /var/log/messages
Now send “hello world” with logger.
logger "hello world"
It will appear in /var/log/messages as well as /var/log/user.notice if you have configure syslog.conf to forward user.notice messages to /var/log/user.notice. This proves that the default message’s PRI is user.notice. You may assign different PRI value to logger. For example if I wanna send message with PRI = user.info:
logger -p user.info "testing 123"
How to send log message to remote server?
Unfortunately, you can’t send through logger. But you can manually send a plain text UDP package to remote servers that listening on UDP port 514. With the help of netcat(nc), we can send the message to remote syslogd as simple as logger command.
nc -w0 -u 192.168.1.1 514 <<< "logging from remote"
To assign your message a PRI, you need to specified PRI’s value in numeric.
User.Info’s PRI value is:
(1 3 ) + 6 = 8 + 6 = 14. ( refers back the numerical code of facility and severity )
nc -w0 -u 192.168.1.1 514 <<< "<14>User Info msg from remote"
If your rsyslogd are listening to TCP port, just ignore -w0 and -u:
nc 192.168.1.1 514 <<< "<14>User Info msg from remote through TCP."
Related Posts
Answer this question;
1. Do you have more than one email services account? Example: yahoo, gmail, hotmail and etc.
2. Do you have more than one online banking account? Example: maybank2u.com, alliance online
3. Do you share the same password for all the accounts?
If your answer is yes, please continue reading…
Recently security.org.my posted that one of the .gov website is disclose their database file openly to public. If you are using the same password for all your account. Then I would advise you to update/change your password immediately. It’s not that you do not know to secure your password. But then, at times, careless administrator might accidentally publish your “password” online, and attack can follow by your email address to compromise your system.
So, that is a good example to learn from. Act now, or regret later.

iPhone 3G
This might be old news but ya, Maxis is bringing in the iPhone 3G.
When? Not too sure, hopefully in the next months. How much? This is not confirmed but Maxis is planning to push the iPhone 3G for under RM1000. Most likely for RM999.99.
This is good news for all those who wanted an iPhone but never found the right channels to get one. Now everyone’s on the same playing field. However, current iPhone owners might be slightly pissed since they might loose their mobile uniqueness
Maxis stands to benifit from this big time, I’m quite sure many are going to switch over to Maxis just for the iPhone. Celcom and Dgi will follow but when is the question.
Source: TheEdgeDaily || Delirium
Tags: 3G, apple, iphone, Malaysia, maxis, mobile phones
Update is splitted in two part because of a kernel update to accomodate free space limitation.
1.4.19 contain some packages updates, most notabily a dnsmasq update to be immune on recent dns advisory.
1.4.20 install the second part of the kernel update and configure the new kernel.
1.4.19 could be installed separately from 1.4.20. A reboot is not needed after 1.4.19 installation.
Concerning the dns issue, see more details in
http://www.heise-online.co.uk/news/DNS-security-problem-details-released–/111145
It is very likely anyone need to a patch without waiting and our is in 1.4.19 for
dnsmasq.
The dns server you use need to be patched too or you may switch to opendns.
You need to reboot to use the new kernel after 1.4.20 installation.
| The new kernel contain : - a new security protection against against null pointer dereference ( mmap_min_addr=4096) - some new nic drivers skge sky2 sc92031 atl1 atl2 - improved support in some IDE or sata driver Please report success/failure for nic and disk controllers detection. Silan sc92031 driver should recognize RslTek 8139D card. It’s a patch I have made and I need to know if everything is right. Original driver has some bugs I try to fix. |
As usual, this version can be installed as an update from previous v1.4.x versions or with a ready-to-go ISO or usb bootable images for a fresh install.
ipcop-avmdrv-2.4.36-1.i386.tgz.gpg is needed to install for avm drivers users.
The date on the machine where the update is installed has to be good.
If date is in the past, signature is considered in the futur and update will refuse to install.
You would have only the ‘This is not an authorized update’ message warning on web interface.
Gilles

Upgrade openssh to 4.7p1
Include lzo binary so, it will match openssl version if openssl is updated
Update dnsmasq to 2.45
Update tzdata to 2008d
Update pcre from 7.4 to 7.7
Update apache to 1.3.41
Upgrade e1000 to 7.6.15.5 solve issue with 7.6.12
Update bzip2 from 1.0.3 to 1.0.5 CVE-2008-1372
Upgrade e2fsprogs from 1.35 to 1.40.11
Update squid to 2.6.STABLE21
Compile r1000 with jumbo frame support
Upgrade bin package to 9.4.2-P1
sysctl.conf
- insert mmap_min_addr=4096 to protect again null pointer on new kernel
does not hurt on lower kernel than 2.4.36
rc.halt
- no need to source rc.flash.down
- save random seed on halt and use that value at start in rc.sysinit
rc.network
- no need to source rc.netaddress.up
rc.updatered
- use readhash to read dhcpcd info file
rc.sysinit
- include fcron -s 86400 for flash
snort
- modify snort.conf to protect against CVE-2008-1804
updfstab
- remove kudzu keyword from /etc/fstab so mount -t ext2 /dev/floppy /mnt/floppy work
log.dat
Fix system log section on update
ddns.cgi
- fix for SF Bug 1728880 - comma in password
- changes for regfish, closes #1950435
time.cgi
- update default time servers to include IPCops vendor name.
update.cgi
- Use cleanhtml to fully display gpg signature.
- The new kernel (with same settings) is automaticly selected during update.
- add a protection in update script against installing binary update package from another arch.
That would broke any binaries
Various
- add an help message for dummies attempting to compile directly inside IPCop
- add a script to set grub default booting kernel
- modify detection for Opera 9.50
Compilation
- Automaticly set vdso_enabled=0 when needed to be able to compile our glibc-3.3 on kernel running after 2.6.17
- uClic : More recent mke2fs use strod and we need to activate UCLIBC_HAS_FLOATS for that
- Allow toolchain compilation when AS_NEEDED is present inside /usr/lib/libc.so (binutils patch).
- Enable previously available nic drivers happymeal sungem
- Add new nic drivers skge sky2 sc92031 atl1 atl2
- Patch for improved amd74xx support NForce IDE (MCP51, MCP61, MCP65, MCP67, MCP73, MCP77) AMD CS5536
- Patch for improved ahci support sata Intel ICH7-M, ICH8, ICH8M, ICH9/ICH9R, ICH9M, ICH10, Tolapay, VIA MP67, MP73, MP79, MP7B, SiS 966, 968, Marvel 6145
- Fix file reload on md5 change
- Fix unzip CVE-2008-0888
- Add machine to the iso label and publisher
- Add german install pdf to iso
- Remove no more used CC=KGCC since we drop gcc-2.95.3
- Fix a bug in lfs/bash that replace building machine original /bin/sh when building toolchain
This has replaced Ubuntu original link to dash, Ubuntu users could recreate the link to dash manually if needed.
- Force SHELL to bash during toolchain because some of our script need that
(brace expansion) on glibc, bzip2 and Ubuntu default link to /bin/sh is dash
- Force SHELL=/bin/sh in lfs/gcc or it fail to build
- Add a comment that syslinux-3.70 and later can’t be compiled because of our binutil,
but we still could used precompiled version
- ppc port have been introduced. It does compile but a few work is still needed.
parted fail to partition the disk actually.
1.4.20 has been tested to compile (including toolchain compilation) with 32b
distrib on Debian etch, Ubuntu-8.04, Centos-5.1/5.2,Fedora-9 without any changes.
On 64b distrib, you need to open a linux32 console and load precompiled
toolchain get with ./make.sh gettoolchain
Installer
- not needed to link installer against libpci
- need a link from /proc/mounts to /etc/mtab for more recent e2fsprogs version
- separate package for disk partitioning utility to spare space on network and scsi floppies for added drivers
- badblock is available on install (but not yet used)
- Avoid modules.conf is more recent…, if you install now from old version and update to 1.4.20
If you could relive yesterday, how would you live it? What will you do? What will you avoid?
Most of us will try to do more and be better if we could relive yesterday. We desire to accomplish more. Like we saw last month, you can be more productive by creating good habits and rejecting bad ones. But then, with all the right intentions, why do we keep practicing bad habits? What’s the bottleneck in achieving what we desire?
The problem is that we do not do what we said we would do. You can become what you want, if you do what you said you would do. We must continually review ourselves and stay in action. Keep practicing the good habits and keep rejecting the bad ones. This persistence will pay off!
But there is another fundamental question we got to ask ourselves. The question is: “Do I want to be great? Really?” Read further if your answer is “Yes!”
There is some good news! You can become great. All great people started like you and me. They had some traits that made them great.
Richard St. John, a millionaire marketer was puzzled when a small girl asked him, “What really leads to success?” Even though he achieved success, he couldn’t tell her how he did it. To answer her question he spent 10 years interviewing over 500 successful people, including Martha Stewart, Richard Branson, Russell Crowe, and the Google founders. After analyzing all the data, Richard discovered the 8-Traits that lead to great success. What he found surprised me with its simplicity! And I had no doubt that following those 8 traits will make anyone successful.
I want to share those 8 traits to become great with you. The picture below depicts the 8 traits. Clicking on the picture will take you to a video Richard made to explain the concepts. The video is wonderful and I strongly recommend watching it, and sharing it with everyone on your team.

8 Traits To Be Great
You can also find a nice summary of these ideas on Richard St. John’s site.
addthis_url = 'http%3A%2F%2Fwww.mehtanirav.com%2F2008%2F07%2F23%2F8-traits-to-be-great'; addthis_title = '8+Traits+To+Be+Great'; addthis_pub = '';
At OSCON, Brian and Dormando gave their ever famous talk, Memcached and MySQL: Everything You Need To Know. I didn’t attend the tutorial, but they assured me it was similar to what was given at the MySQL Conference 2008 (everything, but the very nice buttons dormando was giving out with the memcached logo!). Great, because not only is memcached hot, but I have notes from their talk: Memcached and MySQL tutorial.
Interestingly enough (and this didn’t happen at OSCON), was at the MySQL Conference, Patrick Galbraith jumped on stage to speak about his experience with memcached at Grazr. Why not now, spend an hour listening to Patrick talk about Grazr, memcached, and MySQL?
There’s a webminar, titled: Grazr: Lessons Learned using MySQL and Memcached in Web 2.0 Applications. Its on Thursday, August 14, 2008, and you don’t even need to dress up to listen to Pat talk - the beauty of a webminar :)
P/S: If you don’t already know, subscribing to MySQL Enterprise entitles you to 24/7 production support for memcached. Neat, right?
I don’t know about “me too” types of bug replies, but before everyone goes to the bug database and starts saying “me too”, “this affects me”, “please fix this ASAP”, “I won’t use MySQL 5.1 till this is fixed”, I wonder if this will cause more harm (i.e. more bug spam for the developer, and all those subscribed to it) than good.
It seems like the public Worklog interface gets this right - via voting. Having a count of those that have the same problems, even displayed via “stars”, is a much better interface, and shows urgency a lot better than “me too” posts.
Take one of my favourite worklogs - WL#148 (to implement engine independent foreign keys). Not only can you tag it, you can also comment on it (like a bug report), you can subscribe to it (watch it) and in the event you felt like a “me too”, you just login, and vote!
Lots of bug tracking systems have voting. I remember this being implemented on the OpenOffice.org system (IssueZilla) a few years back, and its definitely proven to be useful. Maybe this is a feature request, for our bugs system?

Amarok 2.0 Alpha 2 (Aulanerk)
Heads up Amarok fans.
The Amarok team released Amarok 2.0 Alpha 2 today, codenamed “Aulanerk” after the friendly sea goddess.
If you don’t already know, Amarok is the most popular media player for Linux today. Amarok 2.0 is new and is set to replace it’s sibling Amarok 1.4 once KDE4 matures. The plan is to have Amarok 2.0 shipped with KDE 4.2 sometime in the future.
Source: Amarok
Tags: amarok, Linux, media players, Open Source, Software