Thanks for all the off-list interest. I just thought I'd add one side note about Nessus. It took over 48 hours to scan 6 ip's (with one of them running a real webserver), never correctly identified the host OS'es I have, and failed to produce the same results twice. Thanks, Bob -----Original Message----- From: netfilter-admin@xxxxxxxxxxxxxxxxxxx [mailto:netfilter-admin@xxxxxxxxxxxxxxxxxxx]On Behalf Of bmcdowell@xxxxxxxxxxxxxxxxxx Sent: Friday, November 14, 2003 10:25 AM To: netfilter@xxxxxxxxxxxxxxxxxxx Subject: RE: Redirect to Honeypot? For the curious, this is what I think I'm going to stick with for now: Brouter --- DMZ | (NAT) | (Decoy Box) --- 25% TARPIT, 25% DROP | (Random HoneyPot) --- (One real W2K server, One real Linux, 10 emulated Honeyd devices) Just as I had drop rules before, I now have DNAT rules first. E.g. iptables -t nat -A PREROUTING -p tcp -d (webserver) --dport ! 80 -j DNAT --to (decoy box) iptables -A FORWARD -p tcp -d (webserver) --dport ! 80 -j (LOG/DROP) Just to muddy the waters a bit, I added the TTL patch to the box distributing packets to my honeypots. E.g. iptables -t mangle -A POSTROUTING -j TTL --ttl-inc 2 That makes TTL's from the NAT'ed boxes and the real boxes have the same value... Now when I aim Nmap at my webserver, for example, it takes an average of 18 minutes to return results (against just that one server). Once it even crashed, after 13 or so minutes of scanning. I couldn't get it to run again after that (on my Windows laptop) until I rebooted. Those results that are returned are wildly inaccurate, and are different each time the scan is run. OS detection is amusing - it generally returns as Unknown, but sometimes picks something interesting. While all this scanning is going on, my webserver still happily serves up pages to the attack box. Clearly this is going to need more work to if I'd ever like to get it out of test. If I find anything truely interesting, I'll pass it along. If anyone has any comments/questions/concerns please don't hesitate to send them my way. Thanks, Bob -----Original Message----- From: netfilter-admin@xxxxxxxxxxxxxxxxxxx [mailto:netfilter-admin@xxxxxxxxxxxxxxxxxxx]On Behalf Of bmcdowell@xxxxxxxxxxxxxxxxxx Sent: Tuesday, November 11, 2003 2:58 PM To: netfilter@xxxxxxxxxxxxxxxxxxx Subject: Redirect to Honeypot? Does anyone on the list have a recomendation as to how one might use iptables to redirect traffic to a honeypot? I have a few ideas, but I'd really like to hear from someone who has a solution they like (or even an idea they like). Thanks in advance. To clarify just a bit: I'd like to be able to redirect packets instead of dropping them. I'd also like to be able to do this as a catch-all rule at the end of my input and forward chains. The overall idea is to combine randomly dropping packets, tarpitting, and live honeypot responses (from different OS'es) in an effort to utterly stump recon efforts. In my head, I have visions of Linux boxes reporting they're running IIS 5 and Crays running (x app), etc. In my testing so far, I've found that combining randomly dropping packets and tarpitting to be extremely effective at slowing normal NMap scans. In some cases, scan time was increased to well over two hours. Now I'd like to introduce live ports into that mix. This way, a positive hit on a live port would not necessarily have to be one of my production boxes. In fact, it probably isn't... Thanks again, Bob
<<winmail.dat>>
