Tag Info

Hot answers tagged

1

certlm.msc will open the local machine's certificate store in the same gui style as certmgr.msc


1

Port 993 is not HTTPS but IMAPS and thus is not related to fiddler. There are several possibilities why the certificate is not acceptable, like wrong time on the system, SSL intercepting firewalls (often in conpanies), malware... If you need more help please add the details of the certificate to your question, especially the trust path. Edit: since the ...


1

I faced a similar issue with Comodo certificates recently when developing a script using Ruby. In the end it was that OpenSSL did not have it in the store, even though it looked like it did. To test this, download all of the Comodo intermediate certs and create a cert bundle something like this (you'll need to use different cert names depending on what you ...


1

OpenSSL at least through current (1.0.2a) has a bug where s_client with NO -CA{path,file} argument doesn't actually use the default truststore as it should, and thus fails to verify certs that are valid according to that truststore. (Also s_server and s_time, but caring about verification in those is rare.) See ...


1

openssl x509: If you mean the Subject and/or Issuer field(s), the simplest and most readable way (IMO) is openss x509 -in certpemfile -noout -text -nameopt multiline,show_type or if you want only the name field(s) change -text to -subject and/or -issuer. There are other formats, and if you want non-trivially encoded data to display usably you may need ...


1

It turns out that openssl verify doesn't allow multiple -CAfile parameters. Instead, I have to concatenate root.pem and intermediate.pem in a single file and pass that as a parameter. $ cat root.pem intermediate.pem > concat.pem $ openssl verify -CAfile concat.pem john.pem john.pem: OK


1

Maybe this thread has some insights: http://www.roundcubeforum.net/index.php?topic=22035.0



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