GSoC 2011 - Implement RFC 6056

[Juraj <duri.strecha%gmail.com@localhost>]

Hello, my name is Juraj Strecha. I'm a 2nd year student of the
Information Technologies bachelor degree program on The University of
Technology in Brno, Czech Republic. I'd like to participate in the GSoC
project this year. This is my first attempt to contribute to the open
source community.

The goal of my GSoC project is to implement source port randomization
algorithms included in RFC 6056 to NetBSD. Once this is done, it
improves security level of the system and lessers the chance of a
successful network attack.

As a result of my work, NetBSD will obtain source code of modified
algorithms mentioned in RFC 6056 and short documentation including some
of the implementation details. I will devote coding my tasks not less
than 40 hours/week as recommended. I fully understand, that this is a
full-time job. I will also set up a blog or wiki page to post updates
and my progress during the whole project.

Here is the schedule of my project:
24.05. - 07.06.   Reading RFCs, prioritizing algorithms, getting
familiar with using them in other systems, summarizing a whole project
plan, discuss my ideas with the mentor
08.06. - 06.07.   Implementing various algorithms + continuous basic
testing of the implementation, writing a short documentation for each
implemented method, asking the mentor for hints
07.07. - 15.07.   Completing in-process algorithms before mid-term
evaluations, discussing its functionality with mentor
16.07. - 17.07.   After-mid-term holiday :)
18.07. - 15.08.   Continue implementing remaining algorithms, continuous
testing of each part, writing the documentation
16.08. - 22.08.   Deeper testing
23.08. - 25.08.   Submitting the final evaluation to Google

Similar algorithms are used in FreeBSD, OpenBSD and Linux, which will be
the part of my information source.

I have not installed or tried NetBSD yet, but I mostly use Linux based
system on my laptop. Of course, after my application is accepted, I will
compile NetBSD and get to know its enviroment.

As this is the part of the kernel space, functionality and effectivity
are the key elements of this project. My implementation will be guided
by both RFCs and other platform source codes.

connect function also uses <sys/types.h> and <sys/socket.h> headers for
its functionality, so I will have to deeply study these and other
libraries for completing my task. I don't know which additional
libraries will be included in the project yet. I'm attending Networking
and Communication course this semester, so I will know many basic
principles from this area soon.

During my studies, I worked with socket-operating functions for
establishing socket communication using socket API. There were one-man
projects. Console application gives you information (last-modified date
and time, server name...) about web-content object you ask for in form
of command line parameters.
Next was focused on client-server solution requesting Postal codes of
cities given on client-side command line. Codes are stored on server
side in a file, both sides (client and server) established TCP
connection and request from client was sent to server program, which
tries to look for corresponding Postal code. Currently I'm working on
program, which models RTP protocol using UDP. All programs were
optimized for FreeBSD and written in C and C++ languages.
The non-network project that I've been involved in is a 5-man team
project to create a education-purpose interpreter for a Basic-derived
language. My task was to code sorting and searching algorithms used for
in-built functions, write binary tree functions and create a set of
tests to verify correct functionality.
Last year I practised the inter-process communication by solving the
Dining philosophers problem in C language.

If You have any additional questions, feel free to contact me through
this e-mail address, or Skype: duri-pb chat.

Thank You for reading my application and I'm looking forward to hearing
from You soon!

Yours sincerely
-- 

S pozdravom Juraj Strecha
FIT VUT Brno
2 BIT