
Honeyd Resources
Main - News - Forums Honeyd ResearchHoneypot ResourcesHappy Hacking
|
Re: Help in deciphering config rules.. DATE_IN_FUTURE_03_06,HTML_MESSAGE,USER_IN_DEF_WHITELIST autolearn=no version=2.63
From: Graeme Connell <gconnell_at_middlebury.edu>
Date: 21 Apr 2004 19:55:13 -0000 ('binary' encoding is not supported, stored as-is) In-Reply-To: <Pine.LNX.4.56.0404201319590.8723_at_pali.cps.cmich.edu> >Just got interested in honeyd. I found sample config files
The lines you quoted are ports where honeyd sends incoming data to scripts. Scripts are (I believe) any executable program, although most are just perl, shell, or python scripts. Incoming data is communicated through STDIN, and outgoing data with STDOUT. For example, in a simple shell script, the script
#!/bin/bash
will produce output as follows:
<b>username dir # telnet IPADDR HONEYPORT</b>
telnet> close
This is the type of input you'd see if IPADDR was part of honeyd and it's port HONEYPORT was directed to the simple script above.
add default udp port 23 "./simplescript.sh $ipsrc"
A simple redoing of our script can log output to a file based on the ip source:
#!/bin/bash
This will create and append to a seperate filename (the ip address) and record all data passed to port 23 through a session.
Hope this helps,
Graeme Connell
NB: This is a filtered version of the Honeypots mailing list. Only posts that concern Honeyd are shown here. For more recent discussions visit the forums. | ||||
|
Copyright (c) 1999-2004 by Niels Provos Don't access my pirated music. | |||||