Error pushing to GitHub (from TortoiseGit)

[jo...@creativepost.co.uk]

I have around 20 or so projects hosted on GitHub. Although I can still fetch and pull, any attempt to push (to any of the projects) produces this error from TortoiseGit:-

"  error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version while accessing https://github.com/johne53/MB3<the project name>.git/info/refs

fatal: HTTP request failed "

It was all working, up until a few days ago (BTW I get the same error - even with different PC's)

I also contribute to some projects which aren't hosted on GitHub. Those ones are still working okay.

I'm sure this'll be some kind of issue with GitHub but before I contact them, I just wondered if anyone could explain what the above error means?

[Jacob Christ]

Are you at work and did someone turn on a firewall for ssh port 22?

Jacob

--
You received this message because you are subscribed to the Google Groups "tortoisegit-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tortoisegit-users+unsubscribe@googlegroups.com.
To post to this group, send email to tortoisegit-users@googlegroups.com.
Visit this group at https://groups.google.com/group/tortoisegit-users.
For more options, visit https://groups.google.com/d/optout.

[John Emmas]

On 26/02/2018 14:58, Jacob Christ wrote:

Are you at work and did someone turn on a firewall for ssh port 22?

Jacob

Thanks for the suggestion Jacob.

Both machines are at home.  Is there a way to check port 22 as I'm not aware of changing anything?  I'm running Windows 7 on one machine and Windows 8.1 on the other (and I see the same message in both cases).  Thanks,

John

[Sven Strickroth]

Hi,

Am 26.02.2018 um 14:33 schrieb jo...@creativepost.co.uk:
> I have around 20 or so projects hosted on GitHub. Although I can still
> fetch and pull, any attempt to push (to any of the projects) produces
> this error from TortoiseGit:-
>
> " error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert
> protocol version while accessing https://github.com/johne53/MB3<the
> project name>.git/info/refs
> fatal: HTTP request failed "

GitHub changed their default settings for ciphers.

See https://githubengineering.com/crypto-removal-notice/

It seems as if you're using a really old version of Git for Windows...

--
Best regards,
Sven Strickroth
PGP key id F5A9D4C4 @ any key-server

[John Emmas]

On 26/02/2018 21:26, Sven Strickroth wrote:
> GitHub changed their default settings for ciphers.
>
> See https://githubengineering.com/crypto-removal-notice/
>
> It seems as if you're using a really old version of Git for Windows...
>

That'll be it, Sven.

In the past, whenever I've tried to update TortoiseGit it's invariably
introduced problems (e.g. git diff stopped working at one point !! ) but
I guess I'll have to bite the bullet now.

IIRC though, isn't TortoiseGit in fact a wrapper for something else? 
i.e. it won't simply be a job of upgrading TortoiseGit itself.  I'm
guessing there'll be at least 2 components to upgrade?

John

[Sven Strickroth]

Am 27.02.2018 um 08:05 schrieb John Emmas:
> In the past, whenever I've tried to update TortoiseGit it's invariably
> introduced problems (e.g. git diff stopped working at one point !! ) but
> I guess I'll have to bite the bullet now.
>
> IIRC though, isn't TortoiseGit in fact a wrapper for something else? 

TortoiseGit is just a GUI frontend for Git (for Windows). Therefore,
yoou still have to keep Git for Windows up2date.

See: https://tortoisegit.org/support/faq/#prerequisites

[John Emmas]

On 27/02/2018 07:30, Sven Strickroth wrote:
>
> TortoiseGit is just a GUI frontend for Git (for Windows). Therefore,
> yoou still have to keep Git for Windows up2date.
>
> See: https://tortoisegit.org/support/faq/#prerequisites
>

Thanks again Sven,

It looks like my current TortoiseGit is wrapping something called
Msys-git. I'm just curious to know if that's an earlier version of Git
for Windows or are they totally different products?

John

[Sven Strickroth]

Am 27.02.2018 um 14:37 schrieb John Emmas:
> It looks like my current TortoiseGit is wrapping something called
> Msys-git.  I'm just curious to know if that's an earlier version of Git
> for Windows or are they totally different products?

Old Git for Windows (called msysgit) was based on msys1, whereas the new
(real) Git for Windows is from the very same authors, but based on msys2.

See https://stackoverflow.com/a/32427897/3906760

[John Emmas]

I updated both TortoiseGit and Git for Windows and (fingers crossed !)
it seems okay so far (I can even push to GitHub again!!)

Is this a good place to ask for feature requests..?

When creating a stash, it'd be really, really, reeeeally useful if I
didn't have to include all my edited files in the stash (i.e. if I could
select which files get included in which stash).

Let's say I've edited 8 files locally (but I've been working on 2
different problems). It'd be sooo useful if I could create different
stashes for each set of changes - let's say 1 x stash consisting of the
3 files which got changed for problem #1 and then a 2nd (separate) stash
for the 5 files which got changed for problem #2.

