
Security it's my main field, about security and about my life you'll find here.



The browserrecon project is doing some research in the field of web client fingerprinting. The goal is the highly accurate identification of given web browser implementations. This became important within professional vulnerability analysis (e.g. drive-by pharming and phishing).Besides the discussion of different approaches and the documentation of gathered results also an implementation for automated analysis is provided. This software shall improve the easyness and efficiency of this kind of enumeration. Traditional approaches known from http fingerprinting (e.g. header-order) are used. However, many other analysis techniques were introduced to increase the possibilities of accurate web client fingerprinting. Some basics of application fingerprinting were already discussed in the book Die Kunst des Penetration Testing (Chapter 9.3, HTTP-Fingerprinting, pp. 530-550).


The researchers achieved a 92 per cent success rate in cracking Microsoft CAPTCHAs, which mix distorted characters with randomly placed arcs. The technique employs a sequence of simple graphical manipulations based on the properties of the CAPTCHAs, including contrast enhancement, transverse histogram analysis for character segmentation, pixel counting for arc elimination and colour filling for character boundary detection. A demonstration written in non-optimised Java took less than 100ms per CAPTCHA on a 1.8GHz PC.

With rtpbreak you can detect, reconstruct and analyze any RTP session. It doesn't require the presence of RTCP packets and works independently form the used signaling protocol (SIP, H.323, SCCP, ...). The input is a sequence of packets, the output is a set of files you can use as input for other tools (wireshark/tshark, sox, grep/awk/cut/cat/sed, ...). It supports also wireless (AP_DLT_IEEE802_11) networks. This is a list of scenarios where rtpbreak is a good choice:reconstruct any RTP stream with an unknown or unsupported signaling protocolreconstruct any RTP stream in wireless networks, while doing channel hopping (VoIP activity detector)reconstruct and decode any RTP stream in batch mode (with sox, asterisk, ...)reconstruct any already existing RTP streamreorder the packets of any RTP stream for later analysis (with tshark, wireshark, ...)build a tiny wireless VoIP tapping system in a single chip Linux unitbuild a complete VoIP tapping system (rtpbreak would be just the RTP dissector module!)This project is released under license GPL version 2.


This file contains all the physical memory saved by the Operating System and aims to be restored by the user the next time the computer is powered on. Live forensics analysis is used to use physical memory dump to recover information on the targeted machine.
One of the main problems is to obtain a readable physical memory dump, hibernation is an efficient way to save and load physical memory. Hibernation analysis has notable advantages. System activity is totally frozen, therefore coherent data is acquired and no software tool is able to block the analysis. The system is left perfectly functional after analysis, with no side effects.
The hibernation file opens two valuable doors:
The first one is forensics analysis for defensive computing. Hibernation is an efficient and easy way to get a physical memory dump. But the main issue about it was: How to read the hiberfil.sys? This is why SandMan was born.
The second one is a new concept we will be introducing and called “offensics” which is a portmanteau from “offensive” and “forensics”. If we can read hiberfil.sys, can we rewrite it? The answer is: Yes, with SandMan you can.
Sandman is a C Library that aims to read the hibernation file, regardless of Windows version. Thus, it makes possible to do forensics live analysis on the dumped file.