[HTTPS-E Rulesets] merge my new contributions

Victor Garin vic.garin at gmail.com
Tue Feb 21 14:46:14 PST 2012


Any update on merging my contributions:

https://github.com/vicgarin/vicHTTPS

or

git://github.com/vicgarin/vicHTTPS.git

?


On Thu, Nov 10, 2011 at 6:21 PM, Peter Eckersley <pde at eff.org> wrote:

> Vic,
>
> We know how time-consuming rulset editing is (we do a lot ourselves ;),
> and we
> appreciate the contributions you've made!  The problem is that we don't
> want
> to merge rulesets that haven't had a bit of care and human prodding,
> because
> everything we merge goes out to around a million web browsers, and when it
> breaks stuff, we get blamed for it!
>
> I will see if anyone else in the community has some time to go through
> them.
> If not, we will be able to do it eventually, but it will take longer!
>
> On Thu, Nov 10, 2011 at 04:20:58PM -0800, Victor Garin wrote:
> > I cannot go through them again...I already spent around 4 hours going
> > through each rule and removing the HTTPS Finder's credits and then
> putting
> > them on the GIT....
> >
> > https://github.com/vicgarin/vicHTTPS
> >
> > or
> >
> > git://github.com/vicgarin/vicHTTPS.git
> >
> > On Thu, Nov 10, 2011 at 11:40 AM, Peter Eckersley <pde at eff.org> wrote:
> >
> > > On Thu, Nov 10, 2011 at 11:10:53AM -0800, Victor Garin wrote:
> > > > I noticed the Git started getting new rules.
> > > >
> > > > Any updates on merging my rulesets.
> > > >
> > > > I spent alot of time putting them in the GIT.
> > >
> > > Yes we're just looking at them now.  There are some that look like they
> > > were
> > > generated by HTTPS Finder and will need more human attention.  For
> > > instance:
> > >
> > > - there's a rulset for www8.garmin.com and a separate ruleset for
> > >  www.garmin.com.  Shouldn't those be in the same file?
> > >
> > > - there are separate rulesets for h20386.www2.hp.com and
> shopping1.hp.com.
> > >  Do
> > >  we have any confidence that rewriting those two domains won't break
> > >  functionality on parts of the HP site? (remember that Referer headers
> > > will be
> > >  blocked by the rewrite, and the example of https://www.hp.com is not
> > >  confidence-inspiring)
> > >
> > > - There are also other smaller things like an "about.telus.com"
> ruleset
> > > that
> > >  rewrites www.about.telus.com (which is a non-existent subdomain)
> > >
> > > If you're able to take an extra pass over the rulesets to make sure
> they're
> > > all basically tested and sensible, we should be able to merge the
> results.
> > >
> > > --
> > > Peter Eckersley                            pde at eff.org
> > > Technology Projects Director      Tel  +1 415 436 9333 x131
> > > Electronic Frontier Foundation    Fax  +1 415 436 9993
> > >
>
> --
> Peter Eckersley                            pde at eff.org
> Technology Projects Director      Tel  +1 415 436 9333 x131
> Electronic Frontier Foundation    Fax  +1 415 436 9993
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.eff.org/pipermail/https-everywhere-rules/attachments/20120221/2bb21216/attachment.html>


More information about the HTTPS-Everywhere-Rules mailing list