I'm opening this issue of behalf of @bolera, per his reports in #7576

the builds.piwik.org server doesn't want to "talk" to us I think the issue can easily be solved by reconfiguring the server without changing any code in Piwik.

Explanation

However, I still think that your server is configured incorrectly.
Today I looked thru the curl bug tracker and found an option to enforce TLS1 in connection with that unspecified SSL error. Et voila, adding that option makes the connection work:
curl -o piwik.latest.tar.gz https://builds.piwik.org/piwik-latest.tar.gz -k -vvvv --tlsv1
Remove the --tlsv1 at the end and it fails. All other servers I tried and which also have SSL2 and SSL3 disabled (as yours) do not fail.
It seems it simply does not reply to an SSL2/non-TLS client hello, not even to tell "use TLS". Remember, so far it seems that builds.piwik.org is the only one that creates this error with curl.

Look at the differences (I removed the asterisks as the Markdown interprets them wrongly):

connect to a working server: SSLv2, Client hello (1): SSLv3, TLS handshake, Server hello (2):
connect to builds.piwik.org without --tlsv1: SSLv2, Client hello (1): -> fails, apparently with no server response
connect to builds.piwik.org with --tlsv1: SSLv3, TLS handshake, Client hello (1): SSLv3, TLS handshake, Server hello (2):
So, seems to me that builds.piwik.org should enforce TLS connections, but instead either doesn't reply or replies with a "no".