[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ale]OT It begins... (jumping into the middle)
- Subject: [ale]OT It begins... (jumping into the middle)
- From: kjkrum at comcast.net (Kevin Krumwiede)
- Date: Wed Feb 4 22:09:16 2004
- In-reply-to: <1075947892.20921.6.camel@bluetoo>
- References: <001b01c3e465$604d14c0$0a00a8c0@atlas> <1075902202.14425.5.camel@bluetoo> <[email protected]> <[email protected]> <1075947892.20921.6.camel@bluetoo>
On Wed, 04 Feb 2004 21:24:52 -0500
Jim Popovitch <jimpop at yahoo.com> wrote:
> yourself exposed. The same concept applies to "obfuscating" email
> addresses. If they can be read by a human, they can be read by a
> machine. I like the image substitution idea, but remember it can be
> OCR'ed... unless it is near impossibe to read (see above comments).
You're right, they *can* be read by a machine. However, obfuscating
them makes it less likely that they will be. There are countless ways
of obfuscating an email address so that it can still be read by a human.
Any given harvester bot will *not* be looking for every single
variation. Likewise, something as simple as changing the name of a
resource or running a server on a non-standard port may do nothing to
stop a determined attacker specifically targeting your systems, but it
*will* stop most worms, viruses, and skript kiddies dead in their
tracks. If you evaluate risk as a product of how potentially damaging
something could be vs. how likely it is to occur, then simple measures
like these should not be discounted.