Objectives

Late post is late.

Anyway, I need to set some objectives for this week.
 - Complete the Introduction part
 - Read one article a day
 - Consult with Sir Ludwig
 - Revise proposal
 - Install Squid Server

Bibliography

Creation of this post has been long overdue.

Anyways, this is a post to dump list all of my references I have read or used, or those that I have found helpful.
Also those stuff that I may find useful.
Only references found at the Internet are listed here.

Squid log parser references:

Security considerations with Squid proxy server
   - http://www.sans.org/reading_room/whitepapers/policyissues/security-considerations-squid-proxy-server_1048

Overview of proxy server caching
   - http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.edge.doc/cp/admingd24.htm

SUSE LINUX - Administration Guide
   - http://www.novell.com/documentation/suse91/suselinux-adminguide/html/ch18s03.html

How to Use Squid Proxy Cache Server to Control Internet Access
   - http://www.thegeekstuff.com/2010/09/squid-control-internet-access/

Webpage classifier references:

Web page classification - Features and algorithms
   - http://dl.acm.org/citation.cfm?doid=1459352.1459357 OR http://www.cse.lehigh.edu/~brian/pubs/2007/classification-survey/

System and Method for Targeted Ad Delivery
   - http://www.google.com/patents/about?id=t4KhAAAAEBAJ

Dividing the Haystack: Web Page Classification
   - http://janulrich.org/web/

HTML Parser - A Java Library
   - http://htmlparser.sourceforge.net/

Confirmation

With confirmation from Sir Jach, Sir Ludwig and my inner gut, I have finally decided on that extension that Sir Jach approved of last week: a webpage classifier.

So right now, my (tentative) title for my SP is:
Squidler - A Squid Log Parser with Webpage Classifier

.. Okay, Squidler may be kind of lame. It's subject to further scrutinization.
It's from the words "Squid" and "crawler" (web crawler).
As for the implementation, I am leaning more on a web-based one.

What I visualize for this SP is that it shows the different IP addresses connected at the proxy server, and it shows the different information about their connections (the websites they have visited and when they accessed them, how long they have accessed the internet, bandwidth consumed, etc) .

Afterwards, it classifies the webpages they have visited, and stores that information for later arrangement.
I have found a lot of papers that deals with webpage classification, and Sir Jach advised me to find something "unique" for my implementation.

Well, here goes nothing. I will pursue this one problem.

Simple Progress

Or perhaps, time-pressured progress?

Anyhows, my adviser has now accepted two of my proposed extensions.
One is an IP Spoofing Detection and DoS Prevention System.
The other is a Webpage Identifier (or Web Crawler, as Sir Ludwig had said).

Looking back at it now, that first proposal of mine was a bit abrupt.
Hopefully I won't choke on my own words.

Now it's time to make a decision. And make some introductions.
The clock is ticking.

Progress Report

Not much progress.
I still plan on pursuing that spoofing detection as my extension.
I have read some literature works about the different kinds of spoofing attacks, and for this week, I will research on spoofing attacks that could attack proxy servers, as well as how proxy servers work in general.

If such an extension is impossible in the context of proxy servers, though..
It seems I need to research on this matter as well.

Goals this week:
 - Research on different kinds of spoofing attacks
 - Research if a spoofing attack is possible on proxy servers, and if a similar SP exists
 - Create a working title