title: GIT HTTPS connection issue
body: <p>I searched around on stackoverflow and I haven't found anything that exactly answers this question so I wanted to ask it here and provide as much detail as possible about my problem.</p>
  
  <p>I just installed openSUSE 12.3, installed git and tried to clone into one of my repos using https.  This following command works on Ubuntu, Mac and other operating systems without issue but for some reason I am having trouble on SUSE.  </p>
  
  <p>When I run:</p>
  
  <pre><code>git clone https://username@mysite.com/git/myrepo.git
  </code></pre>
  
  <p>It hangs when "Cloning into 'myrepo'</p>
  
  <p>I have already disabled sslverify and this is how it works on other machines.  I don't believe this is an sslverify issue because when I don't have sslverify on other machines I get a specific error message regarding that.  In this case I just get a hang on 'Cloning into ...'</p>
  
  <p>I ran the following command to get more info:</p>
  
  <pre><code>GIT_CURL_VERBOSE=1 git clone https://username@mysite.com/git/myrepo.git
  </code></pre>
  
  <p>The output from that is:</p>
  
  <pre><code>Cloning into 'myrepo'...
  * Couldn't find host mysite.com in the .netrc file; using defaults
  * About to connect() to mysite.com port 443 (#0)
  *   Trying x.x.x.x...
  * Connected to mysite.com (x.x.x.x) port 443 (#0)
  * Connected to mysite.com (x.x.x.x) port 443 (#0)
  * successfully set certificate verify locations:
  *   CAfile: none
    CApath: /etc/ssl/certs/
  * Unknown SSL protocol error in connection to mysite.com:443 
  * Closing connection #0
  error: Unknown SSL protocol error in connection to mysite.com:443  while accessing https://username@mysite.com/git/myrepo.git/info/refs?service=git-upload-pack
  fatal: HTTP request failed
  </code></pre>
  
  <p>I obviously changed the username, IP and DNS name for the sake of this question.  </p>
  
  <p>I have heard older versions of curl had issues but this version is one of the newer ones.  The version of libcurl on Ubuntu is actually older so I still don't think this is a bug but not totally sure.  I don't have the privilege of changing this from HTTPS to SSH so that is not an alternative.  </p>
  
  <p>Thanks in advance.</p>