GitHub Enterprise 2.11.2 September 22, 2017 Download

Security Fixes

  • Packages have been updated to the latest security versions.

Bug Fixes

  • Memory budgets computed for services were under-allocated leading to severe performance issues.
  • LFS operations could fail with a slow LDAP server. The internal API timeout for LFS operations has been increased.

Fixes from 2.11.1 that was withdrawn due to a memory budget computation bug

  • Elasticsearch could exceed recommended heap size. The memory budget is capped at a maximum of 32 GB.
  • Upgrading a high availability environment from a 2.10 release to 2.11.0 failed with a Failed drop elasticsearch scan file error.
  • The default authenticated homepage would be blank for users that don't own or have direct collaboration permissions to any repositories.
  • The repository owner was not displayed when configuring a pre-receive hook.
  • Querying the Teams API with an invalid ID failed with a '500 Internal Server Error'.
  • Outside collaborators were not added to a repository if mapped to a suspended user during the migration of a repository using ghe-migrator.

Known Issues

  • We incorrectly redirect to the dashboard if you accessed GitHub Enterprise using an alias while in private mode. This might happen if you set a fully qualified domain name but the subdomain resolves correctly.
  • Images uploaded to issues save with an absolute URL, so they can be broken if the hostname changes.
  • On a freshly set up GitHub Enterprise without any users, an attacker could create the first admin user.
  • Custom firewall rules aren't maintained during an upgrade.
  • svn checkout may timeout while the repository data cache is being built. In most cases, subsequent svn checkout attempts will succeed.
  • Git LFS tracked files uploaded with through the web interface are incorrectly added directly to the repository.
  • GitHub Enterprise clustering can not be configured without https.
  • Deleting a search index doesn't delete all associated metadata, which are then incorrectly reused if a new search index is created. This causes search index repair jobs to be reported as finished in the site admin when they were not.
  • Hotpatch upgrades 2.11.2 could fail reloading the babeld service. If the upgrade fails, run the following command from the affected appliance(s):

    $ sudo systemctl restart babeld
    

Thanks!

The GitHub Team

GitHub Enterprise 2.11.1 September 19, 2017 Download

Notice

  • The 2.11.1 patch release has been withdrawn due to the introduction of a major bug which caused memory budgets for services to be under-allocated. If you have already upgraded your appliance to GitHub Enterprise 2.11.1, please contact support for assistance. (updated 2017-09-21)

Security Fixes

  • Packages have been updated to the latest security versions.
  • LOW: A PDF with looping xref tables caused the PDF renderer to consume high amounts of CPU or hang a user's browser. This vulnerability was also patched in 2.11.0.

Bug Fixes

  • Elasticsearch could exceed recommended heap size. The memory budget is capped at a maximum of 32 GB.
  • Upgrading a high availability environment from a 2.10 release to 2.11.0 failed with a Failed drop elasticsearch scan file error.
  • Users had a missing dashboard (i.e. default authenticated homepage) if they didn't own or have direct collaboration permissions to any repositories.
  • The repository owner was not displayed when configuring a pre-receive hook.
  • Querying the Teams API with an invalid ID failed with a '500 Internal Server Error'.
  • Outside collaborators were not added to a repository if mapped to a suspended user during the migration of a repository using ghe-migrator.

Known Issues

  • We incorrectly redirect to the dashboard if you accessed GitHub Enterprise using an alias while in private mode. This might happen if you set a fully qualified domain name but the subdomain resolves correctly.
  • Images uploaded to issues save with an absolute URL, so they can be broken if the hostname changes.
  • On a freshly set up GitHub Enterprise without any users, an attacker could create the first admin user.
  • Custom firewall rules aren't maintained during an upgrade.
  • svn checkout may timeout while the repository data cache is being built. In most cases, subsequent svn checkout attempts will succeed.
  • Git LFS tracked files uploaded with through the web interface are incorrectly added directly to the repository.
  • GitHub Enterprise clustering can not be configured without https.
  • Deleting a search index doesn't delete all associated metadata, which are then incorrectly reused if a new search index is created. This causes search index repair jobs to be reported as finished in the site admin when they were not.
  • Hotpatch upgrades from 2.11.0 to 2.11.1 and configuration updates could fail reloading the babeld service. If the upgrade or configuration update fails, run the following command from the affected appliance(s): (updated 2017-09-21)

    $ sudo systemctl restart babeld
    

Thanks!

The GitHub Team

GitHub Enterprise 2.11.0 September 13, 2017 Download

Features

Security Fixes

  • Packages have been updated to their latest security versions.
  • LOW: A PDF with looping xref tables caused the PDF renderer to consume high amounts of CPU or hang a user's browser. (updated 2017-09-19)

