Jericho Situmorang

Choose gcc and g++ version. Downgrade gcc-4.4 to gcc-4.3

000jericho — Wed, 11 Apr 2012 23:06:50 GMT

Tingkat terakhir di kampus (sebut saja ITB) merupakan hal-hal yang paling sibuk. Why not? untuk mengerjakan Tugas Akhir yang 5 SKS dan dipaksa untuk menyelesaikan secepat mungkin, semua cara dilakukan dari awal hingga menemukan sebuah inspirsai. Yah walau cuma ide sesaat.

Contohnya: Saat ini (12 April 2012) subuh-subuh di lab ICA (Intelligent Control System), saya seorang mahasiswa yang mencoba-mencoba untuk "ngoprek" Software OpenTLD aka Predator aka TLD Vision. Saat itu sedang berusaha keras mencoba menggunakan software tersebut di laptop pribadi (Intel(R) Core(TM)2 CPU T5300 @1.73GHz) dengan OS Linux Ubuntu 10.04.

Perlengkapan tempur dalam laptop:
1. OpenCV 2.3.1
2. Matlab R2011b

Setelah mencoba-coba baca dari beberapa referensi tiba-tiba DAMN, untuk running file "compile.m" diperlukan gcc-4.3 (Matlab R2011b) sedangkan yang tersedia saat ini gcc-4.4.

Next, dengan segala cara mau tidak mau compiler harus di downgrade. OK baeklah. Berikut step-by-stepnya:

1. Pertama kita hapus dulu yang ada

sudo update-alternatives --remove-all gcc 
sudo update-alternatives --remove-all g++

2. Install lagi package-nya

sudo apt-get install gcc-4.3 gcc-4.4 g++-4.3 g++-4.4

3. Install alternative-nya

sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.3 10
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.4 20

sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.3 10
sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.4 20

sudo update-alternatives --install /usr/bin/cc cc /usr/bin/gcc 30
sudo update-alternatives --set cc /usr/bin/gcc

sudo update-alternatives --install /usr/bin/c++ c++ /usr/bin/g++ 30
sudo update-alternatives --set c++ /usr/bin/g++

4. Step terakhir kita konfigurasi

sudo update-alternatives --config gcc
sudo update-alternatives --config g++

OK sekarang gcc kita telah dibuat menjadi gcc-4.3. Lanjut lagi ngopreknya.

$ gcc --version
gcc (Ubuntu 4.3.4-10ubuntu1) 4.3.4
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

#FightForOctober #Yeahhh

SOP Surfer 8.0

000jericho — Thu, 15 Mar 2012 03:17:34 GMT

Berikut adalah cara atau langkah-langkah pengoprasian aplikasi Surfer 8.0 untuk pembuatan kontur.

New - Worksheet
Tulis data X Y dan Z pada sheet. X dan Y adalah koordinat titik pengukuran sedang Z adalah nilai yang akan dilihat konturnya
Save file dalam bentuk xls
New - Plot documents
Grid - data
Buka File xls tadi
Atur data column, hati-hati penempatan koordinat dengan kolum pada sheet
OK
Map - Contour map - New Contour Map
Buka File hasil grid data tadi file.grd
hasil keluar, silahkan atur-atur kontrasnya, dalam properties centang fill contour

[Quiz] exploit this program!

000jericho — Tue, 22 Nov 2011 13:37:54 GMT

Bank terkenal di Republik Kaya-Raya, baru meluncurkan program transfer secara online melalui mesin ATM. Hanya tinggal memasukkan jumlah yang ditransfer, maka uang nasabah akan ditransfer, canggih sekali bukan? :D

Namun sayangnya, program ATM tersebut mengandung vulnerability yang sangat berbahaya karena dapat membocorkan data bank yang kategorinya "very very top super classified". Pokoknya kalau sampai data ini bocor, bank bisa bangkrut!

Quiznya:

1. Dimanakah letak kesalahannya?

2. Exploitlah program ini untuk mencuri data rahasia bank.

3. Sertakan screenshot sebagai bukti anda berhasil mengexploit program ini.

Hints: data ini adalah data sangat rahasia, nasabah pemakai ATM tidak boleh tahu. Tapi dengan memasukkan "magic number" tertentu, nasabah bisa mencuri data tsb ~i

Selamat mencoba )-l

#include

int main(void)

{

char *passwd="rahasia"; // super extreme top secret data!

int saldo=1000000000; // satu milyar

int transfer;

printf("Masukkan jumlah transfer:");

scanf("%d",&transfer);

saldo = saldo - transfer;

printf( "Saldo sekarang: %s\n",saldo);

return 0;

}

source code diatas dan disave saldo.c (atau apapun)

jericho@go-rangers:~/belajar C$gcc saldo.c -o saldo

jericho@go-rangers:~/belajar C$ gdb -q ./saldo

Reading symbols from /home/jericho/belajar C/saldo...(no debugging symbols found)...done.

(gdb) set disassembly-flavor intel

(gdb) disassemble main

Dump of assembler code for function main:

0x08048444 <+0>: push ebp

0x08048445 <+1>: mov ebp,esp

0x08048447 <+3>: and esp,0xfffffff0

0x0804844a <+6>: sub esp,0x20

0x0804844d <+9>: mov DWORD PTR [esp+0x1c],0x8048570

0x08048455 <+17>: mov DWORD PTR [esp+0x18],0x3b9aca00

0x0804845d <+25>: mov eax,0x8048578

0x08048462 <+30>: mov DWORD PTR [esp],eax

0x08048465 <+33>: call 0x8048364

0x0804846a <+38>: mov eax,0x8048592

0x0804846f <+43>: lea edx,[esp+0x14]

0x08048473 <+47>: mov DWORD PTR [esp+0x4],edx

0x08048477 <+51>: mov DWORD PTR [esp],eax

0x0804847a <+54>: call 0x8048374 <__isoc99_scanf@plt>

0x0804847f <+59>: mov eax,DWORD PTR [esp+0x14]

0x08048483 <+63>: sub DWORD PTR [esp+0x18],eax

0x08048487 <+67>: mov eax,0x8048595

0x0804848c <+72>: mov edx,DWORD PTR [esp+0x18]

