Modify Apache webserver to show something else on Netcraft

I guess I was wrong. I guess the other reason might be just to look cool for geeks. So here are the steps: 1) download the source rpm for my distro.
2) install it.
rpm -ivh apache-2.0.55-3tr.src.rpm
3) make a patch. Here’s how:
cd /usr/src/trustix/sources
tar jxvf httpd-2.0.55.tar.bz2
cp -pr httpd-2.0.55 httpd-2.0.55-orig
vi httpd-2.0.55/include/ap_release.h
— then change the AP_SERVER_BASEPRODUCT to whatever you want. In my case, I used ShocKNetworK.
4) create a patch.
diff -urN httpd-2.0.55-orig/include/ap_release.h httpd-2.0.55/include/ap_release.h > shock.patch
5) add the patch to the spec file list
vi /usr/src/trustix/specs/apache.spec
added to where it lists the patches (your numbers may vary):
Patch6: shock.patch
and where it does the prep:
%patch6 -p1
(Just do a search for patches and you’ll find it)
6) build the rpm:
rpmbuild -ba /usr/src/trustix/specs/apache.spec In my case, I ran into a dependencies problem:
root@chunli /usr/src/trustix/specs# rpmbuild -ba apache.spec
error: failed build dependencies:
expat-devel is needed by apache-2.0.55-3tr
gdbm-devel is needed by apache-2.0.55-3tr So I just downloaded installed them:
swup –install expat-devel gdbm-devel
Trustix (http://www.trustix.org) has a pretty cool tool called “swup” which is similar to yum (that Fedora http://fedora.redhat.com includes or some others. If you don’t have either of these, you could easily just download the rpms from your mirrors and install them manually. So, after all of the stuff’s built and done, I found my rpms in /usr/src/trustix/rpms/i586 So, I just reinstalled it.
root@chunli /usr/src/trustix/specs# rpm -e –nodeps apache
warning: /etc/httpd/conf/httpd.conf saved as /etc/httpd/conf/httpd.conf.rpmsave
root@chunli /usr/src/trustix/specs# rpm –nodeps –force -Uvh /usr/src/trustix/rpms/i586/apache-2.0.55-3tr.i586.rpm
Preparing… ########################################### [100%]
1:apache ########################################### [100%]
root@chunli /usr/src/trustix/specs# cp /etc/httpd/conf/httpd.conf.rpmsave /etc/httpd/conf/httpd.conf
root@chunli /usr/src/trustix/specs# /etc/init.d/httpd restart It’s pretty simple stuff – definitely not rocket science. Something to do when you’re bored I guess. Another thing is, if you go to Netcraft and you see something like this:
ShocKNetworK/2.0.55 (Trustix Secure Linux/Linux) You can hide the version and stuff by opening the httpd.conf and adding to the Section 1: Global Environment:
ServerTokens Prod I also set
ServerSignature Off
just so that it doesn’t show up where I have some directory file listings when there’s no index file. Fun stuff, huh?]]>

followup: up at 5am! (river rafting)

http://www.whitewatervoyages.com/rivers … river.html It was rather fun and I’d definitely do it again. We’ll probably go again next month. We’re debating on how to do it though. Some want to do a class 4, but I’m arguing to do a class 3 without a guide. Hopefully, they give us our refund – we initially scheduled 5 people and only 4 went and also rented 5 wetsuits and only needed 3, so we’ll see what happens. If we don’t get the refund or credit, we might not go to the same place again. After rafting, we stopped by downtown Sacramento on the way home. Just to take a stroll around the capitol and stop by a coffee shop for a pastry/coffee and conversation for a break away from driving. Among other things we talked about, I remembered talking about genetically modified food – how it may not be fully tested, etc. I guess there’s a couple arguments for and against it. Growing corn that the bugs won’t eat might be cool so we can have more food for ourselves, but who knows? Maybe the bugs know better not to eat the corn for one reason or another. Then again, this might be a good thing as we can grow more food for less money and we can feed more people with it. It may disturb the ecosystem a bit though – perhaps creating an imbalance. When they took the wolves out of Yellowstone park because they were killing a lot of elk, they created in imbalance where all of the water was being drinken and grass was being eaten. Bring the wolves back brought back some balance. For dinner, we headed to a restaurant called Prasand. (http://www.pasand.com/index.html) It was pretty good – had a bread basket, some naan and Chicken Tikka Masala Curry. I’d recommend the restaurant – I went with Indians and they thought it was good and authentic. It was good for my taste buds as well. Our dinnertime conversation included of some talk about some of the art on the wall. I asked about one of them similar to this one:
Image
(Image pulled from: http://www.asitis.com/)
From that, I got the brief version of the story about Krishna and Arjuna. The Legend of Bagger Vance was actually a book based on that story. Cool stuff. Was exhausted – went home, showered and went to bed.]]>

PIPE channel in iMS

iMS 5.x – Setting up Program Delivery through the PIPE channel

The purpose of this article is so that you will be able to send email to an script or program like procmail and do something with it.

1. Make sure that your mailsrv user has a home directory that he can write to. /tmp will work just fine. The user does not need to have a valid shell, so /bin/false will work.

2. Write the program and put it in msg-/imta/programs directory.

In my case, I will be creating symbolic link to cat.

# cd msg-/imta/programs

# ln -s /usr/bin/cat cat

3. register cat into the MTA program list.

# ./imsimta program -a -p cat -m catter -g ‘>>/tmp/alton_mails’ -e user

4. list programs to see that your program is there:

#./imsimta program -l

==================================================

Method_name : catter

Program_name : /opt/iMS5.1/msg-goofy/imta/programs/cat

Argument_list : >>/tmp/alton_mails

Execute Permission : User

==================================================

5. add program delivery attributes to your user ldap entries:

mailprogramdeliveryinfo: catter

maildeliveryoption: program

6. execute “imsimta dirsync -F” if necessary.

7. run ./imsimta test -rewrite – you should see that it will send to the pipe channel.

Submitted address list:

ims-ms

program1@ims-ms-daemon (orig [email protected], inter [email protected], host ims-ms-daemon) *NOTIFY-FAILURES* *NOTIFY-DELAYS*

pipe

[email protected]-daemon (orig [email protected], inter [email protected], host catter.pipe-daemon) *NOTIFY-FAILURES* *NOTIFY-DELAYS*

8. Send mail to the user and test it!

mysql commands – create database / set permissions

/usr/bin/mysqladmin -u root password ‘new-password’
/usr/bin/mysqladmin -u root -h chunli.shocknetwork.com password ‘new-password’

mysql -u root -p -e “create database <dbname>”
mysql -u root -p -e “grant all on <dbname>.* to <user>@localhost identified by ‘<password>'”