The research project has officially come to a close. I would like to thank my advisor, Dr. Melody Moh for providing guidance and direction when needed. I would also like to thank the various communities I have been able to bounce ideas off of about the project, and this includes not only fellow students and colleagues, but also various open source communities as well. I have learned a great deal about the research process, and look forward to a possible session of CREU again in the Fall.

The final report summarizes the project, and can be found on my web site at http://www.kizzobot.org, along with other supporting files.

A rough final draft of the report has been completed, and can be found here. I'll add my final touches in the coming week during finals, and the final version should be done by next weekend.

The time has come now to write the article. I have already sectioned off the report into discrete chunks that will be filled in later with information. I have begun filling in information and will continue to do so in phases. Lots of information will be added and a lot will be modified to enhance clarity and cohesion.

I have packaged up the CMake files that I have created for my work with the GNUnet framework, and have placed them on my website for download: http://www.kizzobot.org/ . These CMake files are for 0.8.1b version of the software.

To demonstrate how to make use of the CMake files, follow these instructions. First download the files you'll need: the GNUnet source distribution and the CMake project files. On Ubuntu, you can type "wget http://ftp.gnu.org/pub/gnu/gnunet/GNUnet-0.8.1b.tar.gz" to get the GNUnet code, and "wget http://kizzobot.org/GNUnet-0.8.1b-cmake.tar.bz2" to get the CMake files.

Then, extract the GNUnet source code with "tar xf GNUnet-0.8.1b.tar.gz" . Then extract the GNUnet CMake files to that directory you just extracted from the GNUnet tarball: "tar xf GNUnet-0.8.1b-cmake.tar.bz2 -C GNUnet-0.8.1b" .

Then you should be able to build GNUnet via CMake. Change to the GNUnet source directory and make a new directory where the generated build files from CMake will go: "cd GNUnet-0.8.1b; mkdir build" . Now, change into the build directory that you just created ("cd build") and run cmake to configure. When running cmake, you will need to specify the location of certain things to CMake so that it can proceed. There are only 2 that you must set yourself (GN_USER_HOME_DIR and GN_DAEMON_CONFIG_DIR). Some recommended values are as follows:

GN_USER_HOME_DIR: "/home/kizzo/GNUnet-work/userHome"
GN_DAEMON_CONFIG_DIR: "/home/kizzo/GNUnet-work"
GNUnet_LIBRARY_INSTALL_PATH: "lib/GNUnet"
GNUnet_BINARY_INSTALL_PATH: "bin"
GNUnet_INCLUDE_INSTALL_PATH: "include/GNUnet"
CMAKE_INSTALL_PREFIX: "/home/kizzo/GNUnet-work/install"
CMAKE_INSTALL_RPATH: "/home/kizzo/GNUnet-work/install/lib/GNUnet"

To set these options when running cmake from the build directory, one might use: "cmake .. -DCMAKE_INSTALL_RPATH=/home/kizzo/dsn/install/lib/GNUnet -DCMAKE_INSTALL_PREFIX=/home/kizzo/dsn/install -DGN_USER_HOME_DIR=/home/kizzo/dsn/userHome -DGN_DAEMON_CONFIG_DIR=/home/kizzo/dsn" . Options can be specified on the command line (as shown) or by editing the main CMakeLists.txt file by hand.

After executing this successfully, type "make" to build the libraries and binaries, and then run "make install" to install them to a directories specified by CMAKE_INSTALL_PREFIX .

I have thought about an end of semester timeline to formally close the project. It looks like there about 4 more weeks before the CREU official end date, and so I thought I should divide things in that way.

This week, from April 18 to April 24, I thought I should package up the CMake build files for easy use later. While my project was unsuccessful in providing a usable, secure, and privacy-preserving alternative, I have managed to contribute a small something that can be useful to someone.

Next week, from April 25 to May 1, I will plan out the project demo, which will showcase what work I have done for the project, and instructions for another developer to lead off on. I am not quite sure yet what I will demo, but this will be fleshed out soon enough - a lot of it will be gathered from journal logs.

The last two weeks, lasting from May 2 to May 15, will be used to write the academic report/article. I'm giving a lot of time to this because I would like for it to be complete.

I have begun writing the report for the project, summarizing my methods, results, and conclusions. It will be the first academic article I have written.

I've been spending more time getting the pseudonym list into an array of some sort, and then displaying that in the GUI, with success. It took a lot of weird guess and check work to get the gtk callbacks working, as I had to pass a bunch of widgets around, and I haven't done that much before, but I got used to it eventually.

The semester is coming to an end soon, and it may be likely that I won't be able to continue this project afterwards during the summer, so my advisor said I should probably start thinking about how to wrap things up. I will write an academic article detailing different aspects of the research (results, conclusion, etc.) for publication (my first, I think). I will also have to come up with a demo somehow, but I don't know how to make a good demo out of something that is not complete and does not work as intended, at all. I will think of something though. I was thinking also of packaging up the CMake project files for the GNUnet folks, in case they want them. More on that to come.