0x08048490 <+76>: mov DWORD PTR [esp+0x4],edx

0x08048494 <+80>: mov DWORD PTR [esp],eax

0x08048497 <+83>: call 0x8048364

0x0804849c <+88>: mov eax,0x0

0x080484a1 <+93>: leave

0x080484a2 <+94>: ret

End of assembler dump.

(gdb) x/s 0x8048570

0x8048570: "rahasia"

(gdb) p 1000000000-0x8048570

$1 = 865485968

(gdb)

magic number = 865485968

jericho@go-rangers:~/belajar C$ ./saldo

Masukkan jumlah transfer:865485968

Saldo sekarang: rahasia

jericho@go-rangers:~/belajar C$ ./saldo

Masukkan jumlah transfer:865485967

Saldo sekarang: ahasia

jericho@go-rangers:~/belajar C$ ./saldo

Masukkan jumlah transfer:865485961

Saldo sekarang:

jericho@go-rangers:~/belajar C$ ./saldo

Masukkan jumlah transfer:865485960

Saldo sekarang: Masukkan jumlah transfer:

jericho@go-rangers:~/belajar C$

Perhatikan dengan mengurangkan jumlah transfer, didapatkan data rahasia tapi tidak lengkap, karena addressnya tidak dimulai dari awal string. bahkan pada saat nilai transfer 865485961, tidak muncul apa2 karena di posisi 1M-865485961, ditemukan NULL yang mengakhiri string "rahasia".

Tepat setelah nilai transfer 865485961, dikurangkan 1 menjadi 865485960, kita dapatkan string "Masukkan jumlah transfer:", yaitu parameter ketika memanggil printf().

Jadi jelas printf yang seperti itu akibatnya berbahaya, karna attacker bisa reading memory at arbitrary locations.

INSTALLING KALKUN

000jericho — Fri, 18 Mar 2011 11:00:45 GMT

Kalkun is open source web-based SMS (Short Message Service) management, it use gammu-smsd as SMS gateway engine to deliver and retrieve messages from your phone/modem. Kalkun and gammu is two different things. you have to install and configure gammu at yourself. Kalkun only manage database that given by gammu.

Now we will install kalkun 0.2.1

Before install kalkun, we must install web server.

First, you have to add my PPA (Personal Packages Archive) to your repository list (/etc/apt/source.list).

deb http://ppa.launchpad.net/back2arie/ppa/ubuntu lucid main
deb-src http://ppa.launchpad.net/back2arie/ppa/ubuntu lucid main

Next, add my key to verify the packages and then, update your repository:

$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys B3830FF1
$ sudo apt-get update

Let's we install kalkun

$ sudo apt-get install kalkun

This will install kalkun will all required packages, like apache2, php5, mysql-client, and gammu-smsd. mysql-server is not installed by default, because you might want to use external database, but if you want to use local database, you must install mysql-server package.

$ sudo apt-get install mysql-server

Now, we have kalkun and all required packages installed.

Next is configuration.
=========================================
Database configuration
=========================================
Connect to mysql server and create database named kalkun

$ mysql -u root -p
mysql> CREATE DATABASE kalkun;

It’s highly recommended to create specific database user for kalkun database, so other user will not get interrupted, it’s security issue.

mysql > GRANT ALL PRIVILEGES ON kalkun.* TO 'username'@'localhost' IDENTIFIED BY 'password'

Change username and password as you want.
Then, flush privileges to activate your changes

mysql> FLUSH PRIVILEGES;

==========================================
Gammu-SMSD
==========================================
Connect your phone, and see where it’s attached to.

$ tail -f /var/log/messages

Create log file

$ sudo touch /etc/smsdlog

Edit /etc/gammu-smsdrc.

[gammu]
 port = /dev/ttyUSB0 # change this
 connection = at115200 #chage this

[smsd]
 PIN = 1234
 service = mysql
 DeliveryReport = sms
 logfile = /etc/smsdlog
 debuglevel = 1 # change to 255 if you want to debug

 User = username # change this
 Password = password # change this
 PC = localhost
 Database = kalkun

Option for connection
; This is a sample ~/.gammurc file.
; In Unix/Linux copy it into your home directory and name it .gammurc
; or into /etc and name it gammurc
; In Win32 copy it into directory with Gammu.exe and name gammurc
; More about parameters later
; Anything behind ; or # is comment.
; -----------------------------------------------------------------------------

[gammu]

device = com8:
connection = irdaphonet
; Do not use model configuration unless you really need it
;model = 6110
;synchronizetime = yes
;logfile = gammulog
;logformat = textall
;use_locking = yes
;gammuloc = locfile
;startinfo = yes
;gammucoding = utf8
;usephonedb = yes

[gammu1]

device = com8:
;model = 6110
connection = fbusblue
;synchronizetime = yes
;logfile = gammulog
;logformat = textall
;use_locking = yes
;gammuloc = locfile
;startinfo = yes
;gammucoding = utf8

; Step 1. Please find required Connection parameter and look into assigned 
; with it device type. With some Connection you must set concrete model

; ================================================================ cables =====
; New Nokia protocol for FBUS/DAU9P
; Connection "fbus", device type serial
; New Nokia protocol for DLR3/DLR3P
; Connection "fbusdlr3"/"dlr3", device type serial 
; New Nokia protocol for DKU2 (and phone with USB converter on phone mainboard
; like 6230)
; Connection "dku2phonet"/"dku2", device type dku2 on Windows
; Connection "fbususb" on Linux
; New Nokia protocol for DKU5 (and phone without USB converter on phone
; mainboard like 5100)
; Connection "dku5fbus"/"dku5", device type dku5
; New Nokia protocol for PL2303 USB cable (and phone without USB converter
; on phone mainboard like 5100)
; Connection "fbuspl2303", device type usb
; Old Nokia protocol for MBUS/DAU9P
; Connection "mbus", device type serial
; Variants: 
; You can modify a bit behaviour of connection using additional flags
; specified just after connection name like connection-variant.
; If you're using ARK3116 cable (or any other which does not like dtr 
; handling), you might need -nodtr variant of connection, eg. dlr3-nodtr.
; If cable you use is not powered over DTR/RTS, try using -nopower variant of 
; connection, eg. fbus-nopower.
; -----------------------------------------------------------------------------
; AT commands for DLR3, DKU5 or other AT compatible cable (8 bits, None
; parity, no flow control, 1 stop bit). Used with Nokia, Alcatel, Siemens, etc.
; Connection "at19200"/"at115200"/.., device type serial
; AT commands for DKU2 cable
; Connection "dku2at", device type dku2
; ============================================================== infrared =====
; Nokia protocol for infrared with Nokia 6110/6130/6150
; Connection "fbusirda"/"infrared", device type serial
; Nokia protocol for infrared with other Nokia models
; Connection "irdaphonet"/"irda", device type irda
; -----------------------------------------------------------------------------
; AT commands for infrared. Used with Nokia, Alcatel, Siemens, etc.
; Connection "irdaat", device type irda
; -----------------------------------------------------------------------------
; OBEX for infrared
; Connection "irdaobex", device type irda.
; ============================================================= Bluetooth =====
; Nokia protocol with serial device set in BT stack (WidComm, other) from
; adequate service and Nokia 6210
; Connection "fbusblue", device type serial
; Nokia protocol with serial device set in BT stack (WidComm, other) from
; adequate service and other Nokia models
; Connection "phonetblue", device type serial
; -----------------------------------------------------------------------------
; Nokia protocol for Bluetooth stack with Nokia 6210
; Connection "bluerffbus", device type BT
; Nokia protocol for Bluetooth stack with DCT4 Nokia models, which don't inform
; about services correctly (6310, 6310i with firmware lower than 5.50, 8910,..)
; Connection "bluerfphonet", device type BT
; Nokia protocol for Bluetooth stack with other DCT4 Nokia models
; Connection "bluephonet", device type BT
; -----------------------------------------------------------------------------
; AT commands for Bluetooth stack and 6210 / DCT4 Nokia models, which don't
; inform about BT services correctly (6310, 6310i with firmware lower 
; than 5.50, 8910,..)
; Connection "bluerfat", device type BT
; AT commands for Bluetooth stack with other phones (Siemens, other Nokia,etc.)
; Connection "blueat", device type BT
; -----------------------------------------------------------------------------
; OBEX for Bluetooth stack with DCT4 Nokia models, which don't inform about
; BT services correctly (6310, 6310i with firmware lower than 5.50, 8910,...)
; Connection "bluerfobex", device type BT
; OBEX for Bluetooth stack with other phones (Siemens, other Nokia, etc.)
; Connection "blueobex", device type BT.
; -----------------------------------------------------------------------------
; Connection "bluerfgnapbus", device type BT, model "gnap"
; Connection "irdagnapbus", device type irda, model "gnap"

; Step2. According to device type from Step1 and used OS set Port parameter

; -----------------------------------------------------------------------------
; Port type | "Port" parameter in Windows/DOS | "Port" parameter in Linux/Unix
; ----------|---------------------------------|--------------------------------
; serial | "com*:" | "/dev/ttyS*"
; | (example "com1:") | (example "/dev/ttyS1")
; | | or "/dev/tts/**" (with DevFS)
; | | virtual serial ports like
; | | "/dev/ircomm*" or "/dev/rfcomm*"
; ----------|---------------------------------|--------------------------------
; irda | ignored (can be empty) | ignored (can be empty)
; ----------|---------------------------------|--------------------------------
; BT | Bluetooth device address (example "00:11:22:33:44:55").
; | Optionally you can also include channel after slash
; | (example "00:11:22:33:44:55/12"). Can be also empty.
; ----------|---------------------------------|--------------------------------
; dku2 | ignored (can be empty) | /dev/ttyUSB* or /dev/ttyACM*
; ----------|---------------------------------|--------------------------------
; dku5 | ignored (can be empty) | connection with it not possible
; ----------|---------------------------------|--------------------------------
; usb | connection with it not possible | "/dev/ttyUSB*"

; Step3. Set other config parameters

; -----------------------------------------------------------------------------
; Parameter name | Description
; ----------------|------------------------------------------------------------
; Model | Should not be used unless you have a good reason to do so.
; | If Gammu doesn't recognize your phone model, put it here. 
; | Example values: "6110", "6150", "6210", "8210"
; SynchronizeTime | if you want to set time from computer to phone during
; | starting connection. Do not rather use this option when
; | when to reset phone during connection (in some phones need
; | to set time again after restart)
; GammuLoc | name of localisation file
; StartInfo | this option allow to set, that you want (setting "yes")
; | to see message on the phone screen or phone should enable
; | light for a moment during starting connection. Phone
; | WON'T beep during starting connection with this option.
; GammuCoding | forces using specified codepage (in win32 - for example
; | "1250" will force CP1250) or UTF8 (in Linux - "utf8")
; ----------------|------------------------------------------------------------
; Logfile | Use, when want to have logfile from communication.
; Logformat | What debug info and format should be used:
; | "nothing" - no debug level (default)
; | "text" - transmission dump in text format
; | "textall" - all possible info in text format
; | "errors" - errors in text format
; | "binary" - transmission dump in binary format
; ----------------|------------------------------------------------------------
; Features | Custom features for phone. This can be used as override
; | when values coded in common/gsmphones.c are bad or
; | missing. Consult include/gammu-info.h for possible values
; | (all Feature values without leading F_ prefix).
; | Please report correct values to Gammu authors.
; ----------------|------------------------------------------------------------
; Use_Locking | under Unix/Linux use "yes", if want to lock used device
; | to prevent using it by other applications. In win32 ignored

; vim: et ts=4 sw=4 sts=4 tw=78 spell spelllang=en_us


==========================================
Install Kalkun
==========================================

Edit kalkun database settings on /var/www/kalkun/system/application/config/database.php

$db['default']['hostname'] = "localhost";
$db['default']['username'] = "username"; // change this
$db['default']['password'] = "password"; // change this
$db['default']['database'] = "kalkun";
$db['default']['dbdriver'] = "mysql";
Finally, launch up your browser and go to http://localhost/kalkun, you will see installation wizard there. That should be easy from here.

Now we try upgrade Kalkun 0.2.1 to Kalkun 0.2.9

1. Find and download the last update at http://kalkun.sourceforge.net/

