home
> blog
>> 425
| [previous] / [up] | [overview] | [down] / [next] |
Tue Sep 20 19:56:45 2005 GMT: GSA
Sun Sep 18 19:00:15 2005 GMT: More WRT54G Firmware Hacking
Wed Sep 14 18:33:42 2005 GMT: SSH Brute Force Attack
Today, someone apparently tried to break into edge.cmeerw.net by using a ssh brute force attack (from IP address 210.94.27.156 which appears to be some ISDN dialup connection). Well, there is not much to say about this attempted attack except that the client seems to be have been built with libssh...
Sun Sep 11 21:07:59 2005 GMT: WRT54G Fimware Hacking
I have recently been hacking a bit on my WRT54G firmware, mainly to just update the included software, but I have also added a small uptimes client. You can have a look at the router statistics here.
Thu Sep 01 20:26:08 2005 GMT: jabberd2 64-bit brokenness
Following up on a report of a reproducible crash of the s2s component of jabberd2, I have had a look at the source code to analyse the problem.
Wed Aug 24 22:50:57 2005 GMT: Where is all the RAM?
I have been scratching my head for some time now why the company's proxy server performance was quite bad in the past few weeks. Apparently, a lot of swapping was dramatically slowing down the machine, but I just couldn't figure out the reason for all the swapping, because the machine's configuration didn't change for quite a while.
Unfortunately, "ps" or "top" also weren't of much help here - they didn't show any unusual memory hogs, but "free" insisted that there was no free memory and only a few MBs used for buffers and caches.
Today, I finally looked through the /proc filesystem to see if I could find any unusual traces there. And yes, when looking at /proc/slabinfo I noticed that the kernel has allocated around 200000 "sock" object (consuming around 50000 4k pages or 200 MB of RAM). Hmm, maybe this was a left-over of one of those Bitdefender DoS attacks.
Well, a reboot seems to have fixed the problem for now.
Wed Aug 24 19:57:14 2005 GMT: Google Talk
Hmm, they use an open protocol (XMPP) with some proprietary extensions (VoIP signalling, although they claim to be documenting the extensions in the future) to build a closed service (by not allowing XMPP's server-to-server communication). And by installing their client software you "agree to automatically request and receive Updates" from their servers.
Sounds a lot like Microsoft, doesn't it? But, it's not, it's Google Talk.
BTW, there is an interesting article about Google in the IHT: Google taking on Microsoft's role of villain
Sat Aug 13 18:38:40 2005 GMT: Upgrading to Hoary Hedgehog
Tue Aug 09 18:16:19 2005 GMT: One More Reason to Ignore Google
Mon Aug 08 19:17:15 2005 GMT: Concurrent Access To SQLite Database
Sun Aug 07 08:29:41 2005 GMT: Solaris Internals
Tue Aug 02 19:54:03 2005 GMT: Atom 1.0
