I am unable to get on the TAILS official website through FF. WTF - they use FF ? It won't allow me to make an exception.
I downloaded the addon manually because it wouldn't let me automatically. The addon is just to verify the iso image. tails.boum.org has always been the official website. Why does it say insecure connection -- untrusted - phishing attempt and why does it not let me add it as an exception ? Never had a problem before .
被選擇的解決方法
philipp said
please try the bitdefender bit from How to troubleshoot security error codes on secure websites
That did the trick - thanks. Is that scan SSL function important though ? Should I turn it back on once I have the iso ?
從原來的回覆中察看解決方案 👍 0所有回覆 (18)
Is this the only site that has given you a secure connection error? It seems fine for me (see attached screenshot).
Could you check the certificate that you are getting served for the site. Since the "Add Exception" button is missing, you could try loading the following internal page in a separate tab (copy/paste the address) and then manually paste in the URL, then using Get Certificate and View Certificate.
chrome://pippki/content/exceptionDialog.xul
In particular, does your "Issued by" section match the attached image or does it show something else?
I tried that and it says unable to obtain ID status for this site. Cant figure out why. I disabled the signature requirements a while back to get something else to work but don't see how that could be related.
Could you check the certificate using a different browser? In Chrome, for example, click the lock in the address bar, then click Connection on the drop-down to get to the button to view the certificate.
And/or, if you created any exceptions recently, it would be worth checking some of those to see whether there's a pattern. You can access them using the padlock icon on the site, or check the Certificate Manager:
"3-bar" menu button (or Tools menu) > Options
In the left column click Advanced, then on the right, the Certificates mini-tab. Click the View Certificates button and select the Servers tab. Ignore the ones that have * under the server and look for sites you recognize having visited.
and yes no other connection error problems with other sites
arrghh
由 karelin 於
get to
I never use Chrome but guess I can try
In case this is a cache issue: How to clear the Firefox cache
OK via Chrome it says Your ID of website is verified by bitdefender. Then it says connection to tailsboum.org is encrypted using an obsolete cypher code suite TLS 1.2. Connection is encrypted using AES_128-GCM and uses RSA
Maybe I need to update bitdefender to update the encryption ?
But I was able to get to site via Chrome
still cant via FF which is where the add on to verify the iso is
please try the bitdefender bit from How to troubleshoot security error codes on secure websites
It probably is a good idea to update Bitdefender if it has been a while. But, I don't know whether that will make any difference. Bitdefender is one of several products that intercept web connections for filtering. Since you only have this problem with one site, I assume Firefox is set up to work with this filtering already (or you would have this issue with all secure sites).
Hmm, I'm not sure how to extract more information from Firefox on the reasons for its objections.
選擇的解決方法
philipp said
please try the bitdefender bit from How to troubleshoot security error codes on secure websites
That did the trick - thanks. Is that scan SSL function important though ? Should I turn it back on once I have the iso ?
jscher2000 said
Hmm, I'm not sure how to extract more information from Firefox on the reasons for its objectio
由 karelin 於
karelin said
philipp saidplease try the bitdefender bit from How to troubleshoot security error codes on secure websitesThat did the trick - thanks. Is that scan SSL function important though ? Should I turn it back on once I have the iso
由 karelin 於
karelin said
Is that scan SSL function important though ? Should I turn it back on once I have the iso
If it doesn't cause problems with other sites, and you don't find the performance penalty to be a problem, sure, turn it back on. It provides an extra layer of protection by checking every page before delivering it to Firefox.