Bug Fixes

  • Commit contributions for a repository were not rebuilt when the gh-pages branch is deleted.
  • In a clustering environment, ghe-cluster-config-node-init could fail silently.
  • Adding a project note containing emoji would fail with a '500 Internal Server Error'.
  • The Branch Merging API stripped lines starting with # from commit messages.
  • The user suggestion functionality could timeout when adding members to a very large team.
  • Adding files with a blank content type, e.g. .zip, .docx, to conversations in issues and pull requests would fail.
  • An empty Projects board was shown when Elasticsearch was unavailable or rebuilding indices after an upgrade.

Changes

  • The MIME types used by GitHub Pages match those used by the rest of the appliance.
  • Syslog identifiers for various services have been made more explicit to make it easier to identify the service.
  • The maximum number of multiplexed session for administrative SSH session has been increased to 100. This improves backup restores for clustering environments.
  • NTLM has been removed from the SMTP configuration as an authentication protocol option. This was not working and is insecure.
  • Releases are sorted first by date and then semantic version instead of lexicographically.
  • Support for legacy high availability replication has been removed in 2.11. The default replication mechanism changed in 2.9 and this is now the only option in 2.11. This change has no impact unless legacy high availability replication was explicitly configured.
  • OpenVPN, used in high availability and clustering environments, has been upgraded to 2.4 with support for ECDHE. This removes the need to generate DH parameters and speeds up initial OpenVPN setup.
  • Pre-receive hooks now run as an unprivileged dedicated user. This could impact running hooks if hooks write temporary data outside /tmp. Running pre-receive hooks as an unprivileged dedicated user improves security by limiting access to the rest of the system from pre-receive hooks.
  • GitHub Pages now uses Jekyll 3.5.1.
  • GitHub Pages now uses Commonmark for Markdown rendering.
  • Using enterprise@github.com as the support address is no longer supported. Customers who have this email address configured need to change it to a valid internal support address or URL.
  • samplicator, the utility that sends statistics to the metrics servers in cluster environments, now runs as an unprivileged dedicated user.
  • The commit button text is now shown as "Commit merge" in the conflict editor to better communicate what is happening.

Backups and Disaster Recovery

GitHub Enterprise 2.11 requires at least GitHub Enterprise Backup Utilities 2.11.0 for Backups and Disaster Recovery.

Upcoming deprecation of Internet Explorer 11 support

  • Support for Internet Explorer 11 will be deprecated on September 13, 2018.

Upcoming deprecation of VMware ESX 5.5 support

  • Support for VMware ESX 5.5 will be deprecated on September 13, 2018.

Upcoming deprecation of GitHub Enterprise 2.8

GitHub Enterprise 2.8 will be deprecated as of November 9, 2017. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, upgrade to the newest version of GitHub Enterprise as soon as possible.

Known Issues

  • We incorrectly redirect to the dashboard if you accessed GitHub Enterprise using an alias while in private mode. This might happen if you set a fully qualified domain name but the subdomain resolves correctly.
  • Images uploaded to issues save with an absolute URL, so they can be broken if the hostname changes.
  • On a freshly set up GitHub Enterprise without any users, an attacker could create the first admin user.
  • Custom firewall rules aren't maintained during an upgrade.
  • svn checkout may timeout while the repository data cache is being built. In most cases, subsequent svn checkout attempts will succeed.
  • Git LFS tracked files uploaded through the web interface are incorrectly added directly to the repository.
  • GitHub Enterprise clustering can not be configured without https.
  • Deleting a search index doesn't delete all associated metadata, which are then incorrectly reused if a new search index is created. This causes search index repair jobs to be reported as finished in the site admin when they were not.
  • Upgrading a high availability environment from a 2.10 release to 2.11.0 could fail with the following error: (updated 2017-09-14)

      $ ghe-upgrade ./github-enterprise-ami-2.11.0.pkg
      *** verifying upgrade package signature...
      725MiB 0:00:05 [ 141MiB/s] [===========================>] 100%
      gpg: Signature made Tue 12 Sep 2017 05:03:10 AM UTC using RSA key ID 0D65D57A
      gpg: Good signature from "GitHub Enterprise (Upgrade Package Key) <enterprise@github.com>"
      *** applying update...
      Scanning for incompatible Elasticsearch mappings...
      waiting for ssh for [ghe-host-replica] to be available
      ssh command returned 255
      Failed drop elasticsearch scan file
    

    If you encounter this error, run the following command from your primary or replica appliance before running ghe-upgrade again:

      $ ghe-cluster-each -- sudo touch /data/user/common/es-scan-complete
    
  • Users may have a missing dashboard (i.e. default authenticated homepage) if they don't own or have direct collaboration permissions to any repositories. If users are encountering this error, they can work around this issue by creating a personal repository. (updated 2017-09-14)

Thanks!

The GitHub Team