Re: Re: 3rd release candidate of Git for Windows 2.x, was Re: Release candidate of Git for Windows 2.x is out

[Robert Dailey <rcdailey@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 3615 bytes --]

 Let me add a question to this: how does one add new certs? If there are
multiple files. I have an issue open for this but still no information.
Thanks in advance.

Sorry for top post, replying on my phone.


On Sat, Jun 20, 2015, 10:22 AM Johannes Schindelin <
johannes.schindelin@gmx.de> wrote:

Hi Jon,

On 2015-06-20 16:59, Jon wrote:
> On Saturday, June 20, 2015 at 10:16:09 AM UTC-4, Johannes Schindelin
wrote:
>>
>> I just uploaded the 3rd release candidate for the upcoming Git for
Windows
>> 2.x release. Please find the download link here:
>>
>> https://git-for-windows.github.io/#download
>>
>> Lots of changes since the first release candidate (v2.4.2, I was too
>> swamped to announce the second release candidate -- v2.4.3 -- I published
>> Friday last week, my apologies). Please find them in the release notes:
>>
>>
https://github.com/git-for-windows/build-extra/blob/master/installer/ReleaseNotes.md
>
> 1) Why are there two ssl/certs trees? (e.g. - one is used by git-bash.exe
> and the other git-cmd.exe and cmd/git.exe?)

Please keep in mind that Git for Windows is a hybrid collection of pure
Win32 executables and MSys2 executables (MSys2 is a stripped-down Cygwin
providing a POSIX emulation layer on top of the Win32 API[*1*]). They are
separated into the `/usr/` and the `/mingw64/` directories, respectively
(`/mingw32/` for 32-bit). An example for a pure Win32 executable is
`git.exe` while Perl and Bash are MSys2 executables. In general, we avoid
MSys2 as much as possible: while it provides a nice POSIX emulation layer,
it comes at a noticable performance penalty.

So whenever we can get away with using OpenSSL compiled as pure Win32
library, we do so. Cloning via HTTPS falls into that category.

When it comes to `git-svn` -- something that is needed by many users,
still, and indeed the motivation for the most prolific contributor helping
me with Git for Windows 2.x -- it is not that easy, though: `git-svn` is a
Perl script, our Perl is an MSys2 program and therefore uses OpenSSL
compiled as MSys2 library.

That is the reason why we have separate ssl/ directory structures. One for
MinGW (i.e. pure Win32) programs and one for MSys2 ones.

> 2) Why are INSTALL_DIR/usr/ssl/certs/ca-bundle.crt and
> INSTALL_DIR/mingw64/ssl/certs/ca-bundle.crt different?

We simply use the packages provided by MSys2. The MinGW/MSys2
ca-certificates packages are sometimes out of sync, and that is what you
are seeing here.

Now, theoretically it would be possible to reconcile the different
ca-certificates packages into a single one. The correct way to go about
this would be by contributing to the MSys2 project: that way, not only Git
for Windows but really all MSys2-based projects benefit from it.

-- 
-- 
*** 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 #2: Type: text/html, Size: 4657 bytes --]