2. Backup Kalkun v0.2.1 in /var/www/

#mv kalkun kalkun_backup

3. Rename id_pbk colomn to be ID from pbk table, I'm using phpmyadmin

4. Rename GroupName colomn to be Name from pbk_groups table, I'm using phpmyadmin

5. Ekstrak and move Kalkun v0.2.9 to /var/www

6. Change the database configuration in /application/config/database.php

7. Edit daemon.sh in scripts folder like this
#!/bin/sh

# Configure this (use absolute path)

PHP=/usr/bin/php # php cli path

DAEMON=/scripts/daemon.php # daemon.php path

# Execute

$PHP $DAEMON

8. Make sure the url Kalkun in the files /scripts/daemon.php

// Make sure it's run from CLI

if(php_sapi_name() != 'cli' && !empty($_SERVER['REMOTE_ADDR'])) exit("Access Denied."); 

// Please configure this

$url = "http://localhost/kalkun";

fclose(fopen($url."/index.php/daemon/message_routine/", "r"));

?>

9. Add runonreceive = /scripts/daemon.sh in file /etc/gammu-smsdrc part [smsd]

10. Restart gammu
#/etc/init.d/gammu-smsd restart

Repository Ubuntu 10.04 ITB

000jericho — Sat, 12 Mar 2011 06:26:07 GMT

deb ftp://ftp.itb.ac.id/pub/ubuntu lucid main restricted universe multiverse
deb ftp://ftp.itb.ac.id/pub/ubuntu lucid-security main restricted universe multiverse
deb ftp://ftp.itb.ac.id/pub/ubuntu lucid-updates main restricted universe multiverse
deb ftp://ftp.itb.ac.id/pub/ubuntu lucid-backports main restricted universe multiverse
deb ftp://ftp.itb.ac.id/pub/ubuntu lucid-proposed main restricted universe multiverse
deb-src ftp://ftp.itb.ac.id/pub/ubuntu lucid main restricted universe multiverse
deb-src ftp://ftp.itb.ac.id/pub/ubuntu lucid-security main restricted universe multiverse
deb-src ftp://ftp.itb.ac.id/pub/ubuntu lucid-updates main restricted universe multiverse
deb-src ftp://ftp.itb.ac.id/pub/ubuntu lucid-backports main restricted universe multiverse
deb-src ftp://ftp.itb.ac.id/pub/ubuntu lucid-proposed main restricted universe multiverse

VMware Workstation 7 on Ubuntu 10.04 LTS

000jericho — Mon, 08 Nov 2010 16:24:59 GMT

Recently I installed Ubuntu 10.04. When I want to install VMware Workstation 7 there is a slight problem. Here are the steps I did:

Start the installation
run a loop to kill the "vmware-modconfig-console" that hangs the installation.At this point installation finished, but running "vmware-modconfig --console –install-all” would generate an odd error for me when trying to do the vmnet compiling.

root@kecoak# vmware-modconfig --console --install-all
Stopping VMware services:
   VMware USB Arbitrator                                           done
   VM communication interface socket family                done
   Virtual machine communication interface                  done
   Virtual machine monitor                                          done
   Blocking file system                                                done
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make -C /lib/modules/2.6.32-25-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.32-25-generic'
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
/tmp/vmware-root/modules/vmmon-only/linux/hostif.c: In function ‘HostIFReadUptimeWork’:
/tmp/vmware-root/modules/vmmon-only/linux/hostif.c:1944: warning: ‘newUpBase’ may be used uninitialized in this function
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/iommu.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/comport.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/task.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC      /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-25-generic'
make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
Built vmmon module
make: *** /tmp/vmware-root/modules/vmnet-only: No such file or directory. Stop.
Unable to install vmnet
root@kecoak#

then just did the following manually:

1. tar xvf /usr/lib/vmware/modules/source/vmnet.tar -C /tmp

root@kecoak# tar xvf /usr/lib/vmware/modules/source/vmnet.tar -C /tmp
tmp/vmnet-only/
tmp/vmnet-only/procfs.c
tmp/vmnet-only/vm_basic_asm_x86.h
tmp/vmnet-only/vnetUserListener.c
tmp/vmnet-only/Makefile.kernel
tmp/vmnet-only/compat_module.h
tmp/vmnet-only/vm_oui.h
tmp/vmnet-only/COPYING
tmp/vmnet-only/netdev_has_net.c
tmp/vmnet-only/vnetFilter.h
tmp/vmnet-only/pgtbl.h
tmp/vmnet-only/compat_slab.h
tmp/vmnet-only/compat_skbuff.h
tmp/vmnet-only/vm_atomic.h
tmp/vmnet-only/vm_basic_defs.h
tmp/vmnet-only/includeCheck.h
tmp/vmnet-only/compat_netdevice.h
tmp/vmnet-only/filter.c
tmp/vmnet-only/compat_highmem.h
tmp/vmnet-only/vnetInt.h
tmp/vmnet-only/compat_mm.h
tmp/vmnet-only/compat_pgtable.h
tmp/vmnet-only/compat_file.h
tmp/vmnet-only/compat_sock.h
tmp/vmnet-only/vmnetInt.h
tmp/vmnet-only/vnetKernel.h
tmp/vmnet-only/smac.h
tmp/vmnet-only/vnetEvent.h
tmp/vmnet-only/vm_device_version.h
tmp/vmnet-only/netdev_has_dev_net.c
tmp/vmnet-only/compat_uaccess.h
tmp/vmnet-only/vnet.h
tmp/vmnet-only/bridge.c
tmp/vmnet-only/vnetFilterInt.h
tmp/vmnet-only/driver-config.h
tmp/vmnet-only/vnetEvent.c
tmp/vmnet-only/vmware_pack_init.h
tmp/vmnet-only/setnice.c
tmp/vmnet-only/Makefile
tmp/vmnet-only/smac_compat.c
tmp/vmnet-only/net.h
tmp/vmnet-only/Makefile.normal
tmp/vmnet-only/compat_semaphore.h
tmp/vmnet-only/smac_compat.h
tmp/vmnet-only/geninclude.c
tmp/vmnet-only/userif.c
tmp/vmnet-only/vm_basic_types.h
tmp/vmnet-only/vm_basic_asm.h
tmp/vmnet-only/compat_kdev_t.h
tmp/vmnet-only/vmware_pack_begin.h
tmp/vmnet-only/compat_spinlock.h
tmp/vmnet-only/epoll.c
tmp/vmnet-only/driver.c
tmp/vmnet-only/compat_version.h
tmp/vmnet-only/compat_page.h
tmp/vmnet-only/hub.c
tmp/vmnet-only/smac.c
tmp/vmnet-only/vmware_pack_end.h
tmp/vmnet-only/compat_sched.h
tmp/vmnet-only/x86cpuid.h
tmp/vmnet-only/sk_alloc.c
tmp/vmnet-only/nfhook_uses_skb.c
tmp/vmnet-only/skblin.c
tmp/vmnet-only/netif.c
tmp/vmnet-only/vm_basic_asm_x86_64.h
tmp/vmnet-only/compat_wait.h

