From owner-freebsd-questions@FreeBSD.ORG Sat Feb 25 04:32:39 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 637341065672 for ; Sat, 25 Feb 2012 04:32:39 +0000 (UTC) (envelope-from freebsd-questions@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id 16FC38FC0A for ; Sat, 25 Feb 2012 04:32:39 +0000 (UTC) Received: from mail.unitedinsong.com.au (bell.herveybayaustralia.com.au [192.168.0.40]) by mail.unitedinsong.com.au (Postfix) with ESMTP id 8DFBE5C28 for ; Sat, 25 Feb 2012 14:46:06 +1000 (EST) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.177]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id F258B5C22 for ; Sat, 25 Feb 2012 14:46:05 +1000 (EST) Message-ID: <4F486340.7040907@herveybayaustralia.com.au> Date: Sat, 25 Feb 2012 14:27:44 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111109 Thunderbird/7.0.1 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4F47620D.24859.53F9A2B@dave.g8kbv.demon.co.uk> <868vjs8nto.fsf@ds4.des.no> <4F478D8B.31307.5E97C34@dave.g8kbv.demon.co.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Security? [Re: Why is this Symbol in the front of your website. A humble request.] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2012 04:32:39 -0000 On 02/25/12 12:03, David Brodbeck wrote: > On Fri, Feb 24, 2012 at 5:15 AM, Dave wrote: >> Those address links need changing to graphic's, so that most address >> harvesting bots won't get anything usable. >> >> Mk1 eyeball can still see what's what, but if you have to use the info, >> you have to re-type it manually. > I really don't recommend that. Keep in mind not everyone can use the > "Mk1 eyeball." Websites need to be accessible to blind people using > screen reader software, too. And therein lies the problem. How do you maintain accessibility while preventing bots from harvesting? You can't have your cake and eat it too... :) Only solution lies in a security gate of good filters and blocklists. But occasionally one or two will still pass.