Weekly Plan Chih-Wei Jan

Research plan 2004/01~2004/06 01/0501/1902/0202/1603/0103/1503/2904/1204/2605/1005/2406/0706/21 New arch development New arch benchmark Thesis writing

Weekly plan 04/01/05~04/01/09 Last week:  determine the final tables and diagrams of benchmark  Thesis writing final-term This week:  Presentation in group meeting  Consider new architecture Notes  The main work of this week is to do the remaining test of internal benchmark. For the new arch, I will find out how to link C and Perl program.

Weekly plan(2/2 ~ 2/8) This week  Make snort as a shared library  考預官

Weekly plan(2/9 ~ 2/15) Last week  Make snort as a shared library  考預官 This week  Strip snort Notes  I have surveyed the process of making a shared library. The process is quite simple. Next phase, I will try to strip preprocessors, detection-plug-ins and output-plug-ins of snort.

Weekly plan (2/16 ~ 2/22) Last week  Strip snort This week  Compile snort Notes  After I stripped snort, I realized that it is more difficult to compile whole snort project than to strip it. The original Makefile is too complicated. I would try to write my own Makefile.

Weekly plan (2/23 ~ 2/29) Last week  Compile snort This week  Test snort lib Notes  After I compiled snort as a shared lib, I would like to do some tests of snort lib. Filling the data structure of Packet, for example, is one of the tests to figure out the influence of string matching in snort.

Weekly plan (3/1 ~ 3/7) Last week  Test snort lib This week  Link webfd with snort Notes  As I said last week, there is a problem that an URL matched a signature, but snort generated no alerts. I will try to find out this problem and link webfd with snort lib.

Weekly plan (3/8 ~ 3/14) Last week  Link webfd with snort This week  Run clamav in daemon mode Notes  The webfd with snort is ready. This week, I will try to run clamav in daemon mode and to communicate with it.

Weekly plan (3/15 ~ 3/21) Last week  Run clamav in daemon mode This week  Chapter 1: Introduction  Use perl to communicate with clamav daemon Notes  Clamav daemon is ready. The protocol to communicate with it is simple. This week, I will use perl to do this and finish my chapter 1.

Weekly plan (3/22 ~ 3/28) Last week  Chapter 1: Introduction  Use perl to communicate with clamav daemon This week  Chapter 2: Background  Modify amavisd to communicate with clamav daemon Notes  Socket operation in perl is similar to the operation in C. The only we have to do is to find out how to pass return message to amavisd.

Weekly plan (3/29 ~ 4/4) Last week  Chapter 2: background  Modify amavisd to communicate with clamav daemon This week  Chapter 2:background  Mail relay in amavisd Notes  Chapter 2 will be finished in this week. The function of amavisd to communicate with clamav deamon is ready. I proceed with the mail relay in amavisd.

Weekly plan (4/5 ~ 4/11) Last week  Chapter 2: background  Mail relay in amavisd This week  Chapter 3: Integration  Mail relay in amavisd  Integration benchmark Notes  The modification of amavisd would finish this week. I will start to benchmark new system.

Weekly plan (4/12 ~ 4/18) Last week  Chapter 3: Integration  Mail relay in amavisd  Integration benchmark This week  Chapter 4: benchmark  Integration benchmark Notes  Integration benchmark would be my main work this week. In addition to write chapter4, I have to refine chapter 2 with new survey.

Weekly plan (4/19 ~ 4/25) Last week  Chapter 4: benchmark  Integration benchmark This week  Chapter 4:benchmark  Benchmark of the mail part Notes  Although integration of webfd with DansGuardian is not finished yet, I would start on the benchmark of the mail part.

Weekly plan (4/26 ~ 5/2) Last week  Chapter 4:benchamrk  Benchmark of the mail part This week  Benchmark of the mail part  Debugging of multi-thread amavisd Notes  There are problems in multi-thread amavisd. I would try to find out the problems and then start to benchmark.

Weekly plan (5/3 ~ 5/9) Last week  Benchmark of the mail part  Debugging of multi-thread amavisd This week  Benchmark of the mail part  Debugging of amavisd Notes  Although the problem of multi-thread in amavisd is solved, there is still problem of fork process in amavisd.

Weekly plan (5/24 ~ 5/30) Last week  Paper draft This week  Web results  References Notes  The remaining web results will be accomplish this week. The references will also be replenished.