2. tar xvf /usr/lib/vmware/modules/source/vmci.tar -C /tmp

root@kecoak# tar xvf /usr/lib/vmware/modules/source/vmci.tar -C /tmp
tmp/vmci-only/
tmp/vmci-only/Makefile.kernel
tmp/vmci-only/autoconf/
tmp/vmci-only/autoconf/geninclude.c
tmp/vmci-only/autoconf/epoll.c
tmp/vmci-only/linux/
tmp/vmci-only/linux/driverLog.h
tmp/vmci-only/linux/vmciKernelIf.c
tmp/vmci-only/linux/driver.c
tmp/vmci-only/linux/driverLog.c
tmp/vmci-only/COPYING
tmp/vmci-only/common/
tmp/vmci-only/common/vmciDatagram.c
tmp/vmci-only/common/vmciResource.h
tmp/vmci-only/common/vmciDatagram.h
tmp/vmci-only/common/vmciContext.h
tmp/vmci-only/common/vmciDriver.h
tmp/vmci-only/common/vmciEvent.c
tmp/vmci-only/common/vmciProcess.c
tmp/vmci-only/common/vmciQueuePair.c
tmp/vmci-only/common/vmciGroup.c
tmp/vmci-only/common/vmciDsInt.h
tmp/vmci-only/common/vmciQueuePair.h
tmp/vmci-only/common/vmciGroup.h
tmp/vmci-only/common/vmciDriver.c
tmp/vmci-only/common/vmciContext.c
tmp/vmci-only/common/vmciDs.c
tmp/vmci-only/common/vmciProcess.h
tmp/vmci-only/common/vmciResource.c
tmp/vmci-only/common/vmciEvent.h
tmp/vmci-only/common/vmciHashtable.h
tmp/vmci-only/common/vmciHashtable.c
tmp/vmci-only/common/vmciCommonInt.h
tmp/vmci-only/Makefile
tmp/vmci-only/Makefile.normal
tmp/vmci-only/include/
tmp/vmci-only/include/vmciHostKernelAPI.h
tmp/vmci-only/include/circList.h
tmp/vmci-only/include/vmware.h
tmp/vmci-only/include/compat_module.h
tmp/vmci-only/include/vmci_call_defs.h
tmp/vmci-only/include/vmci_iocontrols.h
tmp/vmci-only/include/pgtbl.h
tmp/vmci-only/include/compat_slab.h
tmp/vmci-only/include/vm_atomic.h
tmp/vmci-only/include/vm_basic_defs.h
tmp/vmci-only/include/vmci_kernel_if.h
tmp/vmci-only/include/includeCheck.h
tmp/vmci-only/include/compat_highmem.h
tmp/vmci-only/include/compat_mm.h
tmp/vmci-only/include/compat_pgtable.h
tmp/vmci-only/include/vmci_defs.h
tmp/vmci-only/include/compat_file.h
tmp/vmci-only/include/vm_assert.h
tmp/vmci-only/include/vm_device_version.h
tmp/vmci-only/include/compat_uaccess.h
tmp/vmci-only/include/compat_interrupt.h
tmp/vmci-only/include/driver-config.h
tmp/vmci-only/include/compat_kernel.h
tmp/vmci-only/include/vmware_pack_init.h
tmp/vmci-only/include/vmci_handle_array.h
tmp/vmci-only/include/compat_semaphore.h
tmp/vmci-only/include/vm_basic_types.h
tmp/vmci-only/include/vmware_pack_begin.h
tmp/vmci-only/include/compat_spinlock.h
tmp/vmci-only/include/compat_version.h
tmp/vmci-only/include/compat_page.h
tmp/vmci-only/include/vmware_pack_end.h
tmp/vmci-only/include/compat_sched.h
tmp/vmci-only/include/compat_wait.h
tmp/vmci-only/include/vmci_queue_pair.h

tmp/vmci-only/include/vmci_infrastructure.h

3. cd /tmp
4. vi both "vmnet-only/vnetUserListener.c” and "vmci-only/include/pgtbl.h” adding #include "compat_sched.h" to both files.
5. tar cvf /usr/lib/vmware/modules/source/vmnet.tar /tmp/vmnet-only
6. tar cvf /usr/lib/vmware/modules/source/vmci.tar /tmp/vmci-only

WHILE THE COMPILE WAS PAUSED (ctrl-z).

root@kecoak# cp -pr /tmp/vm{ci,net}-only /tmp/vmware-root/modules/

