Windows 10: email matching with certificates

To Whom:


I was asked to re-post my issue here.


Microsoft has previous answers to turning off e-mail matching for certificates in Outlook. However, the recommendations are for versions 2003 thru 2013. For Outlook 365 with Windows 10, I cannot find how toturn-off name checking. The registry key used to be called SupressNameChecks and was located at Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\xx.0\Outlook\Security wherexx is your office version.


For windows 10 with outlook 365, setting this registry key here has no affect. Can someone please tell me where to edit the registry?


Also, from a security standpoint, many people need certs for identity validation andemail address matching is NOT required or needed.

:)

 

N8 certificates not trusted/don't match the name

Well I worked out for myself how to verify the certificates are genuine:

• Using a desktop computer
• Go to the page with the certificates
• Select a certificate
• It will say either:
  • Certificate already exists - this confirms that the certificate on the website matches one already in your browser, which we already trust, therefore the certificate on the website is trustworthy
  • Asks if you want to install the certificate, DON'T.
    • First view the certificate details.
    • Copy the certificate serial number or SHA1/SHA256/MD5/etc hash
    • Paste this into a search engine
    • If another website that you trust lists the certificate, e.g. your phone manufacturer or another trusted website (preferably a secure website, therefore you have confidence the website is genuine), then you can trust the certificate
    • If no trustworthy sites are returned in the search then try another hash or serial number
    • If you can't find any trustworthy sites listing the certificate then I suggest you don't trust it.
• Finally, if you decide you trust a certificate then you can download and install on your phone.

 

email certificates on e6 after belle update

Dear Pastmac, Welcome to the Nokia forums, sorry youa re having this frustrating problem!



Some email providers provide secure email connections using the same type of SSL connection commonly used to provide secure web site connections for banking or online purchases.



SSL connections use Certificates to establish what is called Trust between the program being used (web browser, email client, or other type of application) and the server. For the trust to be automatic, the client program must be able to validate
the Certificate that the server has. If the client program cannot validate the Certificate of the server, it will report a
Missing Certificate error.

A server's Certificate can be of two types:

• Self-signed Certificate
• Certification Authority (CA)-signed Certificate

A Self-signed Certificate is created using a Certificate generating program, without needing to go to an outside agency. This is fast and inexpensive, but requires additional steps to use, because client programs cannot validate such a certificate
without information they do not have.

The only way to allow the device to validate a self-signed certificate is to install the certificate on the device. To do this, browse to a secure web page using the same certificate (normally hosted on the same server, such as a secure web
mail page in the case of a certificate for an email server) and accept the certificate when prompted what to do with it. Normally, you will also be asked what to allow it to be used for. Accepting all the uses is normally safe, and will allow email to work
as well.

A Certification Authority-signed certificate is created using a Certificate generating program just like the self-signed Certificate, but is then sent to a Certification Authority. The Certification Authority adds their own digital signature
to the Certificate. This allows the client application to test that the certificate has not been altered since the Certification Authority signed it, and so it can be trusted automatically without further difficulties.

You can still get the same error, however. This is because the client application needs to have a special Certificate (called a Root Certificate) from the Certification Authority in order to determine that the digital signature on a Certificate
is valid. There are many different Certification Authorities, each which may have several different Root Certificates with different properties for different purposes. Not all devices automatically have all valid Root Certificates from all Certification
Authorities. In addition, all Certificates have expiry dates beyond which they are no longer trusted. (Eventually, this will cause a device which is not receiving firmware updates to experience this error for all secure connections using SSL.)

If a Certification Authority-signed Certificate is not accepted, there are two ways to correct the issue:

• As with a self-signed certificate, surf to a secure web page on the same server, and accept the certificate. The certificate will then be trusted and treated as valid.
  
• Install the Root Certificate that the CA used to sign the Certificate. You will need to find out which CA it is from the site operators.
  

I hope this helps

 

email certificates on e6 after belle update

sheldrick, sorry but what you are saying here is **bleep**. I have the same problem on my E7-00 after updating to Belle. I could understand if it had problems with certificates from some obscure email provider, but it does not accept the certificates from
Gmail, Yahoo and 1and1.



This is obvously a bug in Belle, that needs to be addressed. Even if the certificate is not up to date, as the message says, we should be able to accept the certificate permanently, not just 'this time only' every 5 minutes.

The steps you describe do not apply to mail - since all we get is the message, not a certificate with a web address, so we can accept it as you suggest.