Shopsmith Forums

JPG wrote:

rjent wrote:Try reading this: https://support.mozilla.org/en-US/kb/wh ... ecure-mean

Also, make sure your clock is correct. If the clock is not in time, it can cause this error.

JMHO

You have a question? LOL

The link is to firefox help page dealing with the connection issue of the OP
AND
the clock can cause a browser to "think" that a security issue is present, even though it is not. If the clock is off, it "sees" the web site as bogus and will give the error.

35 years experience opinion. It is, however, just an opinion

rjent wrote:

JPG wrote:

rjent wrote:Try reading this: https://support.mozilla.org/en-US/kb/wh ... ecure-mean

Also, make sure your clock is correct. If the clock is not in time, it can cause this error.

JMHO

You have a question? LOL

The link is to firefox help page dealing with the connection issue of the OP
AND
the clock can cause a browser to "think" that a security issue is present, even though it is not. If the clock is off, it "sees" the web site as bogus and will give the error.

35 years experience opinion. It is, however, just an opinion

Interesting! A time difference from 'expected' leads to that conclusion? So for seeing an apple when you expect an orange means anything you want it to?

Programmers are 'supposed' to be cognizant of logic!



Gross extrapolation of questionable assumptions.

JPG wrote:
Programmers are 'supposed' to be cognizant of logic!

This is a perfectly cognizant solution for us programmers . It couldn't be more logical ....
There are infinite tests that could be done but you put a constraint on them.

rjent wrote:

JPG wrote:
Programmers are 'supposed' to be cognizant of logic!

This is a perfectly cognizant solution for us programmers . It couldn't be more logical ....
There are infinite tests that could be done but you put a constraint on them.

Welcome to alternate reality!

It is more common sense than alternate reality. Security certificates are dated for your protection from security hacks. If your clock is set wrong so the certificate date is expired by your clock, you get that error. So, checking the date on your clock is important.

garys wrote:It is more common sense than alternate reality. Security certificates are dated for your protection from security hacks. If your clock is set wrong so the certificate date is expired by your clock, you get that error. So, checking the date on your clock is important.

WHY is the 'user's' clock the 'reference'? (Or even relevant?)

Accurate time/date is defined elsewhere and should have been used when the 'period' started.

Common sense indeed!

JPG wrote:

garys wrote:It is more common sense than alternate reality. Security certificates are dated for your protection from security hacks. If your clock is set wrong so the certificate date is expired by your clock, you get that error. So, checking the date on your clock is important.

WHY is the 'user's' clock the 'reference'? (Or even relevant?)

Accurate time/date is defined elsewhere and should have been used when the 'period' started.

Common sense indeed!

In programming, certain assumptions have to be made. It is assumed that the user has the correct date. Normally that is the case. It is part of the metric that, although a variable, is usually pretty accurate. Common sense ....

rjent wrote:

JPG wrote:

garys wrote:It is more common sense than alternate reality. Security certificates are dated for your protection from security hacks. If your clock is set wrong so the certificate date is expired by your clock, you get that error. So, checking the date on your clock is important.

WHY is the 'user's' clock the 'reference'? (Or even relevant?)

Accurate time/date is defined elsewhere and should have been used when the 'period' started.

Common sense indeed!

In programming, certain assumptions have to be made. It is assumed that the user has the correct date. Normally that is the case. It is part of the metric that, although a variable, is usually pretty accurate. Common sense ....

Gotta disagree! Bad assumption!


But then all assumptions are fraught with pitfalls!


I observe far too many 'assumptions' of late that folks do not realize ARE assumptions.

The assumptions are often inaccurate for the issue at hand.

This might be a good time to run "Malwarebytes" Did that.

Or check into FireFo help. Did that too.

Also, make sure your clock is correct. If the clock is not in time, it can cause this error. And that.

Even deleted Firefox 57 and reinstalled it. Nothing works.

JPG wrote:Gotta disagree! Bad assumption!


But then all assumptions are fraught with pitfalls!


I observe far too many 'assumptions' of late that folks do not realize ARE assumptions.

The assumptions are often inaccurate for the issue at hand.

JPG wrote:How about returning to woodworking and SS stuff.