root@kecoak# fg
vmware-modconfig --console --install-all
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
/tmp/vmware-root/modules/vmmon-only/linux/hostif.c: In function ‘HostIFReadUptimeWork’:
/tmp/vmware-root/modules/vmmon-only/linux/hostif.c:1944: warning: ‘newUpBase’ may be used uninitialized in this function
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/iommu.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/comport.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/task.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC      /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-25-generic'
make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
Built vmmon module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make -C /lib/modules/2.6.32-25-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.32-25-generic'
CC [M] /tmp/vmware-root/modules/vmnet-only/driver.o
CC [M] /tmp/vmware-root/modules/vmnet-only/hub.o
CC [M] /tmp/vmware-root/modules/vmnet-only/userif.o
CC [M] /tmp/vmware-root/modules/vmnet-only/netif.o
CC [M] /tmp/vmware-root/modules/vmnet-only/bridge.o
CC [M] /tmp/vmware-root/modules/vmnet-only/filter.o
CC [M] /tmp/vmware-root/modules/vmnet-only/procfs.o
CC [M] /tmp/vmware-root/modules/vmnet-only/smac_compat.o
CC [M] /tmp/vmware-root/modules/vmnet-only/smac.o
CC [M] /tmp/vmware-root/modules/vmnet-only/vnetEvent.o
CC [M] /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o
LD [M] /tmp/vmware-root/modules/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC      /tmp/vmware-root/modules/vmnet-only/vmnet.mod.o
LD [M] /tmp/vmware-root/modules/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-25-generic'
make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
Built vmnet module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make -C /lib/modules/2.6.32-25-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.32-25-generic'
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/block.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/control.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dentry.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/file.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/inode.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/module.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/stubs.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/super.o
LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST 1 modules
CC      /tmp/vmware-root/modules/vmblock-only/vmblock.mod.o
LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-25-generic'
make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
Built vmblock module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/2.6.32-25-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.32-25-generic'
CC [M] /tmp/vmware-root/modules/vmci-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmci-only/linux/driverLog.o
CC [M] /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDs.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciGroup.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciProcess.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC      /tmp/vmware-root/modules/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-25-generic'
make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Built vmci module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vsock-only'
make -C /lib/modules/2.6.32-25-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.32-25-generic'
CC [M] /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o
/tmp/vmware-root/modules/vsock-only/linux/af_vsock.c:359: warning: initialization from incompatible pointer type
CC [M] /tmp/vmware-root/modules/vsock-only/linux/notify.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/stats.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/util.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.o
CC [M] /tmp/vmware-root/modules/vsock-only/driverLog.o
LD [M] /tmp/vmware-root/modules/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC      /tmp/vmware-root/modules/vsock-only/vsock.mod.o
LD [M] /tmp/vmware-root/modules/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-25-generic'
make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-root/modules/vsock-only'
Built vsock module
Starting VMware services:
   VMware USB Arbitrator                                         done
   Virtual machine monitor                                        done
   Virtual machine communication interface                done
   VM communication interface socket family              done
   Blocking file system                                              done
   Virtual ethernet                                                    done
   Shared Memory Available                                   done

root@kecoak#

SUCCESS..

Asia Computational Material Design Workshop

000jericho — Thu, 08 Jul 2010 10:15:08 GMT

We are pleased to inform you that the Computational Material Design and Quantum Engineering Laboratory, Research Group of Engineering Physics, Faculty of Industrial Technology, Institute of Technology Bandung (ITB), in cooperation with the Kasai Laboratory of the Osaka University will organize 2nd Asia Computational Materials Design Workshop. This workshop will provide lectures of leading-edge researches in Computational Materials Design (CMD) Science and hands-on practical training of the quantum simulation. The invited speakers are the top experts in this field.

Computational materials design is a computational approach aimed at developing new materials with specified properties and functionalities. The basic ingredient is the use of quantum simulations to solve the materials science problems in order to design a material that suits this specification. CMD has the high potentiality to impact the real industrial research and development.

Although the subject covered in this workshop is advance nevertheless we will present it to you step by step. The workshop will be started with the overview of possible roles of CMD in Indonesia, some CMD applications, CMD in surface interactions and nano-spintronics, and followed by the development of quantum simulators. For this workshop we purposefully choose Machikaneyama 2000 for the hands on experience of CMD. Machikaneyama 2000 is an open source application, a sophisticated KKR-CPA-LDA ab initio electronic structure calculation code, which has been developed by Prof. Hisazumi Akai in Osaka University. Prof. Akai will give an introductory lecture on the DFT calculations with the Machikaneyama. On quantum molecular dynamics simulation the workshop will discuss State-Senri code. Another CMD advanced case study in this workshop will be on Naniwa 2001, a quantum calculation code for atomic motion.

We are looking forward to seeing you in the campus of Institute of Technology Bandung. You will also find pleasant places to see and enjoy recreation around the city of Bandung.

The workshop will provide hands-on experience on quantum simulation. We chose to use an open source application so that the participants can easily develop for their own purposes without an extra spending on application softwares. Although there is no computational language knowledge requirements, understanding any of it, preferably fortran or C and Java, will be useful. The lecture, practice, and tutorial will be given by the experts from both ITB and Osaka University.

See for more information: http://cmdqe.tf.itb.ac.id/

URL Rewriting

000jericho — Fri, 09 Apr 2010 20:53:30 GMT

The Apache server’s mod_rewrite module gives you the ability to transparently redirect one URL to another, without the user’s knowledge. This opens up all sorts of possibilities, from simply redirecting old URLs to new addresses, to cleaning up the ‘dirty’ URLs coming from a poor publishing system — giving you URLs that are friendlier to both readers and search engines.

An Introduction to Rewriting

Readable URLs are nice. A well designed website will have a logical file system layout, with smart folder and file names, and as many implementation details left out as possible. In the most well designed sites, readers can guess at filenames with a high level of success.

However, there are some cases when the best possible information design can’t stop your site’s URLs from being nigh-on impossible to use. For instance, you may be using a Content Management System that serves out URLs that look something like

http://www.example.com/viewcatalog.asp?category=hats&prodID=53

This is a horrible URL, but it and its brethren are becoming increasingly prevalent in these days of dynamically-generated pages. There are a number of problems with an URL of this kind:

It exposes the underlying technology of the website (in this case ASP). This can give potential hackers clues as to what type of data they should send along with the query string to perform a ‘front-door’ attack on the site. Information like this shouldn’t be given away if you can help it.

Even if you’re not overly concerned with the security of your site, the technology you’re using is at best irrelevant — and at worst a source of confusion — to your readers, so it should be hidden from them if possible.

Also, if at some point in the future you decide to change the language that your site is based on (to » PHP, for instance); all your old URLs will stop working. This is a pretty serious problem, as anyone who has tackled a full-on site rewrite will attest.
The URL is littered with awkward punctuation, like the question mark and ampersand. Those & characters, in particular, are problematic because if another webmaster links to this page using that URL, the un-escaped ampersands will mess up their XHTML conformance. They will have to laboriously replace all the ampersands with & character entities, which is often forgotten.
Some search engines won’t index pages which they think are generated dynamically. They’ll see that question mark in the URL and just turn their asses around.

