- About us
- Code of Conduct
- Google SoC
- Recent posts
- Security Workshops
In the first part of this two part blog post, the issue of anticipating retaliation during an aggressive battle to wrest control of a DDoS botnet was examined. In this part, the issues of dual standards, taking responsibility, and learning lessons to make positive change over time are examined.
Read full post here...
With winter in the northern hemisphere beginning to turn into spring, it is once again time to think about summer. And of course, for many open source organizations, that means Google Summer of Code (GSoC).
This blog post is the first of a two-part series in response to the Wired article of Oct 14, 2014, "How Microsoft Appointed Itself Sheriff of the Internet." [McM14] I find some problems with this article that raise questions about the depth of research into some elements of the story, and an appearance of bias in how "unintended consequences" are presented.
[McM14] Robert McMillan. How Microsoft Appointed Itself Sheriff of the Internet. http://www.wired.com/2014/10/microsoft-pinkerton/, October 2014.
A few months ago I read the paper "Technical analysis of client identification mechanisms" . The paper is really interesting and it is really worth investing your time and reading. Just a brief excerpt from the abstract:
Thug 0.6 was released just a few hours ago. The most important change introduced during the 0.5 branch was a complete redesign of the logging infrastructure which is now completely modular. This makes adding (or removing) new logging modules extremely easy.
Angelo, you have been HNP CEO for more than over a year now. What were your goals when you started and did you achieve them?
First of all let me confess that it seems really incredible to me that a year has already gone by. I took over the CEO position for the Honeynet Project from Christian Seifert more than a year ago and at times the role appeared quite intimidating to me. Christian and Honeynet Project founder Lance Spitzner did an awesome job of driving the organization
last week I published kippo fork https://gitlab.labs.nic.cz/honeynet/kippo
which contains commits from https://github.com/micheloosterhof/kippo-mo
(Michel Oosterhof brought awesome SFTP, and exec support)
and original kippo https://github.com/desaster/kippo
(I am very pleased is now on github. was on google code before).
On top of that are my changes:
The Italian Chapter is proud to release the latest version of dorothy2 (our ruby-based malware analysis framework) :).
A few days ago I was contacted by our CPRO, Leon van der Eijk, and asked to write a blog post about my own project called Bifrozt; something which I was more than happy to do. :) This post will explain what Bifrozt is, how this got started, the overall status of the project and what will happen further down the road.
What is Bifrozt?
Finally we can announce with great pleasure the first public beta of the Beeswarm project.
Beeswarm is an active IDS project that provides easy configuration, deployment and management of honeypots and clients. The project differentiates itself by two key items: