OSX 10.6.8 - SSL failure in Chrome due to cert authority missing
I'm at my parents house for the holiday period, and they've just revealed to me they've been getting this error every time they visit their banks website in Chrome (ERR_CERT_AUTHORITY_INVALID)
They have a late 2007 MacBook running Snow Leopard 10.6.8
I believe this is because the certificate authority "Entrust Root Certification Authority - G2" that the banks cert has been signed with is not in their System Roots keychain.
Am I correct in thinking this is because Apple are no longer issuing updates for OSX 10.6.8, so any new System Root certificates won't arrive?
The only "workaround" I've been able to offer them, outside of throwing the MacBook in the bin, is to make them use Firefox instead as that doesn't use the OSX keychain. But they're so used to Chrome, it's going to be a pain explaining to them the change.
Any other workarounds anyone can think of?
macos google-chrome security osx-snow-leopard certificate
asked Dec 29 '15 at 12:45
djhworlddjhworld
1308
add a comment |
I'm at my parents house for the holiday period, and they've just revealed to me they've been getting this error every time they visit their banks website in Chrome (ERR_CERT_AUTHORITY_INVALID)
They have a late 2007 MacBook running Snow Leopard 10.6.8
I believe this is because the certificate authority "Entrust Root Certification Authority - G2" that the banks cert has been signed with is not in their System Roots keychain.
Am I correct in thinking this is because Apple are no longer issuing updates for OSX 10.6.8, so any new System Root certificates won't arrive?
The only "workaround" I've been able to offer them, outside of throwing the MacBook in the bin, is to make them use Firefox instead as that doesn't use the OSX keychain. But they're so used to Chrome, it's going to be a pain explaining to them the change.
Any other workarounds anyone can think of?
macos google-chrome security osx-snow-leopard certificate
asked Dec 29 '15 at 12:45
djhworlddjhworld
1308
What is the website they are trying to get to?
– Tim
Dec 29 '15 at 14:06
tescobank.com/sss/auth - it looks like they changed their root on the 22nd October, which has caused this.
– djhworld
Dec 29 '15 at 14:35
the site loaded perfect for me with that new cert issues on the 22nd. The mac is probably trying to use the old one it has cached. Go to keychain, and see if you can find the old one under system. then remove it.
– Tim
Dec 29 '15 at 15:23
I had a look unders system but it wasn't there under "Login", "System" or "System Roots". On my Mac (running el capitan) I can see it under "System Roots", leading me to believe it probably came by a system update
– djhworld
Dec 29 '15 at 16:00
Possible duplicate of Suppress Google Chrome's "Your Connection is Not Private" for specific Address?
– kenorb
Jan 12 '16 at 10:09
add a comment |
I'm at my parents house for the holiday period, and they've just revealed to me they've been getting this error every time they visit their banks website in Chrome (ERR_CERT_AUTHORITY_INVALID)
They have a late 2007 MacBook running Snow Leopard 10.6.8
I believe this is because the certificate authority "Entrust Root Certification Authority - G2" that the banks cert has been signed with is not in their System Roots keychain.
Am I correct in thinking this is because Apple are no longer issuing updates for OSX 10.6.8, so any new System Root certificates won't arrive?
The only "workaround" I've been able to offer them, outside of throwing the MacBook in the bin, is to make them use Firefox instead as that doesn't use the OSX keychain. But they're so used to Chrome, it's going to be a pain explaining to them the change.
Any other workarounds anyone can think of?
macos google-chrome security osx-snow-leopard certificate
asked Dec 29 '15 at 12:45
djhworlddjhworld
1308
I'm at my parents house for the holiday period, and they've just revealed to me they've been getting this error every time they visit their banks website in Chrome (ERR_CERT_AUTHORITY_INVALID)
They have a late 2007 MacBook running Snow Leopard 10.6.8
I believe this is because the certificate authority "Entrust Root Certification Authority - G2" that the banks cert has been signed with is not in their System Roots keychain.
Am I correct in thinking this is because Apple are no longer issuing updates for OSX 10.6.8, so any new System Root certificates won't arrive?
The only "workaround" I've been able to offer them, outside of throwing the MacBook in the bin, is to make them use Firefox instead as that doesn't use the OSX keychain. But they're so used to Chrome, it's going to be a pain explaining to them the change.
Any other workarounds anyone can think of?
macos google-chrome security osx-snow-leopard certificate
macos google-chrome security osx-snow-leopard certificate
asked Dec 29 '15 at 12:45
djhworlddjhworld
1308
asked Dec 29 '15 at 12:45
djhworlddjhworld
1308
asked Dec 29 '15 at 12:45
djhworlddjhworld
1308
asked Dec 29 '15 at 12:45
djhworlddjhworld
1308
asked Dec 29 '15 at 12:45
djhworlddjhworld
1308
1308
What is the website they are trying to get to?
– Tim
Dec 29 '15 at 14:06
tescobank.com/sss/auth - it looks like they changed their root on the 22nd October, which has caused this.
– djhworld
Dec 29 '15 at 14:35
the site loaded perfect for me with that new cert issues on the 22nd. The mac is probably trying to use the old one it has cached. Go to keychain, and see if you can find the old one under system. then remove it.
– Tim
Dec 29 '15 at 15:23
I had a look unders system but it wasn't there under "Login", "System" or "System Roots". On my Mac (running el capitan) I can see it under "System Roots", leading me to believe it probably came by a system update
– djhworld
Dec 29 '15 at 16:00
Possible duplicate of Suppress Google Chrome's "Your Connection is Not Private" for specific Address?
– kenorb
Jan 12 '16 at 10:09
add a comment |
What is the website they are trying to get to?
– Tim
Dec 29 '15 at 14:06
tescobank.com/sss/auth - it looks like they changed their root on the 22nd October, which has caused this.
– djhworld
Dec 29 '15 at 14:35
the site loaded perfect for me with that new cert issues on the 22nd. The mac is probably trying to use the old one it has cached. Go to keychain, and see if you can find the old one under system. then remove it.
– Tim
Dec 29 '15 at 15:23
I had a look unders system but it wasn't there under "Login", "System" or "System Roots". On my Mac (running el capitan) I can see it under "System Roots", leading me to believe it probably came by a system update
– djhworld
Dec 29 '15 at 16:00
Possible duplicate of Suppress Google Chrome's "Your Connection is Not Private" for specific Address?
– kenorb
Jan 12 '16 at 10:09
What is the website they are trying to get to?
– Tim
Dec 29 '15 at 14:06
What is the website they are trying to get to?
– Tim
Dec 29 '15 at 14:06
tescobank.com/sss/auth - it looks like they changed their root on the 22nd October, which has caused this.
– djhworld
Dec 29 '15 at 14:35
tescobank.com/sss/auth - it looks like they changed their root on the 22nd October, which has caused this.
– djhworld
Dec 29 '15 at 14:35
the site loaded perfect for me with that new cert issues on the 22nd. The mac is probably trying to use the old one it has cached. Go to keychain, and see if you can find the old one under system. then remove it.
– Tim
Dec 29 '15 at 15:23
the site loaded perfect for me with that new cert issues on the 22nd. The mac is probably trying to use the old one it has cached. Go to keychain, and see if you can find the old one under system. then remove it.
– Tim
Dec 29 '15 at 15:23
I had a look unders system but it wasn't there under "Login", "System" or "System Roots". On my Mac (running el capitan) I can see it under "System Roots", leading me to believe it probably came by a system update
– djhworld
Dec 29 '15 at 16:00
I had a look unders system but it wasn't there under "Login", "System" or "System Roots". On my Mac (running el capitan) I can see it under "System Roots", leading me to believe it probably came by a system update
– djhworld
Dec 29 '15 at 16:00
Possible duplicate of Suppress Google Chrome's "Your Connection is Not Private" for specific Address?
– kenorb
Jan 12 '16 at 10:09
Possible duplicate of Suppress Google Chrome's "Your Connection is Not Private" for specific Address?
– kenorb
Jan 12 '16 at 10:09
add a comment |
2 Answers
2
active
oldest
votes
Chrome support is ending for 10.6 in April. They will either need to update to 10.9 or use a different browser such as firefox to try and stay secure.
Try opening the page in incognito mode
Open the page in an incognito window. If it works there, it means one of your extensions is causing the security problem and you should remove it. Learn how to turn off an extension.
Temporarily turn off your antivirus (if applicable)
If you have any antivirus software on your computer that provides "HTTPS protection" or "HTTPS scanning," it might be interfering with the browser's ability to provide security. Turn it off for now to see if it fixes the problem. If that works, you'll need to turn off this feature to use secure sites.
Remember to turn it back on.
Updates
Make sure Chrome is updates as well as the Mac itself.
Clear Certificates
Go to Utilities-Keychain
In system, find the old cached key and remove it. Should be under system and not system roots.
answered Dec 29 '15 at 13:22
TimTim
437210
Sadly their Mac is a late 2007 edition MacBook, they can't upgrade to any of the newer operating systems as Apple don't support it.
– djhworld
Dec 29 '15 at 14:00
Well darn. What version of chrome is installed? It is possible that an out of date chrome wont allow it. The biggest cause to this issue is the website using a weak/outdated method of cryptography.
– Tim
Dec 29 '15 at 14:59
I don't have the laptop to hand, but it's in the latest version (47.x) and I checked to see if there were updates available - which it said it was the latest version. The problem is Chrome uses the OSX keychain to manage certificates, whereas Firefox has its own keystore.
– djhworld
Dec 29 '15 at 15:18
Also I tried the incognito mode trick to make sure it wasn't extensions or anything interfering, but same issue. They don't run antivirus. As a temporary measure I went to the Entrust website and downloaded/installed then trusted the certificate myself, but I don't believe this is a good idea to be installing root certs in your user keychain! I think problem is this Root CA is a recent one that would normally come with OSX updates - but Apple don't provide updates for snow leopard anymore.
– djhworld
Dec 29 '15 at 15:23
add a comment |
You could upgrade them to Lion, which is still current and supported.
If they will not update the OS, and you know the certificate, why not download the current root cert (from here) and install the cert.
answered Jan 9 '16 at 16:14
mharrmharr
1212
I took the secondary action and installed the root CA in the end, but this is a hack imo, I don't believe it's appropriate to be installing root certs yourself! In the meantime I'm going to give my parents my 2011 MacBook PRO as Apple still support that
– djhworld
Jan 12 '16 at 13:07
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1019262%2fosx-10-6-8-ssl-failure-in-chrome-due-to-cert-authority-missing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Chrome support is ending for 10.6 in April. They will either need to update to 10.9 or use a different browser such as firefox to try and stay secure.
Try opening the page in incognito mode
Open the page in an incognito window. If it works there, it means one of your extensions is causing the security problem and you should remove it. Learn how to turn off an extension.
Temporarily turn off your antivirus (if applicable)
If you have any antivirus software on your computer that provides "HTTPS protection" or "HTTPS scanning," it might be interfering with the browser's ability to provide security. Turn it off for now to see if it fixes the problem. If that works, you'll need to turn off this feature to use secure sites.
Remember to turn it back on.
Updates
Make sure Chrome is updates as well as the Mac itself.
Clear Certificates
Go to Utilities-Keychain
In system, find the old cached key and remove it. Should be under system and not system roots.
answered Dec 29 '15 at 13:22
TimTim
437210
Sadly their Mac is a late 2007 edition MacBook, they can't upgrade to any of the newer operating systems as Apple don't support it.
– djhworld
Dec 29 '15 at 14:00
Well darn. What version of chrome is installed? It is possible that an out of date chrome wont allow it. The biggest cause to this issue is the website using a weak/outdated method of cryptography.
– Tim
Dec 29 '15 at 14:59
I don't have the laptop to hand, but it's in the latest version (47.x) and I checked to see if there were updates available - which it said it was the latest version. The problem is Chrome uses the OSX keychain to manage certificates, whereas Firefox has its own keystore.
– djhworld
Dec 29 '15 at 15:18
Also I tried the incognito mode trick to make sure it wasn't extensions or anything interfering, but same issue. They don't run antivirus. As a temporary measure I went to the Entrust website and downloaded/installed then trusted the certificate myself, but I don't believe this is a good idea to be installing root certs in your user keychain! I think problem is this Root CA is a recent one that would normally come with OSX updates - but Apple don't provide updates for snow leopard anymore.
– djhworld
Dec 29 '15 at 15:23
add a comment |
Chrome support is ending for 10.6 in April. They will either need to update to 10.9 or use a different browser such as firefox to try and stay secure.
Try opening the page in incognito mode
Open the page in an incognito window. If it works there, it means one of your extensions is causing the security problem and you should remove it. Learn how to turn off an extension.
Temporarily turn off your antivirus (if applicable)
If you have any antivirus software on your computer that provides "HTTPS protection" or "HTTPS scanning," it might be interfering with the browser's ability to provide security. Turn it off for now to see if it fixes the problem. If that works, you'll need to turn off this feature to use secure sites.
Remember to turn it back on.
Updates
Make sure Chrome is updates as well as the Mac itself.
Clear Certificates
Go to Utilities-Keychain
In system, find the old cached key and remove it. Should be under system and not system roots.
answered Dec 29 '15 at 13:22
TimTim
437210
Sadly their Mac is a late 2007 edition MacBook, they can't upgrade to any of the newer operating systems as Apple don't support it.
– djhworld
Dec 29 '15 at 14:00
Well darn. What version of chrome is installed? It is possible that an out of date chrome wont allow it. The biggest cause to this issue is the website using a weak/outdated method of cryptography.
– Tim
Dec 29 '15 at 14:59
I don't have the laptop to hand, but it's in the latest version (47.x) and I checked to see if there were updates available - which it said it was the latest version. The problem is Chrome uses the OSX keychain to manage certificates, whereas Firefox has its own keystore.
– djhworld
Dec 29 '15 at 15:18
Also I tried the incognito mode trick to make sure it wasn't extensions or anything interfering, but same issue. They don't run antivirus. As a temporary measure I went to the Entrust website and downloaded/installed then trusted the certificate myself, but I don't believe this is a good idea to be installing root certs in your user keychain! I think problem is this Root CA is a recent one that would normally come with OSX updates - but Apple don't provide updates for snow leopard anymore.
– djhworld
Dec 29 '15 at 15:23
add a comment |
Chrome support is ending for 10.6 in April. They will either need to update to 10.9 or use a different browser such as firefox to try and stay secure.
Try opening the page in incognito mode
Open the page in an incognito window. If it works there, it means one of your extensions is causing the security problem and you should remove it. Learn how to turn off an extension.
Temporarily turn off your antivirus (if applicable)
If you have any antivirus software on your computer that provides "HTTPS protection" or "HTTPS scanning," it might be interfering with the browser's ability to provide security. Turn it off for now to see if it fixes the problem. If that works, you'll need to turn off this feature to use secure sites.
Remember to turn it back on.
Updates
Make sure Chrome is updates as well as the Mac itself.
Clear Certificates
Go to Utilities-Keychain
In system, find the old cached key and remove it. Should be under system and not system roots.
answered Dec 29 '15 at 13:22
TimTim
437210
Chrome support is ending for 10.6 in April. They will either need to update to 10.9 or use a different browser such as firefox to try and stay secure.
Try opening the page in incognito mode
Open the page in an incognito window. If it works there, it means one of your extensions is causing the security problem and you should remove it. Learn how to turn off an extension.
Temporarily turn off your antivirus (if applicable)
If you have any antivirus software on your computer that provides "HTTPS protection" or "HTTPS scanning," it might be interfering with the browser's ability to provide security. Turn it off for now to see if it fixes the problem. If that works, you'll need to turn off this feature to use secure sites.
Remember to turn it back on.
Updates
Make sure Chrome is updates as well as the Mac itself.
Clear Certificates
Go to Utilities-Keychain
In system, find the old cached key and remove it. Should be under system and not system roots.
answered Dec 29 '15 at 13:22
TimTim
437210
edited Dec 29 '15 at 15:25
answered Dec 29 '15 at 13:22
TimTim
437210
answered Dec 29 '15 at 13:22
TimTim
437210
answered Dec 29 '15 at 13:22
TimTim
437210
437210
Sadly their Mac is a late 2007 edition MacBook, they can't upgrade to any of the newer operating systems as Apple don't support it.
– djhworld
Dec 29 '15 at 14:00
Well darn. What version of chrome is installed? It is possible that an out of date chrome wont allow it. The biggest cause to this issue is the website using a weak/outdated method of cryptography.
– Tim
Dec 29 '15 at 14:59
I don't have the laptop to hand, but it's in the latest version (47.x) and I checked to see if there were updates available - which it said it was the latest version. The problem is Chrome uses the OSX keychain to manage certificates, whereas Firefox has its own keystore.
– djhworld
Dec 29 '15 at 15:18
Also I tried the incognito mode trick to make sure it wasn't extensions or anything interfering, but same issue. They don't run antivirus. As a temporary measure I went to the Entrust website and downloaded/installed then trusted the certificate myself, but I don't believe this is a good idea to be installing root certs in your user keychain! I think problem is this Root CA is a recent one that would normally come with OSX updates - but Apple don't provide updates for snow leopard anymore.
– djhworld
Dec 29 '15 at 15:23
add a comment |
Sadly their Mac is a late 2007 edition MacBook, they can't upgrade to any of the newer operating systems as Apple don't support it.
– djhworld
Dec 29 '15 at 14:00
Well darn. What version of chrome is installed? It is possible that an out of date chrome wont allow it. The biggest cause to this issue is the website using a weak/outdated method of cryptography.
– Tim
Dec 29 '15 at 14:59
I don't have the laptop to hand, but it's in the latest version (47.x) and I checked to see if there were updates available - which it said it was the latest version. The problem is Chrome uses the OSX keychain to manage certificates, whereas Firefox has its own keystore.
– djhworld
Dec 29 '15 at 15:18
Also I tried the incognito mode trick to make sure it wasn't extensions or anything interfering, but same issue. They don't run antivirus. As a temporary measure I went to the Entrust website and downloaded/installed then trusted the certificate myself, but I don't believe this is a good idea to be installing root certs in your user keychain! I think problem is this Root CA is a recent one that would normally come with OSX updates - but Apple don't provide updates for snow leopard anymore.
– djhworld
Dec 29 '15 at 15:23
Sadly their Mac is a late 2007 edition MacBook, they can't upgrade to any of the newer operating systems as Apple don't support it.
– djhworld
Dec 29 '15 at 14:00
Sadly their Mac is a late 2007 edition MacBook, they can't upgrade to any of the newer operating systems as Apple don't support it.
– djhworld
Dec 29 '15 at 14:00
Well darn. What version of chrome is installed? It is possible that an out of date chrome wont allow it. The biggest cause to this issue is the website using a weak/outdated method of cryptography.
– Tim
Dec 29 '15 at 14:59
Well darn. What version of chrome is installed? It is possible that an out of date chrome wont allow it. The biggest cause to this issue is the website using a weak/outdated method of cryptography.
– Tim
Dec 29 '15 at 14:59
I don't have the laptop to hand, but it's in the latest version (47.x) and I checked to see if there were updates available - which it said it was the latest version. The problem is Chrome uses the OSX keychain to manage certificates, whereas Firefox has its own keystore.
– djhworld
Dec 29 '15 at 15:18
I don't have the laptop to hand, but it's in the latest version (47.x) and I checked to see if there were updates available - which it said it was the latest version. The problem is Chrome uses the OSX keychain to manage certificates, whereas Firefox has its own keystore.
– djhworld
Dec 29 '15 at 15:18
Also I tried the incognito mode trick to make sure it wasn't extensions or anything interfering, but same issue. They don't run antivirus. As a temporary measure I went to the Entrust website and downloaded/installed then trusted the certificate myself, but I don't believe this is a good idea to be installing root certs in your user keychain! I think problem is this Root CA is a recent one that would normally come with OSX updates - but Apple don't provide updates for snow leopard anymore.
– djhworld
Dec 29 '15 at 15:23
Also I tried the incognito mode trick to make sure it wasn't extensions or anything interfering, but same issue. They don't run antivirus. As a temporary measure I went to the Entrust website and downloaded/installed then trusted the certificate myself, but I don't believe this is a good idea to be installing root certs in your user keychain! I think problem is this Root CA is a recent one that would normally come with OSX updates - but Apple don't provide updates for snow leopard anymore.
– djhworld
Dec 29 '15 at 15:23
add a comment |
You could upgrade them to Lion, which is still current and supported.
If they will not update the OS, and you know the certificate, why not download the current root cert (from here) and install the cert.
answered Jan 9 '16 at 16:14
mharrmharr
1212
I took the secondary action and installed the root CA in the end, but this is a hack imo, I don't believe it's appropriate to be installing root certs yourself! In the meantime I'm going to give my parents my 2011 MacBook PRO as Apple still support that
– djhworld
Jan 12 '16 at 13:07
add a comment |
You could upgrade them to Lion, which is still current and supported.
If they will not update the OS, and you know the certificate, why not download the current root cert (from here) and install the cert.
answered Jan 9 '16 at 16:14
mharrmharr
1212
I took the secondary action and installed the root CA in the end, but this is a hack imo, I don't believe it's appropriate to be installing root certs yourself! In the meantime I'm going to give my parents my 2011 MacBook PRO as Apple still support that
– djhworld
Jan 12 '16 at 13:07
add a comment |
You could upgrade them to Lion, which is still current and supported.
If they will not update the OS, and you know the certificate, why not download the current root cert (from here) and install the cert.
answered Jan 9 '16 at 16:14
mharrmharr
1212
You could upgrade them to Lion, which is still current and supported.
If they will not update the OS, and you know the certificate, why not download the current root cert (from here) and install the cert.
answered Jan 9 '16 at 16:14
mharrmharr
1212
answered Jan 9 '16 at 16:14
mharrmharr
1212
answered Jan 9 '16 at 16:14
mharrmharr
1212
answered Jan 9 '16 at 16:14
mharrmharr
1212
1212
I took the secondary action and installed the root CA in the end, but this is a hack imo, I don't believe it's appropriate to be installing root certs yourself! In the meantime I'm going to give my parents my 2011 MacBook PRO as Apple still support that
– djhworld
Jan 12 '16 at 13:07
add a comment |
I took the secondary action and installed the root CA in the end, but this is a hack imo, I don't believe it's appropriate to be installing root certs yourself! In the meantime I'm going to give my parents my 2011 MacBook PRO as Apple still support that
– djhworld
Jan 12 '16 at 13:07
I took the secondary action and installed the root CA in the end, but this is a hack imo, I don't believe it's appropriate to be installing root certs yourself! In the meantime I'm going to give my parents my 2011 MacBook PRO as Apple still support that
– djhworld
Jan 12 '16 at 13:07
I took the secondary action and installed the root CA in the end, but this is a hack imo, I don't believe it's appropriate to be installing root certs yourself! In the meantime I'm going to give my parents my 2011 MacBook PRO as Apple still support that
– djhworld
Jan 12 '16 at 13:07
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1019262%2fosx-10-6-8-ssl-failure-in-chrome-due-to-cert-authority-missing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What is the website they are trying to get to?
– Tim
Dec 29 '15 at 14:06
tescobank.com/sss/auth - it looks like they changed their root on the 22nd October, which has caused this.
– djhworld
Dec 29 '15 at 14:35
the site loaded perfect for me with that new cert issues on the 22nd. The mac is probably trying to use the old one it has cached. Go to keychain, and see if you can find the old one under system. then remove it.
– Tim
Dec 29 '15 at 15:23
I had a look unders system but it wasn't there under "Login", "System" or "System Roots". On my Mac (running el capitan) I can see it under "System Roots", leading me to believe it probably came by a system update
– djhworld
Dec 29 '15 at 16:00
Possible duplicate of Suppress Google Chrome's "Your Connection is Not Private" for specific Address?
– kenorb
Jan 12 '16 at 10:09