Re: The OCSP server experienced an internal error

[meagain]

 Original Message 

David E. Ross wrote:


I went to [Edit > Preferences] on the SeaMonkey menu bar and
selected [Privacy & Security > Certificates] on the left side of the
Prefeences window (under Category).  If I clear both checkboxes under
OCSP, I have no problem reaching google.com; but I refuse to surf the
Web in such an insecure manner.  If I check only the first checkbox,
I again have no problem; but that is still surfing in an insecure
manner.  If I check both checkboxes, the problem still exists.


Fair points.

So why should we care if our connection to Google is secure? It's just a 
search engine.




Hmm-mm, both my check-boxes  for certificates are checked and I have no 
problem with https://www.google.com


Now, Google is way more than a "search engine" - it is an archive AND 
accumulates information on what users search for and about. And now it 
listens to every conversation near a Google Home! Home + Dot + Echo 
devices now sell at the rate of  one a second! (or so they tell me)

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: The OCSP server experienced an internal error

[meagain]

 Original Message 

President Trump:  Please stop using Twitter.  We need
to hear your voice and see you talking.  We need to know
when your message is really your own and not your attorney's.


And not a bot!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: The OCSP server experienced an internal error

[David E. Ross]

On 1/20/2018 7:13 PM, Paul B. Gallagher wrote:
> David E. Ross wrote:
> 
>> I went to [Edit > Preferences] on the SeaMonkey menu bar and
>> selected [Privacy & Security > Certificates] on the left side of the
>> Prefeences window (under Category).  If I clear both checkboxes under
>> OCSP, I have no problem reaching google.com; but I refuse to surf the
>> Web in such an insecure manner.  If I check only the first checkbox,
>> I again have no problem; but that is still surfing in an insecure
>> manner.  If I check both checkboxes, the problem still exists.
> 
> Fair points.
> 
> So why should we care if our connection to Google is secure? It's just a 
> search engine.
> 

That is a very good question.  However, Mozilla is working towards
having Firefox mark all non-HTTPS Web sites with warnings.  There have
even been suggestions at other organizations that their browsers reject
attempts to view non-HTTPS sites.

-- 
David E. Ross


President Trump:  Please stop using Twitter.  We need
to hear your voice and see you talking.  We need to know
when your message is really your own and not your attorney's.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: The OCSP server experienced an internal error

[Paul B. Gallagher]

David E. Ross wrote:


I went to [Edit > Preferences] on the SeaMonkey menu bar and
selected [Privacy & Security > Certificates] on the left side of the
Prefeences window (under Category).  If I clear both checkboxes under
OCSP, I have no problem reaching google.com; but I refuse to surf the
Web in such an insecure manner.  If I check only the first checkbox,
I again have no problem; but that is still surfing in an insecure
manner.  If I check both checkboxes, the problem still exists.


Fair points.

So why should we care if our connection to Google is secure? It's just a 
search engine.


--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: The OCSP server experienced an internal error

[David E. Ross]

On 1/20/2018 12:23 PM, meagain wrote:
> On 1/19/2018 5:37 PM, Lee wrote:
>> On 1/19/18, meagain  wrote:
>>> On 1/19/2018 4:26 PM, Paul in Houston, TX wrote:
 meagain wrote:
> What did I do and How do I fix it?

 Odds are that you attempted to connect to a web server that may have an
 invalid security certificate.  It tends to happen around this time of
 year.

 Call or email them and tell them to fix it.
 Temporarily you can be not as secure until they fix it by setting
 security.OCSP.enabled  to False
 I would not leave it that way though.
>>>
>>> Got it!   require
>>
>> What's going on?
>>
>> change
>>security.OCSP.require
>> to true and I get the
>>Secure Connection Failed
>>An error occurred during a connection to www.google.com.
>>The OCSP server experienced an internal error.
>> trying to load https://www.google.com, but then change
>>security.OCSP.GET.enabled
>> to true and it works!?
>>
>> Lee
>>
> 
> I set both ...enabled   and ...required to   "true" and all is well 
> again.  How they got missmatched is a mystery.
> 

I went to [Edit > Preferences] on the SeaMonkey menu bar and selected
[Privacy & Security > Certificates] on the left side of the Prefeences
window (under Category).  If I clear both checkboxes under OCSP, I have
no problem reaching google.com; but I refuse to surf the Web in such an
insecure manner.  If I check only the first checkbox, I again have no
problem; but that is still surfing in an insecure manner.  If I check
both checkboxes, the problem still exists.