Luckily, using rewriting, we can clean up this URL to something far more manageable. For example, we could map it to

http://www.example.com/catalog/hats/53/

Much better. This URL is more logical, readable and memorable, and will be picked up by all search engines. The faux-directories are short and descriptive. Importantly, it looks more permanent.

To use mod_rewrite, you supply it with the link text you want the server to match, and the real URLs that these URLs will be redirected to. The URLs to be matched can be straight file addresses, which will match one file, or they can be regular expressions, which will match many files.

Basic Rewritng

Some servers will not have » mod_rewrite enabled by default. As long as the » module is present in the installation, you can enable it simply by starting a .htaccess file with the command

RewriteEngine on

Put this .htaccess file in your root so that rewriting is enabled throughout your site. You only need to write this line once per .htaccess file.

Basic Redirects

We’ll start off with a straight redirect; as if you had moved a file to a new location and want all links to the old location to be forwarded to the new location. Though you shouldn’t really ever » move a file once it has been placed on the web; at least when you simply have to, you can do your best to stop any old links from breaking.

RewriteEngine on

RewriteRule ^old\.html$
 new.html

Though this is the simplest example possible, it may throw a few people off. The structure of the ‘old’ URL is the only difficult part in this RewriteRule. There are three special characters in there.

The caret, ^, signifies the start of an URL, under the current directory. This directory is whatever directory the .htaccess file is in. You’ll start almost all matches with a caret.
The dollar sign, $, signifies the end of the string to be matched. You should add this in to stop your rules matching the first part of longer URLs.
The period or dot before the file extension is a special character in regular expressions, and would mean something special if we didn’t escape it with the backslash, which tells Apache to treat it as a normal character.

So, this rule will make your server transparently redirect from old.html to the new.html page. Your reader will have no idea that it happened, and it’s pretty much instantaneous.

Forcing New Requests

Sometimes you do want your readers to know a redirect has occurred, and can do this by forcing a new HTTP request for the new page. This will make the browser load up the new page as if it was the page originally requested, and the location bar will change to show the URL of the new page. All you need to do is turn on the [R] flag, by appending it to the rule:

RewriteRule ^old\.html$ new.html [R]

Using Regular Expressions

Now we get on to the really useful stuff. The power of mod_rewrite comes at the expense of complexity. If this is your first encounter with regular expressions, you may find them to be a tough nut to crack, but the options they afford you are well worth the slog. I’ll be providing plenty of examples to guide you through the basics here.

Using regular expressions you can have your rules matching a set of URLs at a time, and mass-redirect them to their actual pages. Take this rule;

RewriteRule ^products/([0-9][0-9])/$
 /productinfo.php?prodID=$1

This will match any URLs that start with ‘products/’, followed by any two digits, followed by a forward slash. For example, this rule will match an URL like products/12/ or products/99/, and redirect it to the PHP page.

The parts in square brackets are called ranges. In this case we’re allowing anything in the range 0-9, which is any digit. Other ranges would be [A-Z], which is any uppercase letter; [a-z], any lowercase letter; and [A-Za-z], any letter in either case.

We have encased the regular expression part of the URL in parentheses, because we want to store whatever value was found here for later use. In this case we’re sending this value to a PHP page as an argument. Once we have a value in parentheses we can use it through what’s called a back-reference. Each of the parts you’ve placed in parentheses are given an index, starting with one. So, the first back-reference is $1, the third is $3 etc.

Thus, once the redirect is done, the page loaded in the readers’ browser will be something like productinfo.php?prodID=12 or something similar. Of course, we’re keeping this true URL secret from the reader, because it likely ain’t the prettiest thing they’ll see all day.

Multiple Redirects

If your site visitor had entered something like products/12, the rule above won’t do a redirect, as the slash at the end is missing. To promote good URL writing, we’ll take care of this by doing a direct redirect to the same URL with the slash appended.

RewriteRule ^products/([0-9][0-9])$ /products/$1/ [R]

Multiple redirects in the same .htaccess file can be applied in sequence, which is what we’re doing here. This rule is added before the one we did above, like so:

RewriteRule ^products/([0-9][0-9])$ /products/$1/ [R] RewriteRule ^products/([0-9][0-9])/$ /productinfo.php?prodID=$1

Thus, if the user types in the URL products/12, our first rule kicks in, rewriting the URL to include the trailing slash, and doing a new request for products/12/ so the user can see that we likes our trailing slashes around here. Then the second rule has something to match, and transparently redirects this URL to productinfo.php?prodID=12. Slick.

Match Modifiers

You can expand your regular expression patterns by adding some modifier characters, which allow you to match URLs with an indefinite number of characters. In our examples above, we were only allowing two numbers after products. This isn’t the most expandable solution, as if the shop ever grew beyond these initial confines of 99 products and created the URL productinfo.php?prodID=100, our rules would cease to match this URL.

So, instead of hard-coding a set number of digits to look for, we’ll work in some room to grow by allowing any number of characters to be entered. The rule below does just that:

RewriteRule ^products/([0-9]+)$ /products/$1/ [R]

Note the plus sign (+) that has snuck in there. This modifier changes whatever comes directly before it, by saying ‘one or more of the preceding character or range.’ In this case it means that the rule will match any URL that starts with products/ and ends with at least one digit. So this’ll match both products/1 and products/1000.

Other match modifiers that can be used in the same way are the asterisk, *, which means ‘zero or more of the preceding character or range’, and the question mark, ?, which means ‘zero or only one of the preceding character or range.’

Adding Guessable URLs

Using these simple commands you can set up a slew of ‘shortcut URLs’ that you think visitors will likely try to enter to get to pages they know exist on your site. For example, I’d imagine a lot of visitors try jumping straight into our stylesheets section by typing the URL http://www.yourhtmlsource.com/css/. We can catch these cases, and hopefully alert the reader to the correct address by updating their location bar once the redirect is done with these lines:

RewriteRule ^css(/)?$ /stylesheets/ [R]

