Universal binary Mac OS X Installer for Git
|git-2.10.2-osx-installer.dmg||13 MiB||v2.10.2||2016-11-08||Mac OS X 10.4+ universal installer for Git version 2.10.2 [hashes]|
|git-2.9.3-osx-installer.dmg||13 MiB||v2.9.3||2016-08-13||Mac OS X 10.4+ universal installer for Git version 2.9.3 [hashes]|
|git-2.8.4-osx-installer.dmg||13 MiB||v2.8.4||2016-06-20||Mac OS X 10.4+ universal installer for Git version 2.8.4 [hashes]|
In order to fully support SHA-256 certificates on Mac OS X 10.4 and Mac OS X 10.5 and to be more fully integrated with the native OS X experience, this version of Git uses libcurl for all http/https/imap/imaps/smtp/smtps activity where libcurl has been compiled to use the OS X native Secure Transport instead of OpenSSL. (This means that Git will use the standard root certificates from the normal system keychain locations for https/smtps/imaps authentication unless one of the various Git certificate configuration options is used to tell it otherwise.) Please note that even though libcurl is using the OS X native Secure Transport backend, the Secure Transport backend has been enhanced so that it does not suffer from the client certificate indigestion problem.
In practice there should be no difference in use between Git built this way and Git built to use curl/OpenSSL with one minor exception.
Secure Transport does not support a directory of certificates like OpenSSL does. An error will result if any of the following are used:
Additionally since the version of git imap-send that’s included is a curl-only version, there is one tiny behavioral difference to be aware of. When git imap-send is set to use a tunnel (i.e. imap.tunnel is set), an OpenSSL-using version of git imap-send will attempt to use the STARTTLS command if the other end of the tunnel supports it. A libcurl-using version of git imap-send will never do this. This only affects tunnels. All direct connections using imaps will always be encrypted.
Starting with Git version 2.8.0, an http.[<url>.]pinnedpubkey option is available. It may be set to any value supported by cURL’s CURLOPT_PINNEDPUBLICKEY option and, in addition, this version also allows it to be set to a filename of a PEM or DER format certificate (in which case the public key is automatically extracted from the certificate) and, in the case of a PEM format file, one or more PEM format public keys and/or certificates may be combined (by simply concatenating them together) to form a public key pinning set similarly to the way multiple “sha256//…” values can be combined to form a public key pinning set (by concatenating them with a “;” separator).
A change log showing the various software versions and patches included in the different releases is available here.
Despite the name of this installer including “OS X” in its title, it supports OS versions 10.4.8 and later no matter what Cupertino’s current nom-du-jour for the OS happens to be – “Mac OS X”, “OS X”, “macOS” etc.
The Git translations ARE included. The installer also contains an option (off by default) to make the installed version of Git choose its translation based on the System Preferences > International > Languages settings (instead of the LANG etc. environment variables) if desired.
Details on how to alter the translation selection behavior can be found in the release notes (installed to /opt/git/Release_Notes.rtf).
Optional installs of TopGit, a curl command line tool (that uses the libcurl.dylib installed for Git), GnuPG’s gpg utility and library headers (so that a new version of Git can be built from source using the libraries installed for Git) are included in the installer and enabled by default.
Customize the installation to turn off any of the optional installs.
Details on what gets installed and where everything goes can be found in the release notes (installed to /opt/git/Release_Notes.rtf).
Universal binary installers of Git (including required support libraries and executables) runnable on Mac OS X 10.4 or later are available from the following convenient download links:
Please note that older versions which were previously listed here, while they may still be available for download, are no longer recommended.
Git itself is licensed under GPLv2. Some of the libraries it has been linked with have less restrictive licenses, but since GPLv2 is the most restrictive of the bunch it’s the controlling one. GnuPG is licensed under GPLv3 but is an optional install (aggregated into the installer) and does not affect the license used by Git. GnuPG is linked with libusb and libusb-compat to provide smart card support and those are LGPLv2.1 making the effective GnuPG license restrictions still GPLv3.
The installer will display ALL licences for all software included in the installer package.