Tag Info

New answers tagged

1

I don't know if it would help at all, but you could try using different proxies such as http://vtunnel.com/ or http://free-proxyserver.com/.


1

From what i see http://outlook.com makes several redirects until it lands on https://login.live.com/login.srf?.... You can test where it stop (if it stops) with curl from command line curl -vL 'http://outlook.com' I tested also https://col125.mail.live.com/default.aspx, and it redirects also to https://login.live.com/login.srf I know this is not an ...


0

If you definitely want changes to be effective for all applications you're running now and and at all times you can imagine, edit the existing files in /etc/apache2/mods-available/, otherwise modularize as early as possible by separating into different files. The latter case should almost always be the way to go as you'll figure out much later that you can ...


0

I didn't try it, but I think a redirection should work. Try adding this after the server block where you configure the SSL connection on the IP : server { listen 443; server_name *; return 301 http://$http_host$request_uri; }


0

It only seems to be happening on this website. I think it is a bug in the site itself. And it only happens deep inside the connection, i.e. the critical phase of SSL (the initial handshake) is long done. You will probably fail to receive the data using another program or the browser too.


1

Without having more detail about the server my guess is that the server uses weak Diffie-Hellmann keys and that the SSL handshake will fail because OpenSSL was fixed to enforce stronger DH keys. The reason for this fix are the recent publication of the Logjam attack. From the Changelog SECURITY IMPROVEMENT: reject dh keys smaller than 768 bits ... ...


0

For Tomcat 6, in addition to the above, we also had to do the following: In server.xml connector, add: ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA" Source: ...


0

Certificates are a means of establishing trust. There are a number of certificate signing authorities which are trusted by browsers and other tools which use SSL/TLS certificates. When the make an encrypted connection they verify that the provide certificate was signed by a trusted certificate. A self-signed certificate is not signed by a trusted signer ...


1

This looks like a problem with ECDH support between client and server. If you exclude all ECDH ciphers it works: openssl s_client -connect ms.icometrix.com:443 -cipher 'DEFAULT:!ECDH' My guess is that the server croaks on some of the 25 ECC curves offered by the client. Browsers only offer few curves. OpenSSL 0.9.8 does not support any ECC yet and ...


1

It seems to be important that the name you enter when importing the certificate via Tools→Certificates matches the connect server in the XMPP account configuration. This is the only way I was able to get it to work for the same error.


0

After researching and working on this over the last couple days I got it to work, and the answer ended up being rather simple. I needed to set capath=/etc/ssl/certs/in my .curlrc file. This got curl working on the command line. To further get curl to work in R (where I first encountered the problem) I also needed to have ...


1

The certificates are from the package ca-certificates. The files in /etc/ssl/certs are actually symlinks managed by update-ca-certificates. See How does one remove a certificate authority's certificate from a system? if you want to remove some of them.


0

There are a couple things you can try. First off, have you tried creating a new ethereum-ethereum-<version>.list file for ethereum in /etc/apt/sources.list.d/ manually? I doubt that will make any difference if it's truly a verifcation error, but if apt is just being screwy that could do it. The line you would want to put in that file is something ...


2

I think you're asking too many questions at once. I'd recommend using nginx, as it is much, much easier to configure, especially when dealing with multiple Virtual Hosts. RewriteRule ^/(.*) http://127.0.0.1:5050/$1 This is a Regular Expression (regex) rule that matches against url the user has visited. This rule says 'Take all of the characters after ...



Top 50 recent answers are included