A blog about computer science and a life between Heidelberg and Munich

During my studies of the Border Gateway Protocol I did the very same like every guy playing around with raw BGP data dumps, I used libbgpdump of RIPE NCC to get the binary data into a readable format. But the tool is not maintained that well and so sometimes errors still occur during parsing the BGP dumps. At least one of them is easy to solve within a few seconds.

Working and analysing BGP data always contains a bit of geographical knowledge. So I was in need of a geolocation database to look up certain IPs and different ranges and their location. This article is about creating such a small database and about how to get information out of it.

During a project at university I had to analyse raw RIS data dumps of the RIPE NCC. As BGP related stuff is a fairly advanced topic which is only used by computer scientists there are few tool around to work with those raw data dumps. This is why I’m publishing a small Bash snippet I wrote to create a non-binary data dump joining all the raw data files from RIPE NCC.

Most people do not know about some additional but rarely used headers about security issues. In this article I would like to give some hints to two of those unknown headers. They do not improve security a lot but clearly make it harder for common clickjacking to misuse your websites.

This semester has been a lot of work. At our university we did a pratica offered by the chair of IT Security which was about the setup and operation of honeypots. In fact it was more than just one single honeypot to work with - we had a whole subnet to play around. Summed up it was a honeynet with different teams owning several machines, offering various services and analyzing data on different layers. Because it was quite a lot of work I decided to share most of my stuff here. Maybe there is someone out there working on the same topic and in search for some experiences.

To have a nice, small repository to upload and track the development of your blog is a great thing. But it would be even greater if it is deployed automatically after every git pull command. This article describes the deployment of a Octopress based blog. But it’s easy to extend those instructions or even to rewrite them for working together with Jekyll or other static site generators.

If you’re using a remote repository like they are created from gitolite and similar software, there is a problem: we do need a local repository to do a rake generate. Otherwise Rake is not able to find his Rakefile.

Nowadays git is the Tool of choice when it comes to collaboration and source code management. But projects often need more than that: there are lists of features to implement, bug reports and patches to integrate in the source. So it is natural that there is another tool to manage all that stuff.

My projects are using gitolite and Redmine as Frontend to those repositories.

Redmine is currently not able to access other than local git repositories. This is quite a problem as Redmine is not able to browse through repositories within the local file-system. So there is no other way to mirror the repository. This can be done my a post-receive hook in gitolite. But first we have to create the mirror.