Hot answers tagged

2

You can set this host machine to use and present your (existing, purchased) externally-verified SSL certificate thus (instructions probably also work for Windows 8 & 8.1, may or may not work for Windows 7) (parts of this based on a Microsoft KB 2001849): First, you need to have purchased a genuine verified ssl certificate. If you have this certificate ...


1

Behind a firewall, ...github ... Chrome uses our certificate for this access. Based on this description I assume that "our" certificate is not the original certificate for Github but that you are using a firewall with SSL inspection which generates its own ("our") certificate to a man in the middle the connection. The CA in the firewall which issued this ...


1

When you use chrome and access Github over HTTPS, you are just verifying Github's certificate chain against built-in root certs in your browser and in Windows. Under the covers, Gitextensions uses msysgit, which does not consult Windows trust certificates when building the certificate chain. From the error, it appears that the root certificate used by ...


1

Here are the basic steps I use: Get a valid certificate that for the host, (it doesn't have to come from an external CA, but all your machines have to trust it). Make sure it has the correct hostname, I had problems with wildcard certs. Install the cert on the host, like: certutil.exe -p myPassword -importPFX c:\mycert.pfx noExport find the thumbprint ...


1

The reason for the Certificate Error in the browser, inspite of adding the certificate to the 'Trusted Root Certification Authorities' is because the certificate was issued for <machinename>.<domain>.com. I was opening the site using just <machinename>. When opening the sites using <machinename>.<domain>.com, no certificate ...


1

If looking just a little bit further (one click) from the article you refer to one will find the documentation of all parameters usable for http_port, which includes: key= Path to SSL private key file (PEM format) if not specified, the certificate file is assumed to be a combined certificate and key file.


1

You need the private key corresponding to the certificate; without that, you cannot create a .p12 file or use the certificate to sign your app. The private key is not included in a .cer file, and it's impractical to compute it from anything in the .cer file. The private key should have been created when you created the certificate; exactly where it was ...


1

First thing's first: DO NOT DO THE FOLLOWING IF YOU DO NOT TRUST THE CERTIFICATE ISSUER Doing this a man-in-the-middle to see all of your communications. This fix should only be employed if you are in a situation which warrants it, not if you're sitting at a coffee shop and having problems connecting to things. That said... The first step is to acquire ...



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