pandora still broken in 3.0 development version

I downloaded the stable version of https everywhere and pandora rule was broken, so I googled and I found a ticket tracking it:

https://trac.torproject.org/projects/tor/ticket/5804

it says this bug was fixed in 3.0development.3 so I downloaded the 3.0development.7 but still the pandora rule is broken

Trac:
Username: Ghilteras

added component::https everywhere/eff-https everywhere owner::pde priority::medium reporter::Ghilteras resolution::worksforme status::closed type::defect version::https-e 3.0dev7 labels

Weird. The pandora ruelset is disabled by default, and when disabled, the site works for me. Do you have the pandora ruleset enabled? (you can look in the context menu or go to the HTTPS Everywhere settings and find in the list of rulesets)

Marking as "works for me". Please reopen if you see this after resetting rules to the defaults, or installing in a fresh browser profile.

Trac:
Resolution: N/A to worksforme
Status: new to closed

well yes I am reopening it because.. it does not work.

this time I'm attaching screenshots.

how can you say it works? disabled/enabled it's the same since the rule is marked as broken and in any case the website shows as restriced in both cases

Trac:
Username: Ghilteras
Resolution: worksforme to N/A
Status: closed to reopened

Trac:
Username: Ghilteras

enabled

Trac:
Username: Ghilteras

Trac:
Username: Ghilteras

disabled

Trac:
Username: Ghilteras

1. With the ruleset disabled, have you tried manually going back to http://www.pandora.com ?

2. Since you appear to be in Belgium, does the IP block really not affect you when HTTPS Everywhere is completely disabled? Or is Pandora just not accessible at all?

For the most part I just don't believe your screenshots are of an HTTPS Everywhere bug. They're screenshots of Pandora being blocked because you're in Belgium. I'm willing to hear evidence that those two things are connected in some way (eg, while still in Belgium you disable HTTPS Everywhere completely and Pandora works again, or you're not actually in Belgium at all), but those would be surprising.

Replying to pde:

1. With the ruleset disabled, have you tried manually going back to http://www.pandora.com ?

yes I tried and I still got the restricted page

2. Since you appear to be in Belgium, does the IP block really not affect you when HTTPS Everywhere is completely disabled? Or is Pandora just not accessible at all?

of course pandora is not accesible from belgium, that's why I am using https everywhere and with the older versions everything was working, check bug #5804 (moved)

Replying to pde:

For the most part I just don't believe your screenshots are of an HTTPS Everywhere bug. They're screenshots of Pandora being blocked because you're in Belgium. I'm willing to hear evidence that those two things are connected in some way (eg, while still in Belgium you disable HTTPS Everywhere completely and Pandora works again, or you're not actually in Belgium at all), but those would be surprising.

as I said, maybe there is a misunderstanding here.

I am using https to access pandora when I am in Belgium, of course from the US I do not have any issue and of course without the plugin I still cannot access.

But months ago it simply worked, then the rule broke, but according to #5804 (moved) it was fixed.

Trac:
Username: Ghilteras

Replying to Ghilteras:

of course pandora is not accesible from belgium, that's why I am using https everywhere and with the older versions everything was working, check bug #5804 (moved)

It sounds like this was a fluke; maybe Pandora's old IP block only worked over HTTP. Nothing in HTTPS Everywhere can hide your public IP address from the site you're visiting, so if Pandora is checks your IP they will know you are in Belgium, HTTPS or not.

If you want to actually tunnel your traffic from country A to country B, the common methods would be using a proxy or "ssh -D" proxy in country B; using a VPN service in country B; or using Tor with a configuration that says only use exit nodes in country B.

HTTPS Everywhere can't do any of these things for you!

Trac:
Resolution: N/A to worksforme
Status: reopened to closed

Trac:

Trac:

This is definitely not an HTTPS Everywhere bug, it's due to the fact that you're in Belgium.

I am currently in Belgium as well, and I've attached screenshots of the same thing happening with 3.0-dev5. The rule is disabled by default, and my servers back in the States hit pandora.com just fine.

so indeed something changed at certain point early 2012, because at that time it was going to pandora even from non-US countries and many guides have been published for that infact.

if you google pandora + https everywhere you'll get many of them:

i.e. http://www.howtogeek.com/107650/listen-to-pandora-anywhere-without-a-using-a-proxy/

so since this is not possible anymore (being the rule enabled or not) I'll just go back the old way and discover usa proxies with vidalia and use them with tor.

Trac:
Username: Ghilteras

Sure, something changed, but it was probably just Pandora noticing that HowToGeek article and fixing their SSL client IP checking. Nothing changed in HTTPS Everywhere.

closed

moved to tpo/applications/https-everywhere-eff#7012 (closed)