##slackware

The server is back up

2010-11-04T15:25:00.000-04:00

The server was rebuilt. I still don't know what happened. I found no evidence of tampering, but my servers don't normally degenerate like that. The file structure of webroot was changed, along with SSH and other services not working (it wasn't the firewall). I think my son may have done a driveby when I left a terminal session to the linode open. :/

I need ease of use, so it no longer uses Slackware (please spare me the Slackware and simplicity discussion).

Web server is once again sharing content (logs and such).

There is no eggdrop yet. Phrag and I will link slackboy and g0v (redundancy) as soon as I can get the bot going again.

Since there's no eggdrop yet, there's no channel stats (although Phrag has that covered also).

FW is in place, along with Snort. I may do Modsecurity again, but that's not a high priority for me right now.

BTW, the server now uses Ubuntu v10.10

Server is down

2010-10-07T13:15:00.000-04:00

Noticed that the server took a dump last night, not letting me shell into it (showing 'permission denied when I shelled in the night before with an ssh key). I have access via an admin interface, took a look at the logs and didn't see anything. Ended up trying to restart the server...it booted up fine (I didn't see any errors) but the system was still acting hokey.

I can't access the webserver either, as I keep getting 'forbidden' errors.

It may be down for a few days while I find out what's going on.

Need to do items

2010-08-24T11:44:00.001-04:00

Need to update the ##slackware links page:

1. Juhl has a new page that I keep meaning to update (Juhl used to be a channel op a long time ago)

2. Slackware Security link is down (linked to http://www.slacksec.info/)...need to point this to a different place, perhaps to http://www.slackware.com/security/

3. Update Slackware Gallery link (point it to http://gallery.slackadelic.com/index.php).

4. ##slackware stats page needs to point to http://wigglit.ath.cx/slackware_stats2/

5. http://www.slackersbible.org/ should be removed; link broken.

6. http://slackbook.lizella.net/ is broken...needs to be removed.

I just need to do a basic refresh of the page...shouldn't take long.

Security Patches for Slackware -- July 2010

2010-07-24T14:39:00.001-04:00

Security patches for the month of July for Slackware:

mozilla-firefox (SSA:2010-204-01)
seamonkey (SSA:2010-202-03)
mozilla-thunderbird (SSA:2010-202-02)
mozilla-firefox (SSA:2010-202-01)

I'll update this particular post with updates as they come for the month of July.

Security Patches for Slackware -- June 2010

2010-06-29T23:40:00.001-04:00

Security patches for the month of June for Slackware:

libtiff (SSA:2010-180-02)
libpng (SSA:2010-180-01)
cups (SSA:2010-176-05)
mozilla-thunderbird (SSA:2010-176-04)
seamonkey (SSA:2010-176-03)
mozilla-firefox (SSA:2010-176-02)
bind (SSA:2010-176-01)
samba (SSA:2010-169-01)

I'll update this particular post with updates as they come for the month of June.

Security Patches for Slackware -- May 2010

2010-05-18T16:13:00.000-04:00

Security patches for the month of May for Slackware:

pidgin (SSA:2010-138-01)
fetchmail (SSA:2010-136-01)

I'll update this particular post with updates as they come for the month of May.

Security Patches for Slackware -- April 2010

2010-04-26T00:08:00.000-04:00

Security patches for the month of April for Slackware:

irssi (SSA:2010-116-01)
kdebase-workspace (SSA:2010-110-02)
sudo (SSA:2010-110-01)
seamonkey (SSA:2010-095-03)
mozilla-firefox (SSA:2010-095-02)
mozilla-thunderbird (SSA:2010-095-01)

I'll update this particular post with updates as they come for the month of April.

More Server Maintenance

2010-04-24T23:01:00.000-04:00

Jordan reported that the bot logs hadn't been updated since late February. I took a look and that was indeed the case. I didn't start the bot correctly when I last did maintenance. While the bot was working the script that syncs the logs stopped working. I fixed the issue by altering the rsync script.

Thanks, Jordan!

Security Patches for Slackware -- March 2010

2010-03-31T14:04:00.000-04:00

Security patches for the month of March for Slackware:

seamonkey (SSA:2010-090-03)
mozilla-firefox (SSA:2010-090-02)
openssl (SSA:2010-090-01)
pidgin (SSA:2010-069-01)
httpd (SSA:2010-067-01)
mozilla-firefox (Slackware 12.2)
openssl (SSA:2010-060-02)

I'll update this particular post with updates as they come for the month of March.

Hung Apache

2010-03-11T23:46:00.000-05:00

I logged into the server from my Dell Mini and found that I couldn't get to the website. I don't know if this just affected me or everyone, nor do I know how long it was like this. I got a response from the server that the connection could not be made, which told me it was up, otherwise, I'd have gotten a standard browser client error. I restarted the service and was immediately able to connect.

I will check the server logs for anomalies.

Security Patches for Slackware -- February 2010

2010-02-28T23:36:00.000-05:00

Security patches for the month of February for Slackware:

None

I'll update this particular post with updates as they come for the month of February.

Server reboot

2010-02-12T14:29:00.003-05:00

The server will need to be rebooted between today (Friday, February 12th) and Sunday, February 14th at 10:00pm EST.

More than likely, this will happen Sunday afternoon (around 4PM), but I'm still not sure.

Minor server work conducted; stats script adjusted

2010-02-06T17:14:00.003-05:00

I had to reboot the server to free up some drive space (I will need to also offload some logs at a later time, but this shouldn't impact services).

While I was at it, I revised the bot log structure (see here). I tar'd and compressed each month into one file, then put that year's files into one dir (2008, for instance). I saved a ton of space this way. You can bzcat/bzless each file for content (after downloading it). You can even archive all these files. These files contain a wealth of knowledge that can help anyone that lives anywhere!

I've also been working on the stats due to several complaints that several users are within the stats but haven't been within ##slackware in months. Realize that the stats script parses all the logs within the eggdrop logs...the stats are NOT broken. Its a matter of how the script is configured to output its stats. The stats are NOT there to represent in any official capacity the nuances of the channel. The stats are for fun only. This means that I'm not going to always fix the stats to represent someone's viewpoint. The stats were never meant to show the world the channel's signal-to-noise ratio (that's what the actual logs are for and even those are more for research purposes than anything else)...the stats were also not meant to help a channel oper find a troll (again, the actual logs can help with that). So, I'll fix an actual problem with the stats, but half the complaints I've received recently about the stats aren't really problems. That being said, lastly, if you're the type of person that always changes his nick at the drop of a hat, it doesn't bother me but I will NOT alter the stats config file to adjust for the fact that you may be a habitual nick changer. If you want to change your nick constantly, that's fine but let it be known that you're going to cause your stats entry to fork (every time you change to a new nick). I will not fix the forks any longer and further requests will be ignored.

Sorry to seem BOFH-like, but I've a job IRL and I don't always have time to dedicate to troubleshooting an issue that later turn out to not really be an issue.

I've reworked the stats a bit by making them more reader-friendly and cutting some stats-fat. I'm also working on it parsing only the last 30 days of logs. For those that like to show me web examples of others doing this, thanks, but I'd rather see something that shows me how to do it...the README for these scripts are sometimes not intuitive to configuration. I'll continue to work on this. Please limit your input of the stats results to tactful and useful criticism...and remember that it is very difficult to please all requestors.

Security Patches for Slackware -- January 2010

2010-01-30T22:44:00.000-05:00

Security patches for the month of January for Slackware:

mozilla-firefox (SSA:2009-351-01)
httpd (SSA:2010-024-01)
php (SSA:2010-024-02)
pidgin (SSA:2010-024-03)

I'll update this particular post with updates as they come for the month of January.

Security Patches for Slackware -- December 2009

2009-12-18T22:42:00.001-05:00

Security patches for the month of December for Slackware:

bind (SSA:2009-336-01)
kernel (SSA:2009-342-01)
ntp (SSA:2009-343-01)
gimp (SSA:2009-345-01)
seamonkey (SSA:2009-352-01)

I'll update this particular post with updates as they come for the month of December.

Security Patches for Slackware -- November 2009

2009-11-30T22:40:00.001-05:00

Security patches for the month of November for Slackware:

mozilla-firefox (SSA:2009-306-01)
openssl (SSA:2009-320-01)

I'll update this particular post with updates as they come for the month of November.

Security patches for Slackware -- Octobert 2009

2009-10-31T20:42:00.000-04:00

Security patches for the month of October for Slackware:

gnutls (SSA:2009-290-01)
pidgin (SSA:2009-290-02)
xpdf (SSA:2009-302-01)
poppler (SSA:2009-302-02)
samba (SSA:2009-276-01)
php (SSA:2009-276-02)

I'll update this particular post with updates as they come for the month of October.

Rebooted Server

2009-10-05T09:39:00.003-04:00

I rebooted the server two days ago.

The server had 474 days of uptime. My drive space was at 94% and I didn't feel like archiving a bunch of data. I had 9G free space so I resized the current partition to 2G to buy me some time.

Of course, with rebooting come the uncertainty of certain services starting on their own. The webserver didn't start on its own, even though the startup script is set up correctly (and has the executable bit turned on). The IRC bot didn't start on its own, either...

Another thing I've to deal with is that the IRC bot won't autoidentify with NickServ, even though I've configured the tcl script correctly (this has been a development in progress for years...).

Security patches for Slackware -- September 2009

2009-09-14T03:21:00.001-04:00

Security patches for the month of September for Slackware:

seamonkey (SSA:2009-250-01)
mozilla-firefox (SSA:2009-257-01)

I'll update this particular post with updates as they come for the month of September.

Security patches for Slackware -- August 2009

2009-08-20T22:31:00.002-04:00

Security patches for the month of August for Slackware:

httpd (SSA:2009-214-01)
mozilla-firefox (SSA:2009-215-01)
fetchmail (SSA:2009-218-01)
subversion (SSA:2009-219-01)
apr (SSA:2009-219-02)
apr-util (SSA:2009-219-03)
curl (SSA:2009-226-01)
kernel (SSA:2009-230-01)
kernel [updated] (SSA:2009-231-01) <== follow-up to SSA:2009-230-01 above
pidgin (SSA:2009-231-02)
mozilla-thunderbird (SSA:2009-232-01)

I'll update this particular post with updates as they come for the month of August.

Linode uptime

2009-08-06T18:10:00.003-04:00

ron@starchild:~$ w
18:09:25 up 417 days, 5:21, 2 users, load average: 0.01, 0.01, 0.00

Last year, I had the around the same, per linuxcounter.org's stats:

ID Name Last auto-update Uptime
316269 starchild 2008-05-12 00:06:02 414.8

Nice, huh?? Don't let the load average fool you...it has a decent load at certain intervals, and that doesn't include when I'm doing maintenance.

Security patches for Slackware -- July 2009

2009-07-15T08:08:00.003-04:00

Security patches for the month of July for Slackware:

dhcp (SSA:2009-195-01)
mozilla-firefox (SSA:2009-209-01)
bind (SSA:2009-210-01)

I'll update this particular post with updates as they come for the month of July.

Slackware.com Site Down; Slackware v13.0 RC1 out

2009-07-06T22:11:00.002-04:00

Apparently, the Slackware.com site is down and has been since late yesterday. Also, the site supposedly has been experiencing intermittent connectivity issues for at least a week. I've no idea why, but it is possible that the site/server is being revamped due to the release of v13.0 being imminent.

Yes, Slackware v13.0 is in release candidate stage 1. This includes 64-bit and 32-bit, I believe. It is difficult to determine the nature of the release when the main site is down, though, so bear with me. As soon as I find more info, I'll update this entry.

Things to do

2009-07-05T16:55:00.002-04:00

1. Update ##slackware users links...Juhl (a previous ##slackware oper) is active again and gave me some updated URLs.

2. Apparently, the ##slackware stats page is broke. Fix this within a week.

EDIT: Stats page is fixed: See http://wigglit.ath.cx/slackware_stats2/ When I upgraded Apache to the latest version, I had to change the path of the webserver pages directory, which broke a backend script. Also, there were no image files in the stats directory. All is well now.

Security patches for Slackware -- June 2009

2009-06-30T02:40:00.000-04:00

Security patches for the month of June for Slackware:

ntp (SSA:2009-154-01)
apr-util (SSA:2009-167-02)
mozilla-firefox (SSA:2009-167-01)
libpng (SSA:2009-170-01)
ruby (SSA:2009-170-02)
seamonkey (SSA:2009-176-01)
samba (SSA:2009-177-01)
mozilla-thunderbird (SSA:2009-178-01)
ghostscript (SSA:2009-181-01)

I'll update this particular post with updates as they come for the month of June.

Youch! Freenode bans Mibbit.com connections

2009-06-26T22:00:00.003-04:00

New freenode webchat (and why to use it)

OW.

I remember awhile back, the server opers would frown upon banning Mibbit users. I guess they had a change of heart due to abusers using Mibbit to dodge bans. I remember having to place broad bans on Mibbit on a temp basis, but it was always temporary bans that I placed. I even became a Mibbit user. I hadn't joined the server using Mibbit in about a month so something happened recently for Freenode to lock out all Mibbit connections.

Oh well.

For now, Freenode is hosting its own web-IRC client: http://webchat.freenode.net/

Modsecurity is blocking some access to the channel logs

2009-06-24T23:24:00.003-04:00

Looking through the firewall logs, I noted an IP that had a 300+ hitcount. It was Googlebot, but I was curious as to what Google was doing and how the Modsecurity logs looked. See below:

[Wed Jun 24 12:15:57 2009] [error] [client 66.249.72.197] ModSecurity: Access denied with code 500 (phase 4). Pattern match "(?:\\b(?:(?:s(?:elect list because it is not contained in (?:an aggregate function and there is no|either an aggregate function or the) GROUP BY clause|upplied argument is not a valid (?:(?:M(?:S |y)|Postgre)SQL|O(?:racle|DBC)))|S(?:yntax error converti ..." at RESPONSE_BODY. [file "/etc/httpd/conf/modsecurity_crs_50_outbound.conf"] [line "23"] [id "970003"] [msg "SQL Information Leakage"] [severity "WARNING"] [tag "LEAKAGE/ERRORS"] [hostname "wigglit.ath.cx"] [uri "/slackware_botlogs/slackware.log.26Jan2009"] [unique_id "SkJRPUKgjR4AABcVLwoAAAAK"]

Something is preventing Googlebot from logging this page (and a few others). More than likely, there is some SQL code in these logs that is causing these blocks. I'll look at this further throughout the week and possibly disable this rule if it becomes extremely problematic, especially to normal visitors (I attempted to view the page above but the attempt was blocked).

Uptime!

2009-06-23T22:54:00.004-04:00

Latest uptime for the server:

22:52:30 up 373 days, 10:04, 3 users, load average: 0.05, 0.04, 0.00

Yeah, some say that keeping track of uptime stats is 'old school', and some will say that availability is more important. I beg to differ, because if your server is down (downtime), there is NO availability. So, same crap, different stink.

Eggdrop patching

2009-05-18T18:28:00.006-04:00

Looks like I need to patch Slackboy (the channel admin bot).

http://www.milw0rm.com/exploits/8695:

eggdrop/windrop remote crash vulnerability

* This message: [ Message body ] [ More options ]
* Related messages: [ Next message ] [ Previous message ] [ Next in thread ] [ Replies ]

From: Thomas Sader
Date: Fri, 15 May 2009 05:54:08 +0200

Affected software
-----------------

eggdrop (1.6.19 only, not 1.6.19+ctcpfix)
windrop (1.6.19 only, not 1.6.19+ctcpfix)
all eggdrop/windrop versions and packages which apply Nico Goldes
patch for CVE-2007-2807/SA25276 See: [1]

Vulnerability details
---------------------

The SA25276 patch ([1]) uses strncpy to fix a buffer overflow vulnerability
in src/mod/server.mod/servmsg.c (gotmsg). The last argument is not checked
for being non-negative, but that can happen if ctcpbuf is "". That causes
a remote crash vulnerability to be exploited by anyone connected to the same
IRC network as eggdrop. The SA25276 patch has been applied to the eggdrop1.6.18
debian package and was later adopted by Eggheads into eggdrop1.6.19.

One possible exploit anyone can send to the IRC server to crash eggdrop:

PRIVMSG eggdrop :\1\1

Resolution
----------

Upgrade to eggdrop/windrop 1.6.19+ctcpfix ([2],[3]), the current cvs versions,
or apply the ctcpfix patch at [2] before compiling.

Disclosure timeline
-------------------

2009-05-06: Vulnerability discovered and reported to Eggheads.
2009-05-06: Patch committed to cvs.
2009-05-14: New eggdrop and windrop version released with the fix applied.
2009-05-14: Public disclosure.

References
----------

[1] http://bugzilla.eggheads.org/show_bug.cgi?id=462
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427157
http://www.securityfocus.com/bid/24070
http://secunia.com/advisories/25276
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2807

[2] http://www.eggheads.org/downloads/
[3] http://windrop.sourceforge.net/downloads.html

---
Thomas Sader (thommey)

# milw0rm.com [2009-05-15]

EDIT -

I patched Slackboy: eggdrop v1.6.19+ctcpfix

It is running the same config and user/channel files, so there shouldn't be any access issues or problems with excessive kicking/banning.

Having already had the 1.6.19 version helped somewhat...glad I updated the eggbot when I was supposed to! :)

All I had to do was follow this link...basically I patched and rebuilt the binary, then used my old configs.

Thanks to Strykar of ##slackware for the heads-up!

Security patches for Slackware -- May 2009

2009-05-17T20:19:00.007-04:00

Security patches for the month of May for Slackware:

ruby (SSA:2009-120-01)
gnutls (SSA:2009-128-01)
xpdf (SSA:2009-129-01)
cyrus-sasl (SSA:2009-134-01)
pidgin (SSA:2009-146-01)

I'll update this particular post with updates as they come. Expect a similar post every month. I should also make a similar page on the website that tracks these.

Also, note that last month, the Slackware team made BitchX EOL. Here's the e-mail that I received:

[slackware-security] bitchx EOLed in Slackware (SSA:2009-116-02)

This is a notice that bitchx, an IRC client based on ircii-EPIC4, has been
removed from Slackware -current and will not be part of future Slackware
releases. Security issues and bugs have been reported, but upstream
work seems to have stalled leaving bitchx in a state where there are
known problems without official (or in some cases any) fixes.

The most secure course of action is to remove bitchx from the system and
switch to using a supported IRC client.

We have not compiled a complete list of open issues in BitchX, but here are
a few that we know about:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-3360
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-4584
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5839

Package removal instructions:
+---------------------------+

Remove the package as root:
# removepkg bitchx

Some admins may also want to add a symlink to another console IRC client
such as irssi to help users migrate:

cd /usr/bin
ln -sf irssi BitchX

+-----+

Slackware Linux Security Team
http://slackware.com/gpg-key
security@slackware.com

Not exactly good, but anyone who wants/needs it can always build their own package...all you have to worry about is how the dev team handles the discovered vulnerabilities.

--
Ron

Modsecurity edits

2009-01-28T00:06:00.003-05:00

I've added the following config file to enhance my Modescurity ruleset:

http://www.gotroot.com/downloads/ftp/mod_security/2.0/apache2/rules.conf

I immediately had to disable the first rule (enforcing proper HTTP requests), as it was blocking almost EVERYTHING, including my own HTTP client.

I'll monitor the logs throughout the day tomorrow to ensure things are OK.

Found the issue with 'mail'

2009-01-25T00:59:00.004-05:00

I did some grepping of another system that had v12 of Slackware installed:

ron@suna:~$ ls -l /usr/bin/mail
lrwxrwxrwx 1 root root 5 2007-11-02 18:24 /usr/bin/mail -> mailx*

ron@suna:~$ ls -l /var/log/packages/*mail*

-rw-r--r-- 1 root root 4814 2007-11-02 18:24 /var/log/packages/fetchmail-6.3.8-i486-2
-rw-r--r-- 1 root root 3004 2007-11-02 18:24 /var/log/packages/getmail-4.7.4-noarch-1
-rw-r--r-- 1 root root 1112 2007-11-02 18:24 /var/log/packages/mailx-12.1-i486-1
-rw-r--r-- 1 root root 2215 2007-11-02 18:24 /var/log/packages/metamail-2.7-i486-2
-rw-r--r-- 1 root root 2024 2007-11-02 18:25 /var/log/packages/procmail-3.22-i486-2
-rw-r--r-- 1 root root 2780 2007-11-02 18:26 /var/log/packages/sendmail-8.14.1-i486-1
-rw-r--r-- 1 root root 9388 2007-11-02 18:26 /var/log/packages/sendmail-cf-8.14.1-noarch-1

ron@suna:~$ cat /var/log/packages/mailx-12.1-i486-1 | grep /usr/bin/mailx

ron@suna:~$ cat /var/log/packages/mailx-12.1-i486-1
PACKAGE NAME: mailx-12.1-i486-1
COMPRESSED PACKAGE SIZE: 231 K
UNCOMPRESSED PACKAGE SIZE: 470 K
PACKAGE LOCATION: /var/log/mount/slackware/n/mailx-12.1-i486-1.tgz
PACKAGE DESCRIPTION:
mailx: mailx (a simple mail client)
mailx:
mailx: Mailx is derived from Berkeley Mail and is intended provide the
mailx: functionality of the POSIX mailx command with additional support
mailx: for MIME, IMAP, POP3, SMTP, and S/MIME. It provides enhanced
mailx: features for interactive use, such as caching and disconnected
mailx: operation for IMAP, message threading, scoring, and filtering.
mailx: It is also usable as a mail batch language, both for sending
mailx: and receiving mail.
mailx:
mailx: The maintainer and primary developer of nail is Gunnar Ritter.
FILE LIST:
./
bin/
etc/
etc/nail.rc.new
usr/
usr/bin/
usr/bin/mailx
usr/doc/
usr/doc/mailx-12.1/
usr/doc/mailx-12.1/TODO
usr/doc/mailx-12.1/README
usr/doc/mailx-12.1/AUTHORS
usr/doc/mailx-12.1/INSTALL
usr/doc/mailx-12.1/ChangeLog
usr/doc/mailx-12.1/COPYING
usr/man/
usr/man/man1/
usr/man/man1/mailx.1.gz
install/
install/doinst.sh
install/slack-desc

Found the package @ http://slackware.mirrors.tds.net/pub/slackware/slackware-12.0/slackware/n/mailx-12.1-i486-1.tgz, downloaded and installed it.

Problem resolved.

Recent issues and upgrades

2009-01-25T00:33:00.006-05:00

I've updated Apache to v2.2.9 (this was mandatory, so that I could install Modsecurity).

When I upgraded Apache, I didn't realize that it would break the bot's logging scripts. I'll have to look at this tomorrow (its too late to do it today).

I also upgraded the Modsecurity ruleset. Please be aware of any new access constrictions that I need to be aware of. Here's an example of how a bad rule may work: When I upgraded the ruleset, I noticed that a site visitor could no longer access that part of the website. When I checked, I saw that there was a rule preventing listings of directories. I disabled the rule.

I've also noticed that I can no longer check system mail by typing 'mail' in CLI. I need to find out how this is done in Slackware 12.0 (obviously something changed between v12 and v9).

Also installed screen (no idea how I've not noticed this before).

EDIT -- I believe I've fixed the log script issue. A simple directory change was needed. I'll check for success in the AM. I did a manual rsync of the old and new directory and found that 32 files were missing, so this problem dates back to Christmas Day.

Backend tools

2008-12-24T11:49:00.004-05:00

I've installed Webalizer so that I can better monitor web traffic to the server. The config file needs to be tuned (I can get good results via a CLI run, though). Thanks to alienBOB and ananke for their help in getting this running, as I had an issue with compiling Webalizer where libgd wasn't being recognized (I've learned to now always check my config.log).

I'm also running Snort on this machine (its been running since the beginning).

I'm running a simple Iptables script (it will be gradually hardened).

I'm also running denyhosts. It monitors the typical SSH brute force attempts.

Webmin is installed (on a non-default port).

A future project is to get modsecurity installed (it was installed in the prior version of the OS). This will help with attacks against the webserver itself (since the firewall is configured to allow web traffic). For now, since the website is set up in a static manner, I can dodge the attacks that look for dynamic vulnerabilities.

More work...

2008-06-16T19:47:00.004-04:00

1. Backed up new cronjob directory, then moved old cronjob directory in place of new. This means I've to tackle all things listed within the crons tonight or disable what I don't tackle before I quit server maintenance tonight (otherwise I'm going to have a ton of errors in the syslog and possibly mail.

2. Enabled the script that controls the ##slackware stats page (##slackware stuff).

3. Installed ntpdate (internal server stuff).

4. Enabled Linux Counter project script that tracks uptime (internal server stuff).

5. Enabled the channel bot logging scripts (##slackware stuff).

I believe this part of updates to the new server should be complete, but the proof will be in the syslog, I guess.

Also, I'm sick and may put off some of this maintenance until I'm feeling a bit better...sorry...

Current status:

1. Bot -- up **
2. Channel stats (on webserver) -- up, with cronjob that updates pages now running
3. Channel logs (on webserver) -- up, with cronjob that rsyncs files to webserver now running
4. Webserver -- up

** Admins, pls check your access to ensure things are fine.

Server rebuild

2008-06-15T15:53:00.000-04:00

unixfool has rebuilt the Linode server that hosts the channel's information (guidelines pages, stats page, channel logs...).

The server was upgraded from Slackware v9.0 to v12.0. The server has been stable for many years but was sorely in need of an upgrade that was supported by the maintainer of the distribution.

The bot, slackboy, is up and running after a hectic night of transferring it from v9.0 to v12.0, which wasn't quite as trivial as first thought out.

The web server itself was just re-initialized and is using an upgraded version of Apache. All data is now viewable from the server that was viewable before the upgrade.

The channel stats page will need to be worked on sometime this week but should be finished by next Sunday at the latest.

The work so far to get things semi-working again has been tremendous (I was up until 4:30am this morning) and there is still a lot of work to do to get things at the level they were before the distro upgrade.

Internal software (denyhosts, mnwclient, dshieldclient, Snort, Modsecurity) still has to be reinstalled but I plan to have most installed within the next 30 or so days.

So, the current status:

1. Bot -- up **
2. Channel stats (on webserver) -- up but not current
3. Channel logs (on webserver) -- down
4. Webserver -- up

** Admins, pls check your access to ensure things are fine.