Skip to content
PherricOxide edited this page Apr 6, 2012 · 15 revisions

Welcome to the DataSoft Honeyd wiki!

Build Process

Configuring

Honeyd uses automake to set up dependencies and such. So you'll need the following packages installed beforehand:

On Ubuntu:

sudo apt-get install libevent-dev libdumbnet-dev libpcap-dev libpcre3-dev libedit-dev bison flex libtool automake

On ArchLinux:

`

# First get these packages

pacman -S libdnet libpcap pcre libedit bison flex libtool automake

# Libevent1 must be downloaded and installed from AUR. Libevent2 does not currently work with honeyd.

pacman -S base-devel

wget http://aur.archlinux.org/packages/li/libevent1/libevent1.tar.gz

tar -xzf libevent1.tar.gz

cd libevent1

makepkg

pacman -U libevent1-1.4.14b-1-x86_64.pkg.tar.xz

`

Now go to the main source directory, and run:

./autogen.sh

automake

./configure

For Ubuntu 11.04+ Users

You will need lib-event1 as well if you are running 11.04

sudo apt-get install libevent1-dev

One of the changes made for multiarch support was to move libc.so from /usr/lib/ to /lib/1386-linux-gnu/ This was done so that you can have i386 and AMD64 versions of libc installed on your system and use them. However, it breaks compatibility with old scripts that hardcoded the location of libc. Honeyd does this.

You can't fix this with a symlink, since that'd defeat the whole purpose of moving the file for multiarch support in the first place. Just edit the configure script, like so:

gedit configure

Then hit ctrl-H, Search for

/usr/lib/libc.so

And replace with:

/lib/i386-linux-gnu/libc.so

That'll do the trick. Now try running ./configure again.

Import into Eclipse

Set a new workspace as the honeyd source directory.

Then File->Import... -> Existing Code as Makefile Project. Select the honeyd source file directory. (The directory that contains ./configure, README, etc...) Select Finish.

It should all import in. Now build the project, and have fun!

Fingerprint Errors

If ever you find a Honeyd profile that doesn't come up as a 100% result on an Nmap OS Scan, please make an Issue for it! We really want to know if there are any instances where Honeyd doesn't respond exactly correct. Keep a watchful eye out for the SP and ISR values inside the SEQ line of results. (Those ones are timing based, and you have to nail the value within a sometimes very tight bound) Thanks!

Clone this wiki locally