Tag Info

Hot answers tagged

4

16:33:19 SMTP REPLY: 250-STARTTLS 16:34:31 SMTP REPLY: 250-XXXXXXXA It looks for me that there is something manipulating the connection, in that it explicitly replaces the announced STARTTLS feature from the server with some junk. This way the client thinks that STARTTLS is not supported and will often downgrade to plain text and thus the ...


2

First off, verify that you can connect from your local machine... you can just telnet to port 443, both on localhost (127.0.0.1) as well as on your machine's IP address. You should at least get an answer (ie. verification that there is a listener on that port). Example - This is what you do not want: $ telnet 127.0.0.1 443 Trying 127.0.0.1... telnet: ...


2

It will not be deleted because the certificate is on your server but it will be known that it expired and browsers will react appropriately, an unsecured site.


1

I see two things immediately wrong. You have a certificate for *.example.com, but you're accessing the site as https://example.com. A wildcard certificate won't be accepted for a parent domain. Either access it via https://www.example.com, or make a new certificate. You're using a SHA1 hash for the cert. This is considered bad. the -sha256 switch in ...


1

Either you or the CA had to create a private/public key pair, before the CA signed the public key. You need the private key in order to decrypt the TLS traffic. If you created the key pair, then you have the private key file. If the CA created it, then they have it and you need to get it from them.


1

You've got Yourself a SSL certificate for your domain, I think you have exported certificate without private key. A ".cert" (or ".cer" or ".crt") file usually contains a single certificate, alone and without any wrapping (no private key, no password protection, just the certificate). Ex- Some CAs store the certificate's private key in a Private Key (.pvk) ...


1

In general, SQL Server is using Windows SChannel services for transport encryption. So you should be able to restrict protocols and ciphersuites by manipulating the SCHANNEL-related registry keys in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL. For details, see KB245030 and the relevant section in Technet Documentation for ...



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