On Fri, 5 Jul 2024 at 03:50, brian m. carlson <sandals@xxxxxxxxxxxxxxxxxxxx> wrote: > > On 2024-07-04 at 13:56:15, Abraham Zsombor Nagy wrote: > > Hello Git Team, > > > > I hope you can help me. > > > > I'm trying to push my code to GitHub, however I'm unable to do so: > > > > abris@dell:~/Projects/maradandohalo/server$ git push --set-upstream origin main > > Username for 'https://github.com': nazsombor > > Password for 'https://nazsombor@xxxxxxxxxx': > > fatal: protocol error: bad line length 175 > > send-pack: unexpected disconnect while reading sideband packet > > error: failed to push some refs to > > 'https://github.com/nazsombor/maradandohalo.git' > > Enumerating objects: 31, done. > > Counting objects: 100% (31/31), done. > > Delta compression using up to 16 threads > > Compressing objects: 100% (22/22), done. > > > > I use Debian 12. I tried this with the git installed via apt as well > > with the git compiled from source code. Git version: 2.45.GIT > > > > I also asked this question first on StackOverflow: > > https://stackoverflow.com/questions/78670914/git-fatal-protocol-error-bad-line-length-173 > > I know you've got this working with SSH, but I'll just mention that > usually this message "protocol error: bad line length" means that you > have some sort of proxy (such as an antivirus or a TLS-intercepting > device) that's tampering with the data. TLS, which is the protocol used > for encryption on HTTPS URLs, has built-in mechanisms to detect any sort > of accidental or intentional modification of the data, so if we assume > that both your version of Git and GitHub sent valid protocol data, then > this means that if it came out bad on the other side, it was tampered > with in the middle by something that can decrypt the data (which would > have to be something trusted by your machine). > > That's why SSH works for you: because the types of proxies that > typically know how to process HTTPS data don't know how to decrypt or > intercept SSH connections, so your data doesn't get corrupted. > -- > brian m. carlson (they/them or he/him) > Toronto, Ontario, CA Thank you Brian, I cannot think of anything, I'm just behind my home network, I don't have a dedicated firewall or proxy. Pushing via https works on Windows on the same laptop. So I guess it's something in my Linux env. I don't know if it matters, but cloning worked out of the box on Linux. Sincerely, Abraham
