Joined: 29 Mar 01
with the latest update I am now getting this scary error message from Firefox:
"This Connection is Untrusted
You have asked Firefox to connect securely to givetocal.berkeley.edu, but we can't confirm that your connection is secure.
Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified.
What Should I Do?
If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn't continue."[/b]
Joined: 9 Jun 99
It's because since today the Seti web site runs in HTTPS, although any bookmarks you have using the HTTP address will also work.
The warning is there because the project uses a "self-signed" SSL certificate
(i.e. they don't have $500 to Verisign it).
You can ignore the warning.
A delusion starts like any other idea, as an egg. Identical on the outside, perfectly formed. - Legion.
Joined: 20 Jan 14
Follow these steps I think Helpful...
Go to Firefox > History > Clear recent history or (if no Firefox button is shown) go to Tools > Clear recent history.
Under "Time range to clear", select "Everything".
Now, click the arrow next to Details to toggle the Details list active.
From the details list, check Cache and Cookies and uncheck everything else.
Now click the Clear now button.
HERE IS ANOTHER ONE>......
1 - Edit -> Preferences
2 - Advanced tab/button
3 - Encryption tab
4 - View Certificates
5 - Servers tab
6 - [find cert]
7 - Delete button
8 - OK to confirm delete
9 - OK to close Certificate Manager
10 - Close to close Preferences
11 - Add Exception button
12 - Confirm Security Exception button grayed out?
If not, you are done (jump to step 22); if not, continue to step 13.
13 - Cancel Add Security Exception
14 - Edit -> Preferences again
15 - Privacy tab/button
16 - clear your recent history link
17 - Time range to clear (I suggest Everything)
18 - Unselect all; Select Cache [only]
19 - Clear Now button
20 - Close to close Preferences
21 - Add Exception
22 - Unselect Permanently store this Exception
23 - Confirm Security Exception
Joined: 14 Nov 01
Mozilla Firefox is NOT the trouble - Mozilla have taken steps by upgrading to prevent "Poodle Attacks" from Websites using the HTTPS connection.
The "Poodle Attacks" were known about some 20 years ago, and it was hoped that "sometime the problem would be fixed, but the problem has not gone away.
Mozilla Firefox has had several small "repair Upgrades over the last few weeks.
Mozilla Firefox v34 soon to come out will fix Firefox only.
Read more here: https://blog.mozilla.org/security/2014/10/14/the-poodle-attack-and-the-end-of-ssl-3-0/
And re Firefox v34 here: https://blog.mozilla.org/security/
Please note that it is not a Browser Problem - It is a problem inbuilt into the HTTPS code.
Further note: Other Browswer have the "Poodle Attack" problem, and several have yet to attend to it.
Full marks to Mozilla for promptly attending to the problem with Firefox - The best Browser of them all :)
Cheers from New Zealand[/url]
Joined: 16 May 16
This usually occurs due to the development of Https protocol and IPV6 Version of Ip (internet protocol) Addressess . This protocol is introduced to make the world wide web more secure as before
Joined: 9 Apr 02
That's not correct at all. The browser warning is due to the security certificate of the website. It has nothing to do with IPv6 or https itself.
©2019 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.