[HTTPS-E Rulesets] Wildcard confusion and data structure question

[Adam Fisk]

This makes perfect sense, Peter, and thanks for the timely response.

I'll again let people know more soon, but one interesting part of
integrating this into Lantern will be that Lantern runs as a local
HTTP proxy, so the rules will work on all browsers and ultimately all
OSes (just Windows and Mac for now unfortunately). Having those rule
sets as separate XML files is really invaluable for creating a common
language. Lantern is primarily a censorship circumvention tool, but
being able to channel as much traffic as possible through HTTPS has
become a vital part of its architecture.

Thanks again.

-Adam


On Thu, Aug 11, 2011 at 3:54 PM, Peter Eckersley <pde at eff.org> wrote:
> On Thu, Aug 11, 2011 at 03:51:26PM -0700, Peter Eckersley wrote:
>
>> Unlike other portions of the rulset, these are not regular expressions.  A
>> * matches a number of characters that are not ".".  As a special case, a * at
>> the leftmost end matches things that include ".".
>
> Also: you can have at most one * in a target host element.
>
> --
> Peter Eckersley                            pde at eff.org
> Technology Projects Director      Tel  +1 415 436 9333 x131
> Electronic Frontier Foundation    Fax  +1 415 436 9993
>