-- 
David E. Ross


President Trump:  Please stop using Twitter.  We need
to hear your voice and see you talking.  We need to know
when your message is really your own and not your attorney's.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: The OCSP server experienced an internal error

[meagain]

On 1/19/2018 5:37 PM, Lee wrote:

On 1/19/18, meagain  wrote:

On 1/19/2018 4:26 PM, Paul in Houston, TX wrote:

meagain wrote:

What did I do and How do I fix it?


Odds are that you attempted to connect to a web server that may have an
invalid security certificate.  It tends to happen around this time of
year.

Call or email them and tell them to fix it.
Temporarily you can be not as secure until they fix it by setting
security.OCSP.enabled  to False
I would not leave it that way though.


Got it!   require


What's going on?

change
   security.OCSP.require
to true and I get the
   Secure Connection Failed
   An error occurred during a connection to www.google.com.
   The OCSP server experienced an internal error.
trying to load https://www.google.com, but then change
   security.OCSP.GET.enabled
to true and it works!?

Lee



I set both ...enabled   and ...required to   "true" and all is well 
again.  How they got missmatched is a mystery.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: The OCSP server experienced an internal error

[Lee]

On 1/19/18, meagain  wrote:
> On 1/19/2018 4:26 PM, Paul in Houston, TX wrote:
>> meagain wrote:
>>> What did I do and How do I fix it?
>>
>> Odds are that you attempted to connect to a web server that may have an
>> invalid security certificate.  It tends to happen around this time of
>> year.
>>
>> Call or email them and tell them to fix it.
>> Temporarily you can be not as secure until they fix it by setting
>> security.OCSP.enabled  to False
>> I would not leave it that way though.
>
> Got it!   require

What's going on?

change
  security.OCSP.require
to true and I get the
  Secure Connection Failed
  An error occurred during a connection to www.google.com.
  The OCSP server experienced an internal error.
trying to load https://www.google.com, but then change
  security.OCSP.GET.enabled
to true and it works!?

Lee
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: The OCSP server experienced an internal error

[Paul in Houston, TX]

meagain wrote:

On 1/19/2018 4:26 PM, Paul in Houston, TX wrote:

meagain wrote:

What did I do and How do I fix it?


Odds are that you attempted to connect to a web server that may have an
invalid security certificate.  It tends to happen around this time of year.

Call or email them and tell them to fix it.
Temporarily you can be not as secure until they fix it by setting
security.OCSP.enabled  to False
I would not leave it that way though.


Got it!   require

Thanks


Just checked Google and it is doing the same with me.
Same thing happened with them last year.
Give them a couple of days then change the ocsp back to True.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: The OCSP server experienced an internal error

[meagain]

On 1/19/2018 4:26 PM, Paul in Houston, TX wrote:

meagain wrote:

What did I do and How do I fix it?


Odds are that you attempted to connect to a web server that may have an
invalid security certificate.  It tends to happen around this time of year.

Call or email them and tell them to fix it.
Temporarily you can be not as secure until they fix it by setting
security.OCSP.enabled  to False
I would not leave it that way though.


Got it!   require

Thanks

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: The OCSP server experienced an internal error

[meagain]

On 1/19/2018 4:26 PM, Paul in Houston, TX wrote:

meagain wrote:

What did I do and How do I fix it?


Odds are that you attempted to connect to a web server that may have an
invalid security certificate.  It tends to happen around this time of year.

Call or email them and tell them to fix it.
Temporarily you can be not as secure until they fix it by setting
security.OCSP.enabled  to False
I would not leave it that way though.


the site was

https://www.google.com

which I use as my SeaMonkey "home page".


to access   security.ocsp.enabledwhat is the argument to 'about:'?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: The OCSP server experienced an internal error

[Paul in Houston, TX]

meagain wrote:

What did I do and How do I fix it?


Odds are that you attempted to connect to a web server that may have an
invalid security certificate.  It tends to happen around this time of year.

Call or email them and tell them to fix it.
Temporarily you can be not as secure until they fix it by setting
security.OCSP.enabled  to False
I would not leave it that way though.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey