Currently the database is not updated after a succesfull whitelist, only the current session is whitelisted.
If you set the greylist cache to several days, the visitor has to whitelist every time he returns.
Is it possible to get an option to update the database, setting the status of the IP to HTTPBL_LIST_SAFE after a succesfull whitelist attempt.
Attached my patches.

CommentFileSizeAuthor
httpbl.admin_.inc_.patch1016 bytespromes
httpbl.module.patch667 bytespromes

Comments

bryrock’s picture

bryrock commented
Assigned: Unassigned » bryrock

promes, Sorry for the late response (been super busy), but I'll check this out. I'm ambivalent about who gets whitelisted after a challenge, but I think it's worth a shot. Just not sure when I'll have a chance to test it.

bendiy’s picture

bendiy commented
Issue summary: View changes
Status: Active » Reviewed & tested by the community

I found the $_SESSION setting wasn't working on D6. This change fixed it.

bryrock’s picture

bryrock commented
Status: Reviewed & tested by the community » Closed (won't fix)

Not fixing this because it is supposed to only be session based whitelisting. It happens when a grey-listed IP succeeds at the challenge, but based on how they scored from Project Honeypot, they are listed as status 2, and that doesn't change in the database. You could say session white-listed is grey-listed on temporary probation.