Or is this already available somehow? If so, I've never found it....

John

[John Emmas]

On 26/02/2018 21:26, Sven Strickroth wrote:

Am 26.02.2018 um 14:33 schrieb jo...@creativepost.co.uk:

I have around 20 or so projects hosted on GitHub. Although I can still
fetch and pull, any attempt to push (to any of the projects) produces
this error from TortoiseGit:-

"  error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert
protocol version while accessing https://github.com/johne53/MB3<the
project name>.git/info/refs
fatal: HTTP request failed "

GitHub changed their default settings for ciphers.

See https://githubengineering.com/crypto-removal-notice/

It seems as if you're using a really old version of Git for Windows...

Hi Sven,

On my main machine I updated to the latest version and I'm now able to push my projects to GitHub again.

However... my 2nd PC is still running an older copy of TortoiseGit and I was surprised to find that it can't 'pull' any more from my GitHub repo (even from projects that haven't changed).  In fact I see the same error message that I reported above.

Naturally, I assumed this must be a problem with GitHub (I figured it must be insisting on TLSv1.2 for both pushing and pulling) so I contacted GitHub to complain.  However, they've just replied to say that whilst a TLSv1.2 client is needed for pushing, it doesn't affect pulling.

So could this possibly be a problem with TortoiseGit?  i.e. if my repo gets pushed using a newer TGit, it can't then get pulled by somebody using an older version?  My older version (of TortoiseGit) can still pull from other people's repos (i.e. ones that aren't hosted on GitHub)  Thanks...

John

[Sven Strickroth]

Hi John,

Am 04.03.2018 um 19:59 schrieb John Emmas:
> However... my 2nd PC is still running an older copy of TortoiseGit and I
> was surprised to find that it can't 'pull' any more from my GitHub repo
> (even from projects that haven't changed).  In fact I see the same error
> message that I reported above.

TortoiseGit just calls git.exe of the Git for Windows package. So our
your computer where it does not work, you seem to have an outdated
version of git installed (cf. https://stackoverflow.com/q/48938019/3906760).

[John Emmas]

On 04/03/2018 21:45, Sven Strickroth wrote:
>
> TortoiseGit just calls git.exe of the Git for Windows package. So our
> your computer where it does not work, you seem to have an outdated
> version of git installed (cf.https://stackoverflow.com/q/48938019/3906760).
>

Thanks Sven, it looks like I'll need to dig a bit deeper.

I do have an old version of git installed on my 2nd computer (I haven't
updated that one yet) but according to GitHub Support, that should only
affect pushing.  'git pull' and 'git fetch' should still be possible -
even with an older client using TLSv1.0 or v1.1 (and to be fair, that
was definitely possible before I updated Git and TortoiseGit on my 1st
machine).

On that 1st machine I'm now running Git v2.16.2 and TortoiseGit v2.6.0.0
- it feels as if one of them has 'marked' my GitHub repo somehow, so
that it can't be used any more with older versions.

(either that - or GitHub Support are simply mistaken...)

And if I read between the lines, there's something called 'Git
Credential Manager' which might also be involved.  I didn't update GCM
(in fact, I'm not even sure what it is) but maybe that needs updating too?

John

[John Emmas]

On 05/03/2018 09:56, John Emmas wrote:

> On 05/03/2018 08:43, John Emmas wrote:
>>
>> it looks like I'll need to dig a bit deeper.
>>
>

> Hmmm... I think I just found something which might be significant...
> my own git projects are housed here:-
>
> https://github.com/johne53/
>
> but I just managed to find some other people's projects which are also
> hosted on GitHub (but which don't have any connection with mine) -
> namely:-
>
> https://github.com/swh/LRDF
> https://github.com/dajobe/raptor
> git://github.com/behdad/harfbuzz
> git://github.com/atgreen/libffi.git
>
> for all the projects which are hosted at 'https://github.com' I can no
> longer pull or fetch from them if I use an older combination of Git
> for Windows & TortoiseGit - BUT -
>
> for both the projects hosted at 'git://github.com' I can still pull
> and fetch from them !!
>
> Does that give any clue as to where the problem might lie?
>
> John
>

[Sven Strickroth]

Am 05.03.2018 um 12:00 schrieb John Emmas:
>> for both the projects hosted at 'git://github.com' I can still pull
>> and fetch from them !!

The https protocol uses encryption which is affected by old Git clients,
whereas the git:// doesn't use encryption at all, therefore the latter
is not affected.

[John Emmas]

On 05/03/2018 11:36, Sven Strickroth wrote:
> The https protocol uses encryption which is affected by old Git clients,
> whereas the git:// doesn't use encryption at all, therefore the latter
> is not affected.
>

That makes a lot of sense, Sven. Many thanks for all your help with this.

John