From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Thomas Gemmrich <Thomas.Gemmrich@vzch.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git clone error : RPC failed; curl 56 OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 0
Date: Wed, 5 Jun 2024 22:01:35 +0000 [thread overview]
Message-ID: <ZmDgP57-5AS8B6Pc@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <80a4c8c85415406c947ee588ef223ce6@vzch.com>
[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]
On 2024-06-05 at 06:06:33, Thomas Gemmrich wrote:
> Thank you for filling out a Git bug report!
> Please answer the following questions to help us understand your issue.
>
> What did you do before the bug happened? (Steps to reproduce your issue)
> git clone from azure.devops.com - server behind corporate proxy
>
> What did you expect to happen? (Expected behavior)
> clone of repository gets created locally
>
> What happened instead? (Actual behavior)
> git clone fails with an error message : http.c:868 == Info: OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 0
>
> What's different between what you expected and what actually happened?
> The connection should not be aborted and the git clone process should complete
Usually this error means that the connection was interrupted. I'd
normally expect a non-zero errno in this case, but this is Windows, so
all bets are off.
Since you've mentioned that you're using a corporate proxy, is it one
that intercepts TLS? We often see those kinds of proxies break
connections for reasons that are unclear to me. Perhaps the proxy found
some undesirable pattern in the compressed data and dropped the
connection, or it could have become overloaded and dropped a connection
for that reason. In any event, you should try to reproduce without
that, because in my experience that's very frequently the cause.
It could also be a simple network problem, a flaky wireless or wired
network driver, a non-default antivirus or firewall (which often also do
TLS interception), monitoring software, or a bad ISP or network
connection. None of these are really a Git bug, so there's nothing for
us to fix here. You may want to talk to your corporate IT department if
need be.
Also, just as a side note, I'll mention that using NTLM over HTTP is
insecure and can, in some cases, expose your credentials in a form that
costs about $20 to crack, with just one request.
--
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
prev parent reply other threads:[~2024-06-05 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 6:06 git clone error : RPC failed; curl 56 OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 0 Thomas Gemmrich
2024-06-05 22:01 ` brian m. carlson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZmDgP57-5AS8B6Pc@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=Thomas.Gemmrich@vzch.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox