GitHub’s support determined the root of the issue right away: Two-factor authorization. To use GitHub over the shell with https, create an OAuth token. As the page notes, I did have to remove my username and password credentials from Keychain but with osx-keychain in place, the token is stored as the password and things work … Read more
This work-around worked for me: http://connect.microsoft.com/PowerShell/feedback/details/419466/new-webserviceproxy-needs-force-parameter-to-ignore-ssl-errors Basically, in your PowerShell script: add-type @” using System.Net; using System.Security.Cryptography.X509Certificates; public class TrustAllCertsPolicy : ICertificatePolicy { public bool CheckValidationResult( ServicePoint srvPoint, X509Certificate certificate, WebRequest request, int certificateProblem) { return true; } } “@ [System.Net.ServicePointManager]::CertificatePolicy = New-Object TrustAllCertsPolicy $result = Invoke-WebRequest -Uri “https://IpAddress/resource”
I fixed the problem by disabling HTTPS checks using the approach presented here: I put following code into the the ISomeService class: static { disableSslVerification(); } private static void disableSslVerification() { try { // Create a trust manager that does not validate certificate chains TrustManager[] trustAllCerts = new TrustManager[] {new X509TrustManager() { public java.security.cert.X509Certificate[] getAcceptedIssuers() … Read more
This is an old question, but I felt the need to provide my opinion on this important matter. There is so much misinformation here The OP never mentioned sending the password in clear over HTTP – only HTTPS, yet many seem to be responding to the question of sending a password over HTTP for some … Read more
I think the cleanest way is as described here on IIS-aid.com. It’s web.config only and so if you change server you don’t have to remember all the steps you went through with the 403.4 custom error page or other special permissions, it just works. <configuration> <system.webServer> <rewrite> <rules> <rule name=”HTTP to HTTPS redirect” stopProcessing=”true”> <match … Read more
According to documentation: to verify host or peer certificate you need to specify alternate certificates with the CURLOPT_CAINFO option or a certificate directory can be specified with the CURLOPT_CAPATH option. Also look at CURLOPT_SSL_VERIFYHOST: 1 to check the existence of a common name in the SSL peer certificate. 2 to check the existence of a … Read more
It’s pretty straightforward, using jdk6 at least… bash$ keytool -keystore foo.jks -genkeypair -alias foo \ -dname ‘CN=foo.example.com,L=Melbourne,ST=Victoria,C=AU’ Enter keystore password: Re-enter new password: Enter key password for (RETURN if same as keystore password): bash$ keytool -keystore foo.jks -exportcert -alias foo | \ openssl x509 -inform der -text Enter keystore password: asdasd Certificate: Data: Version: 3 … Read more
If the browser supports RFC 1808 Section 4, RFC 2396 Section 5.2, or RFC 3986 Section 5.2, then it will indeed use the page URL’s scheme for references that begin with “//”.
There’s the more general but perhaps not as helpful to you Wireshark. One of the SO server sites might be better suited for your question. In fact, it’s already been asked on SuperUser.
I solved it in XAMPP by uncommenting ;extension=php_openssl.dll in /apache/bin/php.ini despite phpinfo() telling me /php/php.ini was the loaded ini file. EDIT: I guess Ezra answer is the best solution directly adding the extension line to the appropriate ini file.