The 2.17 series release notes contain important changes in this release series.

Security Fixes

• MEDIUM: An attacker with direct network access to the server could send a specially crafted sequence of network packets that could cause a kernel panic or slow down the system causing a Denial of Service (DoS). For more information, see the associated CVEs: CVE-2019-11477, CVE-2019-11478, CVE-2019-11479.
• Packages have been updated to the latest security versions.

Bug Fixes

• Internal API data values exceeded internal buffer sizes and caused access from the Git command-line to fail unconditionally for some users or deploy keys.
• In single node appliances, the ghe-export-audit-logs command did not correctly detect the instance type in some cases, causing backups to fail.
• Adding a new node to a currently or previously configured high availability replication primary node that has been upgraded to GitHub Enterprise Server 2.17 could fail due to a missing /etc/openvpn/easy-rsa/openssl.cnf file.
• Pre-seeding the initial replica appliance in a HA configuration would result in the failure of the existing primary appliance.
• The GitHub Connect "Learn more" link beside the message "You can now connect to an enterprise account" pointed to a nonexistent help article.
• The "Learn why" link beside the message "Custom sign-in messages are disabled when SAML authentication is enabled" pointed to a nonexistent help article.
• The GraphQL API would only return 300 objects instead of the documented 3000.
• In the GraphQL API, the suggestedReviewers field returned an error when queried in combination with some other fields (e.g., additions or deletions).
• Displayed an invalid prompt when editing FUNDING.yml, which would then also fail to preview changes correctly.
• The Collaboration "Funding model links" section would appear within the UI.
• Pre-receive hooks that printed non UTF-8 characters would fail with an "incompatible character encodings" error message.
• When attempting to search for private repositories on GitHub.com via GitHub Connect, a 500 Internal Server Error occurred.
• GitHub Enterprise Server incorrectly enforced a version of Backup Utilities that was the same or newer than the precise patch version of GitHub Enterprise Server.

Changes

• GitHub Enterprise is now available in the AWS GovCloud (US-East) region.
• When pushing a very large number of Git LFS objects to a repository, the returning "Git LFS Integrity Check" warning message was confusing, leading users to think something went wrong.

Known Issues

• On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
• Custom firewall rules aren't maintained during an upgrade.
• Subversion (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.
• Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
• Resque workers may not be cleaned up following a configuration run leading to a growing number of stale workers which in turn could lead to high memory consumption.
• Hypervisor type and root volumes are incorrectly detected on AWS Nitro instance types, preventing non-hotpatch upgrades. (updated: 2019-07-09)
• Lines in gists are not selectable. (updated: 2019-07-19)
• When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.

Thanks!

The GitHub Team