Check out Gimpy, which I believe is what Yahoo uses:
http://www.captcha.net/captchas/gimpy/
http://www.captcha.net/
Narins, Josh wrote:
Can GIMP be programmatically set up to warp/woof/weird-out an image?
Yahoo's warped words works, I bet, since they use it.
I'm referring to get getting an
> "BM" == Bill Moseley <[EMAIL PROTECTED]> writes:
BM> I've got a mod_perl feed-back form that sends mail to a specific address..
BM> Spammers have their bots hitting the form now. The tricks I know of are:
Rename your script and the link pointing to it. It will take some
time for them to f
At 02:51 PM 12/18/02 -0500, Daniel Koch wrote:
>Check out Gimpy, which I believe is what Yahoo uses:
>
>http://www.captcha.net/captchas/gimpy/
I'm thinking of something along those lines. This problem is this is on
Solaris 2.6 w/o root, and I'll bet it would take some time to get The Gimp
and GTK
- Original Message -
Subject: RE: [OT] Ideas for limiting form submissions
> Can GIMP be programmatically set up to warp/woof/weird-out an image?
>
> Yahoo's warped words works, I bet, since they use it.
>
> I'm referring to get getting an anon email account from
Can GIMP be programmatically set up to warp/woof/weird-out an image?
Yahoo's warped words works, I bet, since they use it.
I'm referring to get getting an anon email account from yahoo.com
-Original Message-
From: Bill Moseley [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2
Bill Moseley wrote:
what would you recommend for caching the md5 strings. Cache::Cache or
DBM? I suppose a Cache::Cache file cache would be the easiest.
In order of speed:
IPC::MM
BerkeleyDB (with built-in locking)
Cache::Mmap
Cache::FileBackend (from Cache::Cache -- no need to use Cache::Cach
Some other "imperfect" solutions:
* Take the CRC (or some other hash function) of the message content and
reject messages with duplicate CRC (still vulnerable to morphing of the
message).
* limit submissions by sender to one every X minutes. Avoids the AOL issue,
but vulnerable to DDOS and spoofin
