Re: Release candidate of Git for Windows 2.x is out

[Robert Dailey <rcdailey@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 2961 bytes --]


On Wednesday, May 27, 2015 at 5:11:37 PM UTC-5, Johannes Schindelin wrote:
>
> Hi all, 
>
> I just uploaded release candidates for the upcoming Git for Windows 2.x 
> release. Please find the download link here: 
>
> https://git-for-windows.github.io/#download 
>
> There are 32-bit and 64-bit versions both of regular installers and 
> portable installers ("portable" meaning that they are .7z archives that can 
> be unpacked anywhere and run in place, without any need for running an 
> installer). 
>
> My projected time line is to hammer out the last kinks until Friday, and 
> then continue after a one-week leave, if needed, and then finally retire 
> msysGit and start the official 2.x release cycle of Git for Windows. 
>
> If you are running Windows and have a little time to spare, please test 
> this release candidate thoroughly. If you find bugs, please first look at 
> https://github.com/git-for-windows/git/issues (even the closed ones), and 
> comment either on existing tickets or open new ones. It would be even 
> cooler, of course, if you could open Pull Requests with fixes :-) 
>

It's no longer clear exactly how to setup self-signed certificates in this 
new version of Git:

$ git fetch origin
fatal: unable to access 'https://mygitserver/myrepo.git/': SSL certificate 
problem: self signed certificate in certificate chain

No one on my team at $DAYJOB uses SSH, they all use HTTPS. Switching 
everyone to SSH certainly won't be an option either. So prior to asking 
everyone to upgrade, I'll need to be able to provide them instruction on 
how to properly setup our cert so that HTTPS works properly.

Ideally the solution will be done in such a way that when installing newer 
versions of Git for Windows, that the keys are not overwritten. Using the 
normal Git config approach won't work either since when you get the CA cert 
path to our key, it no longer knows about the other built-in certs, so 
fetches from github.com and the like will also fail.

Maybe there is an elegant or easy solution to this. But I just haven't 
found it yet.

 

-- 
-- 
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.

You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en

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

[-- Attachment #1.2: Type: text/html, Size: 4594 bytes --]