The simple regular expression in this rule allows it to match the css URL with or without a trailing slash. The question mark means ‘zero or one of the preceding character or range’ — in other words either yourhtmlsource.com/css or yourhtmlsource.com/css/ will both be taken care of by this one rule.

This approach means less confusing 404 errors for your readers, and a site that seems to run a whole lot smoother all ’round.

Source : http://www.yourhtmlsource.com/sitemanagement/urlrewriting.html

Incoming and Outgoing Mail Server Settings for Hotmail, Yahoo! Mail, GMail, MSN, AOL and more

000jericho — Thu, 11 Mar 2010 18:37:25 GMT

# Hotmail Settings

As other web based email services, Hotmail is using the HTTP protocol for connecting you to your mailbox. If you want to send and receive Hotmail emails using an email client software, then your software must support Hotmail HTTP access for your email account. Some email clients, such as Outlook Express or Microsoft Outlook, offer builtin support for Hotmail accounts, so you only have to select HTTP when you are asked to select your email account type and select Hotmail as the HTTP Mail Service Provider.

Mail Server Settings for Hotmail using the Microsoft Outlook Connector

If you are using Microsoft Outlook & the Outlook Connector, you can define your Hotmail account just like any regular POP3 email account:

      Hotmail Incoming Mail Server (POP3) - pop3.live.com (logon using Secure Password Authentification - SPA, mail server port: 995)

      Hotmail Outgoing Mail Server (SMTP) - smtp.live.com (SSL enabled, port 25)

# Yahoo! Mail Settings

Yahoo Mail offers standard POP3 access for receiving emails incoming through your Yahoo mailbox, by using your favorite email client software. To setup your email client for working with your Yahoo account, you need to select the POP3 protocol and use the following mail server settings:

      Yahoo Incoming Mail Server (POP3) - pop.mail.yahoo.com (port 110)

      Yahoo Outgoing Mail Server (SMTP) - smtp.mail.yahoo.com (port 25)

POP Yahoo! Mail Plus email server settings

      Yahoo Plus Incoming Mail Server (POP3) - plus.pop.mail.yahoo.com (SSL enabled, port 995)

      Yahoo Plus Outgoing Mail Server (SMTP) - plus.smtp.mail.yahoo.com (SSL enabled, port 465, use authentication)

# Google GMail Settings

The Google GMail service offers email client access for retrieving and sending emails through your Gmail account. However, for security reasons, GMail uses POP3 over an SSL connection, so make sure your email client supports encrypted SSL connections.

      Google Gmail Incoming Mail Server (POP3) - pop.gmail.com (SSL enabled, port 995)

      Outgoing Mail Server - use the SMTP mail server address provided by your local ISP or smtp.gmail.com (SSL enabled, port 465)

# MSN Mail Settings

The MSN email service allows you to use the MSN POP3 and SMTP servers to access your MSN mailbox.

      MSN Incoming Mail Server (POP3) - pop3.email.msn.com (port 110, using Secure Password Authentication - SPA)

      MSN Outgoing Mail Server - smtp.email.msn.com (select "My outgoing server requires authentication")

# Lycos Mail Settings

The Lycos Mail Plus service allows you to use POP3 and SMTP servers for accessing your Lycos mailbox.

      Lycos Mail Incoming Mail Server (POP3) - pop.mail.lycos.com (port 110)

      Outgoing Mail Server - smtp.mail.lycos.com or use your local ISP SMTP mail server

# AOL Mail Settings

The AOL email service is a web based system, designed for managing your AOL mailbox via HTTP IMAP access. Unlike Hotmail, you can use any email client to access your AOL mailbox, as long as it supports the IMAP protocol.

      AOL Incoming Mail Server (IMAP) - imap.aol.com (port 143)

      AOL Outgoing Mail Server - smtp.aol.com or use your local ISP SMTP mail server

# Mail.com Mail Settings

The Mail.com email service allows you to use POP3 and SMTP servers for accessing your Mail.com mailbox.

      Mail.com Mail Incoming Mail Server (POP3) - pop1.mail.com (port 110)

      Outgoing Mail Server - use your local ISP SMTP mail server

# Netscape Internet Service Mail Settings

The Netscape e-mail system is web-based, which means you can access their e-mail from any Internet connection. Netscape Internet Service also supports AOL® Communicator, Microsoft® Outlook, Microsoft® Outlook Express, and other POP3 e-mail software. The outgoing mail server needs SSL support, so make sure your email client software supports SSL connections over the SMTP protocol.

      Netscape Internet Service Incoming Mail Server (POP3) - pop.3.isp.netscape.com (port 110)

      Netscape Internet Service Outgoing Mail Server - smtp.isp.netscape.com (port 25, using a secure SSL connection)

# Tiscali Mail Settings

The Tiscali email service allows you to use POP3 and SMTP servers for accessing your Tiscali mailbox.

      Tiscali Incoming Mail Server (POP3) - pop.tiscali.com (port 110)

      Outgoing Mail Server - use your local ISP SMTP mail server

# Freeserve Mail Settings

The Freeserve email service allows you to use POP3 and SMTP servers for accessing your Freeserve mailbox.

      Freeserve Incoming Mail Server (POP3) - pop.freeserve.com (port 110)

      Outgoing Mail Server - use your local ISP SMTP mail server

# Supanet Mail Settings

The Supanet email service allows you to use POP3 and SMTP servers for accessing your Supanet mailbox.

      Supanet Incoming Mail Server (POP3) - pop.supanet.com (port 110)

      Outgoing Mail Server - use your local ISP SMTP mail server

Using adept apt-get

000jericho — Mon, 01 Mar 2010 11:30:29 GMT

Setting the http_proxy variable

Here's how you set the variable:

bash$ export http_proxy=http://proxy:8080

If you're required to use your username and password for your proxy, they can be specified this way. Obviously, port 8080 can and should be replaced with the valid port for your proxy server (sometimes it's 3128):

bash$ export http_proxy=http://username:password@proxy:8080

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

Using adept apt-get behind proxy

Create or edit /etc/apt/apt.conf

Acquire::http::Proxy "http://[[user:password]@]proxy:port”;

Sometimes you don’t need [user:password]. Just type:

Acquire::http::Proxy "http://proxy:port"