Message Board

Installing Honey Pots

Older Posts ]   [ Newer Posts ]
 YAVE (Yet another validation error)
Author: M.Lievaart   (25 Jan 05 5:32pm)
Yup, I also seem to hit the dreaded validation error.

First I tried the php script, this timed out on the md5 sum (old P90). So I tried the mod_perl version. Had to add

PerlModule Apache2
PerlModule Apache::compat

to httpd..conf, then got the validation error.

A Pcap dump revealed that th ecorrect hostname was reported, so it must be something else.

Any clue? Do you need more info?

TIA,
M4
 
 Re: YAVE (Yet another validation error)
Author: L.Holloway   (31 Jan 05 12:26am)
Thats correct, after installing mod_perl you need to add the following lines:

LoadModule perl_module modules/mod_perl.iso
PerlModule Apache2
PerlModule Apache::compat

I believe the last two lines are normally not auto inserted by apxs.

Looks like your pot is running just fine. I was able to validate it; its currently active -- just not linked. mod_perl was recently supported and it looks like you tried it the first day it came out; maybe thats it?

Let us know if you run into any more problems. Thanks for the support and welcome to the Project!
 
 Re: YAVE (Yet another validation error)
Author: M.Lievaart   (8 Feb 05 2:39pm)
Hi,

I think I found the problem. The script works when accessed over IPv4, but not when accessed over IPv6. You may want to look into this, for now, I'll just add the links to the page as instructed. Not many harvesters on IPv6 I guess.... :-)

TIA,
M4

Post Edited (8 Feb 05 1:43pm)
 
 Re: YAVE (Yet another validation error)
Author: M.Lievaart   (8 Feb 05 2:51pm)
Another slight problem.

I cannot find the information to setup the hidden linsk to the page anymore. I can think up some ways myself, but that information surely should be accessible somewhere?

TIA,
M4
 
 Re: YAVE (Yet another validation error)
Author: M.Prince   (8 Feb 05 4:17pm)
Funny about IPv6. We definitely aren't supporting that yet, but should and will.

In terms of the Linking Instructions, if you go to the Manage Honey Pots page, click ont he domain of the honey pot you want linking instructions for, and then click on the Linking Instructions menu item in the left-hand menu you'll get instructions customized for that particular honey pot.

The Linking Instructions are something that a LOT of people have trouble finding. Not sure where would be more intuitive to put them. Could include them in the package you download, but then we couldn't have them customized for the location of your honey pot since we wouldn't know where it is going to be installed yet. If anyone has a thought, let us know.
 
 Re: YAVE (Yet another validation error)
Author: M.Lievaart   (9 Feb 05 4:28am)
IPv6: Maybe for now just check and return a meaningful error, that should be pretty easy I think. The validation error is pretty confusing I say.

Linking instructions: Yes, now you say it, it's perfectly clear. What you can do to make it clearer is to turn the name of the honeypot into a visible link. Mosts links on the site are underlined, but the honeypots are not. I missed I could click them, even if it /is/ mentioned one line below. Makes me feel stupid, but if as you say more people have trouble with this....

Cheers and good luck,

M4
 
 Re: YAVE (Yet another validation error)
Author: A.Stewart   (9 Mar 05 11:37am)
Aha! That's my problem, IPv6.
 
 Re: YAVE (Yet another validation error)
Author: L.Holloway   (12 Mar 05 5:23pm)
Ah, IPv6... adding support for that should make things interesting. I'll try to work it in for version 2 of the pots.
 
 Re: YAVE (Yet another validation error)
Author: M.Gruning   (30 Oct 05 11:29pm)
I have installed the script but I do not control my server and do not have access to it logs so I do not know what errors would be in them although I do know that php is installed so I have no idea why I am getting a validation error. Any ideas would be appreciated.

MG



do not follow this link

Privacy Policy | Terms of Use | About Project Honey Pot | FAQ | Cloudflare Site Protection | Contact Us

Copyright © 2004–17, Unspam Technologies, Inc. All rights reserved.

contact | wiki | email