Hi
Yesterday I upgraded my version of firefox using zypper. Since then I am unable to browse hardly an sites
on the net, I get this error
Secure Connection Failed
An error occurred during a connection to signon.########.com. The security card or token does not exist, needs to be initialized, or has been removed. (Error code: sec_error_no_token)
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
Is it possible to reverse this upgrade. I have read about the fix on various sites but i do not have the expertise to do that.
I am using opensuse 12.3 Kde
Thank you for your help
On 2015-01-21 01:46, Subzero01 wrote:
>
> Hi
> Yesterday I upgraded my version of firefox using zypper. Since then I am
> unable to browse hardly an sites
> on the net, I get this error
You get that error on all sites? Because the error you post is specific
for one site.
> I am using opensuse 12.3 Kde
They announced discontinuation of 12.3 for about “Jan 4th 2015”, thus
I’m surprised that you could update your system at all.
Well, assuming the repo is still available, you need to start yast
package manager, select firefox, click on the version tab, which should
produce a list of available versions for the selected package. You have
to click on the one you want.
Sorry if the explanation is not simple enough… I must be tired. If you
don’t understand, just ask again and somebody else will surely be able
to explain better
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
I’ve not seen that error before but based purely on your error message I would strongly suspect the problem is the SSL version you’re using.
Background on the issue:
For the longest time SSL only offered the <option> to verify identity but about a half year ago malware was found to be widely used taking advantage whenever authentication wasn’t enabled. So, patches were released forcing authentication instead of allowing it to be only an option.
It sounds to me like your system’s software for whatever reason isn’t implementing the updated SSL correctly. Whether it’s the browser or your SSL package itself, I wouldn’t know. Or, it could be the website(s) which are poorly deployed. All the world, both servers and clients should be updated everywhere by now.
Bottom line as Carlos described is that it makes little sense to put effort into a losing cause using an unsupported OS version. Upgrade at least to 13.1 (which if you care will be Evergreen).
