Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Disabling https everywhere

2,274 views
Skip to first unread message

JC Dill

unread,
Jun 1, 2012, 3:21:00 PM6/1/12
to
I'm running into a problem where it looks like https is being blocked,
but only on one network I'm using. (Arugh!) I think I may also have
https everywhere enabled, as attempts to reach pages like
http://maps.google.com redirect to https://maps.google.com, and since
https is blocked, I can't reach Google Maps.

I'd like to disable https everywhere, but I can't reach the EFF page
about https everywhere - because https is being blocked. Catch-22! I
tried using Yahoo cache, but it just redirects to the eff site (using
https) so I can't actually SEE the cache page.

Can someone look-up the info about how to disable https everywhere for
both Safari and Firefox, on a Mac?

Or... is there some other reason that attempts to reach
http://maps.google.com would be redirected to https://maps.google.com
which then doesn't work? (In other words, have I made a dumb assumption
about where the root problem lies?)

jc

David Arnstein

unread,
Jun 1, 2012, 5:03:09 PM6/1/12
to
In article <jqb4mp$ak$1...@speranza.aioe.org>,
JC Dill <jcdill...@gmail.com> wrote:
>Can someone look-up the info about how to disable https everywhere for
>both Safari and Firefox, on a Mac?

On Firefox, the https-everywhere that I know about is an extension. I
suggest that you use the menu bar to open Tools/Add-ons and then
select the Extensions tab. If you have HTTPS-Everywhere installed, you
will see it. Each extension has a "Disable" button.

I visited the EFF site, and I can only find downloads for Firefox and
Chrome. In fact, the FAQ states that Apple has made it impossible to
port the extension to Safari. At the moment, I don't have an Apple
computer to fiddle with.

>Or... is there some other reason that attempts to reach
>http://maps.google.com would be redirected to https://maps.google.com
>which then doesn't work? (In other words, have I made a dumb assumption
>about where the root problem lies?)

Previous posts from JC Dill are evidence against the "dumb" theory. I
found this web page via Google, maybe it applies:
http://support.mozilla.org/en-US/kb/Firefox%20cannot%20connect%20securely%20because%20the%20SSL%20protocol%20is%20disabled
--
David Arnstein (00)
arnstei...@pobox.com {{ }}
^^

NoOp

unread,
Jun 1, 2012, 7:25:30 PM6/1/12
to
On 06/01/2012 12:21 PM, JC Dill wrote:
> I'm running into a problem where it looks like https is being blocked,
> but only on one network I'm using. (Arugh!) I think I may also have
> https everywhere enabled, as attempts to reach pages like
> http://maps.google.com redirect to https://maps.google.com, and since
> https is blocked, I can't reach Google Maps.

Works for me.

Build identifier: Mozilla/5.0 (X11; Linux i686; rv:12.0)
Gecko/20120429 Firefox/12.0 SeaMonkey/2.9.1
[HTTPS-Everywhere 2.0.5]

And

User Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20100101
Firefox/12.0
[HTTPS-Everywhere2.0....@eff.org]

And

Safari 5.0.5 (7533.21.1)
Note: no https everywhere installed on that as there isn't a version for
Safari (that I'm aware of) - I just tried 'https://google.maps' instead.

My _guess_ is that it's not https that is causing you problems if you
can't get to 'https://google.maps' from Safari.

>
> I'd like to disable https everywhere, but I can't reach the EFF page
> about https everywhere - because https is being blocked. Catch-22! I
> tried using Yahoo cache, but it just redirects to the eff site (using
> https) so I can't actually SEE the cache page.
>
> Can someone look-up the info about how to disable https everywhere for
> both Safari and Firefox, on a Mac?

Firefox:
about:addons
Or Tools|Add-ons
HTTPS Everywhere - Disable
(however you might want to check Preferences
>
> Or... is there some other reason that attempts to reach
> http://maps.google.com would be redirected to https://maps.google.com
> which then doesn't work? (In other words, have I made a dumb assumption
> about where the root problem lies?)
>
> jc

I modified my Google search button a long time ago to use https
(https://encrypted.google.com/), I I use it even if I do not have
https-everywhere turned on.

As a side note: When in Safari, I decided to try the 'Help|Safari
Extensions Gallery' to see if perhaps there was an 3rd party
https-everywhere... had to laugh as that came up with an invalid cert
error. However, going back to the link is fine & uses the proper
Verisign cert.

Jeff Liebermann

unread,
Jun 1, 2012, 7:38:03 PM6/1/12
to
On Fri, 01 Jun 2012 12:21:00 -0700, JC Dill <jcdill...@gmail.com>
wrote:

>I'm running into a problem where it looks like https is being blocked,
>but only on one network I'm using.

Process de limination:
1. Try your Thinkpad X31 and HTC phone and see if they do the same
thing. If yes, then something is goofy at whatever hot spot you're
using. If possible, reboot the router.
2. If Firefox and Safari both do the same thing, try Chrome. If all
three screw up, then it's NOT the browser or HTTPS Everywhere.
3. Try Lynx:
<http://habilis.net/lynxlet/>
SSL support. Same logic as above. If everything screws up, then it's
not the browser or HTTPS Everywhere.
4. Check the date on y'er Mac. The wrong date causes problems with
certificates.
5. Ummm... reboot the Mac? Yeah, I know it's dumb, but I keep
running into situations where it magically fixes things, especially if
you've been running days without a reboot.


--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831-336-2558
# http://802.11junk.com je...@cruzio.com
# http://www.LearnByDestroying.com AE6KS

JC Dill

unread,
Jun 2, 2012, 11:04:01 AM6/2/12
to
On 01/06/12 4:25 PM, NoOp wrote:
> On 06/01/2012 12:21 PM, JC Dill wrote:
>> I'm running into a problem where it looks like https is being blocked,
>> but only on one network I'm using. (Arugh!) I think I may also have


> I modified my Google search button a long time ago to use https
> (https://encrypted.google.com/), I I use it even if I do not have
> https-everywhere turned on.

OK, I think that the problem is that the network I'm using has blocked
https, but because Google search is set to only use https, I can't reach
*any* Google page. So I can't get into Google to change the setting, to
allow me to connect with a non-https page.

However, I'm running into this same authentication loop problem with
other sites including Facebook and nextdoor.com. I try to go to the
non-https page, it redirects to the https page, which is blocked. ARUGH.

jc

0 new messages