Tag Info

Hot answers tagged

3

The signature you are referring to is found in the SSL Certificate, not the CSR. This is why you can't find the option. :) What you need to do is make sure your Certificate Issuer is generating your certs based off of your CSR with the correct options. The exact method to do so changes from CA to CA. For example, GoDaddy generally have a drop-down box on ...


3

Your own certificate is signed by exactly one certificate. This means that your certificate is at one end of exactly one of these Thawte chains, you would need a different certificate to be in the other chain (one signed by the intermediate certificate from that chain). As for the signature of the root certificate being SHA-1, SHA-2 or something else it is ...


2

The interactive genkey command wont give you the option to change the defaults, but you should be able to update your /etc/pki/tls/openssl.cnf if you really want to use that command. Change: default_md = sha1 To: default_md = sha256 Or you can use the openssl command direct. If the hashing algorithm is set to SHA1 by ...


1

I have resolved this issue. I was getting the error: ERROR 2026 (HY000): SSL connection error: ASN: bad other signature confirmation when I was connecting with HeidiSQL version 8.3.0.4694. I failed to mention that as I thought it was not relevant. I tried connecting using the mysqli and ssl_set function in PHP 5.6.2, and that worked. So the problem was ...


1

The Crypt32.dll 5.131.3790.5235 version fixes the issue (after a reboot). It is available at http://support2.microsoft.com/kb/2868626 The previous version was 5.131.3790.5014 version and it did not fix the issue. According to this post (https://mendel129.wordpress.com/tag/crypt32-dll/), there are two variants of the 5014 version: one from Windows Update ...


1

Check if the file is on the QFE branch. If it is on RTM or GDR then you need to push it to QFE to make the bug fix effective.


1

It turns out that Thawte's site is just confusing for people who don't work with SSL certs a lot. Despite the fact that there are two certificates shown for SSL123 SHA2 under SHA-1 Root, you only need the first one. The second certificate is the SHA-1 root, and you don't need it concatenated with your site's cert for deployment to nginx. Just use the first ...



Only top voted, non community-wiki answers of a minimum length are eligible