The 2.7 series release notes contain important changes in this release series.
- MEDIUM: Local privileged MySQL credentials and Alambic HMAC/API keys were exposed in log files included in the support bundle.
- None of the currently supported releases of GitHub Enterprise are affected by the Linux kernel UDP remote code execution vulnerability issued 4 April 2017 (CVE-2016-10229).
- Packages have been updated to the latest security versions.
- An issue or pull request comment containing the string 'User-Agent: GitHub-Hookshot' incorrectly triggered a firewall rule that caused an internal server error on several pages, including the author's profile page.
- Collectd statistics were collected for the temporary pre-receive hook environment mount points.
- Users could be added to a team if they don't satisfy the Organization's 2FA requirements.
- Very large release or Git LFS assets failed to replicate due to a timeout in a high availability environment.
- In a clustering environment, several services failed to start following a reboot.
- In a clustering environment, configuring multiple nodes in parallel could lead to nodes overwriting each other's MySQL seed data.
jq utility has been added to the default pre-receive hook environment.
- More colors are used in the monitoring graphs in a high availability environment, making them more legible.
- Backups of cluster environments with a large number of archived repositories has been optimized for improved performance.
Upcoming deprecation of GitHub Enterprise 2.6
GitHub Enterprise 2.6 will be deprecated as of April 26, 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.
- 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.
- Enqueued background jobs are sometimes not purged when a repository is deleted.
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.
- Additional white spacing can sometimes be seen above the Admin center header.
- 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.
- collectd metric paths can be truncated, which causes multiple write attempts to the same file for different metrics. (updated 2017-07-10)
The GitHub Team