[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-talk] BridgeDB reCAPTCHA deployed

To: tor-talk@xxxxxxxxxxxxxxxxxxxx
Subject: [tor-talk] BridgeDB reCAPTCHA deployed
From: Aaron <aagbsn@xxxxxxxxxxxxxx>
Date: Mon, 16 Jul 2012 19:48:39 +0000
Delivered-to: archiver@xxxxxxxx
Delivery-date: Mon, 16 Jul 2012 15:48:07 -0400
List-archive: <http://lists.torproject.org/pipermail/tor-talk>
List-help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-id: "all discussion about theory, design, and development of Onion Routing" <tor-talk.lists.torproject.org>
List-post: <mailto:tor-talk@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
Reply-to: tor-talk@xxxxxxxxxxxxxxxxxxxx
Sender: tor-talk-bounces@xxxxxxxxxxxxxxxxxxxx

BridgeDB's HTTPS distributor (https://bridges.torproject.org) now
requires a CAPTCHA to be solved before serving bridges.

The related tickets can be found here:
https://trac.torproject.org/projects/tor/ticket/5481

The CAPTCHA implementation used is reCAPTCHA. BridgeDB proxies
requests to the reCAPTCHA API servers so that visitors to
https://bridges.torproject.org connect only to
https://bridges.torproject.org.

--Aaron
_______________________________________________
tor-talk mailing list
tor-talk@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

Follow-Ups:
- Re: [tor-talk] BridgeDB reCAPTCHA deployed
  - From: andrew

Prev by Author: Re: [tor-talk] [info] Anonymous Publishing Is Dead.
Next by Author: Re: [tor-talk] BridgeDB reCAPTCHA deployed
Previous by thread: Re: [tor-talk] cached-descriptors data format
Next by thread: Re: [tor-talk] BridgeDB reCAPTCHA deployed
Index(es):
- Author
- Thread