Turns out that I was trying to create a certificate from the .pfx instead of the .cer file. Lesson learned… .cer files are an X.509 certificate in binary form. They are DER encoded. .pfx files are container files. Also DER encoded. They contain not only certificates, but also private keys in encrypted form.
If the keystore is PKCS12 type (.pfx) you have to specify it with -storetype PKCS12 (line breaks added for readability): keytool -genkey -alias <desired certificate alias> -keystore <path to keystore.pfx> -storetype PKCS12 -keyalg RSA -storepass <password> -validity 730 -keysize 2048
The best idea we have found so far is to setup two Amazon EC2 micro machine instances with a small bit of nginx configuration. Then, provision two elastic IP addresses to point to those EC2 instances and point 2 A records to those IP addresses. This way, if something goes wrong on the hardware, you … Read more
You can use the Apple JCA Provider to use the OSX keychain as the java trust store. Just start the JVM with the following system property: -Djavax.net.ssl.trustStoreType=KeychainStore You can set this property for every started JVM using the JAVA_TOOL_OPTIONS environment variable, as described in hagrawal’s answer.
The SSL Cert is bound to the actual host name. If you have an SSL cert for “qa.example.com”, it won’t work on your machine named “dev.example.com”. Perhaps that’s the issue you’re having.
So the solution was to (first a backup) $ cd /etc/kubernetes/pki/ $ mv {apiserver.crt,apiserver-etcd-client.key,apiserver-kubelet-client.crt,front-proxy-ca.crt,front-proxy-client.crt,front-proxy-client.key,front-proxy-ca.key,apiserver-kubelet-client.key,apiserver.key,apiserver-etcd-client.crt} ~/ $ kubeadm init phase certs all –apiserver-advertise-address <IP> $ cd /etc/kubernetes/ $ mv {admin.conf,controller-manager.conf,kubelet.conf,scheduler.conf} ~/ $ kubeadm init phase kubeconfig all $ reboot then $ cp -i /etc/kubernetes/admin.conf $HOME/.kube/config that did the job for me and thanks for your hints … Read more
Yep, that’s the current behavior of Chrome but I wouldn’t expect it to continue to be the policy in the future. In firefox 4 (if you enable WebSockets in about:config) you will get a warning about the certificate. To approve the certificate you may also have to enter the WebSockets URL in the browser (substitute … Read more
You can choose to ignore the server certificate (at your own risk!). Configure your TortoiseGit in the following way. First of all open the TortoiseGit settings. Then: Select the Git configuration Open the global git configuration pressing “Edit systemwide gitconfig“ In the [http] section write: [http] sslVerify = false