|
#9
| |||
| |||
| The dialogue says that the certificate on the server can't be validated by a third party. This could mean that the server admin created his own certificate, to enable encrypted sessions without having to pay for validation service. It could also mean that the servers certificate has expired. A third option is the one listed in the dialogue: it could be that someone has hijacked the server name, and has set up a rogue server for phishing purposes. |
|
#10
| ||||
| ||||
| Click 'Show certificate'. In the following window there'll be a checkbox named 'Always trust these certificates' ![]()
__________________ leo at code.coop Co-operatives are private corporations based on the values of self-help, self-responsibility, democracy, equality, equity and solidarity. |
|
#11
| |||
| |||
| hey KSV...that is incorrect...there is no option to always trust the certificate. I have attempted to add the certificate into different keychains (System, login, X509 Anchors) and chose to Always Trust the certificate...to no avail. I assume this may be the way to do it but possibly I'm not using keychain access correctly...any suggestions would be appreciated. Thanks. |
|
#12
| |||
| |||
| Certificates have dates to start/finish their "job". So, if your machine got an past/future date due to battery/reset problems, you will probably get this error message. Just that! best, rs |
|
#13
| ||||
| ||||
| Have you clicked on "Show certicate?" At least in Safari you can then select to trust this certificate. Edit: Sorry for the duplicate suggestion, I hadn't noticed page 2 of the thread. ![]() |