GitHub Enterprise - The best way to build and ship software
Features Case Studies Pricing Resources Contact Sign in Try it for free Release notes for the 2.3 series GitHub Enterprise 2.3.23 November 01, 2016 Download Security Fixes Packages have been updated to the latest security versions. Changes GitHub Enterprise is now available in the US East (Ohio) AWS region. 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. Email can't be sent over TLS when SSL is disabled. Deleting a user doesn't delete their gists, which can cause problems with replication. 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.
The management console settings interface doesn't clearly show if you have previously uploaded certificate files or a private key. Management console sessions can expire too quickly for Safari users. Gist repositories are not garbage collected by the maintenance scheduler. Custom firewall rules aren't maintained during an upgrade. Repositories that are in an incomplete state, which is a rare problem, can cause the migration to the new repository disk layout to fail.
Enqueued background jobs are sometimes not purged when a repository is deleted. When a fork is detached from its repository network by an administrator or by changing visibility , its filesystem path won't be updated on a high availability replica until at least one commit has been pushed. Viewing raw files in repositories owned by a user or organization named "github" fails with a 400 error. Deprecation of GitHub Enterprise 2.3 GitHub Enterprise 2.3 is now deprecated.
That means that no patch releases will be made, even for critical security issues, after this release. For better performance, improved security, and new features, upgrade to the newest version of GitHub Enterprise as soon as possible. Thanks! The GitHub Team GitHub Enterprise 2.3.22 October 18, 2016 Download Security Fixes Packages have been updated to the latest security versions. Bug Fixes Changing the default branch of a repository was not synchronized to a high availability replica, so the wrong branch was set as default after fail over.
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. Email can't be sent over TLS when SSL is disabled. Deleting a user doesn't delete their gists, which can cause problems with replication. 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. The management console settings interface doesn't clearly show if you have previously uploaded certificate files or a private key. Management console sessions can expire too quickly for Safari users. Gist repositories are not garbage collected by the maintenance scheduler. Custom firewall rules aren't maintained during an upgrade.
Repositories that are in an incomplete state, which is a rare problem, can cause the migration to the new repository disk layout to fail. Enqueued background jobs are sometimes not purged when a repository is deleted. When a fork is detached from its repository network by an administrator or by changing visibility , its filesystem path won't be updated on a high availability replica until at least one commit has been pushed.
Viewing raw files in repositories owned by a user or organization named "github" fails with a 400 error. Thanks! The GitHub Team GitHub Enterprise 2.3.21 September 20, 2016 Download Pre-generated SSH Host Keys in GitHub Enterprise A CRITICAL issue was identified for all 2.x versions of GitHub Enterprise. The GitHub Enterprise images contain pre-generated SSH host keys that were not regenerated upon installation for all supported platforms: Hyper-V (VHD) OpenStack KVM (QCOW2) VMware ESXi/vSphere (OVA) Xen (VHD) Amazon Web Services (See the ssh_host_ed25519_key in GitHub Enterprise section below) Microsoft Azure This means an attacker with the capability to perform a man-in-the-middle attack on SSH traffic can intercept and modify network traffic to the GitHub Enterprise appliance.
The affected supported versions are: 2.7.0 - 2.7.3 2.6.0 - 2.6.8 2.5.0 - 2.5.13 2.4.0 - 2.4.16 2.3.0 - 2.3.20 This vulnerability was found and reported internally and we have no evidence that it has been exploited in the wild. We strongly recommend upgrading your GitHub Enterprise appliance to the latest patch release in your series, GitHub Enterprise 2.7.4, 2.6.9, 2.5.14, 2.4.17, or 2.3.21. In addition, with backup-utils-2.7.1 , ghe-backup and ghe-restore will check for any leaked SSH host keys in the snapshot(s).
Please contact GitHub Enterprise Support if you have questions. -- Verification and Mitigation on GitHub Enterprise 2.7.4, 2.6.9, 2.5.14, 2.4.17, 2.3.21, or greater If you've upgraded to the latest patch release, GitHub Enterprise 2.7.4, 2.6.9, 2.5.14, 2.4.17, 2.3.21, or greater, SSH to your primary GitHub Enterprise appliance. Check for leaked SSH host keys using the ghe-ssh-check-host-keys utility. $ ghe-ssh-check-host-keys The utility should output either: One or more of your SSH host keys were found in the blacklist.
Please reset your host keys using ghe-ssh-roll-host-keys. -- The SSH host keys were not found in the SSH host key blacklist. No additional steps are needed/recommended at this time. If one or more SSH host keys were found in the blacklist, continue to the next step. Otherwise, your GitHub Enterprise environment is not vulnerable. Put your GitHub Enterprise environment in Maintenance Mode . Rotate all SSH host keys using the ghe-ssh-roll-host-keys utility. $ sudo ghe-ssh-roll-host-keys $ sudo ssh-keygen -t ed25519 -N "" -f /etc/ssh/ssh_host_ed25519_key The utility should output: $ SSH host keys have successfully been rolled.
If you've upgraded to GitHub Enterprise 2.7.4, 2.6.9, or greater, and you are using the High Availability Configuration , there are no additional steps to take on your replica appliance. If you've upgraded to GitHub Enterprise 2.5.14, 2.4.17, 2.3.21, or greater, and you are using the High Availability Configuration , After completing steps 1-5, stop replication on the replica appliance. $ ghe-repl-stop Synchronize the SSH host keys from the primary appliance. $ ghe-repl-setup Resume replication on the replica appliance. $ ghe-repl-start -- Verification and Mitigation if Immediate Upgrade is not Possible If you're unable to upgrade immediately to the latest patch release, GitHub Enterprise 2.7.4, 2.6.9, 2.5.14, 2.4.17, 2.3.21, or greater, SSH to your primary GitHub Enterprise appliance.
Download the list of leaked SSH host keys and verify its content using any of the provided hashes. $ curl -O https://enterprise.github.com/security/2016-09-20/ghe-ssh-leaked-host-keys-list.txt $ sha256sum ghe-ssh-leaked-host-keys-list.txt 3bb29658784a4059a41f1a77cffba9586baab179ba07b795f80e12a9f10c5665 ghe-ssh-leaked-host-keys-list.txt $ sha1sum ghe-ssh-leaked-host-keys-list.txt 5db799da044da9aae0bcfc523d22e7ce0fe72550 ghe-ssh-leaked-host-keys-list.txt $ md5sum ghe-ssh-leaked-host-keys-list.txt de75bcb0bf1d13e15620952c0af8da41 ghe-ssh-leaked-host-keys-list.txt Print the fingerprint of your GitHub Enterprise appliance's SSH host keys.
Note: The ssh_host_ed25519_key may exist on your GitHub Enterprise appliance but is only used in 2.7.4 or greater. $ ssh-keygen -lf /etc/ssh/ssh_host_dsa_key.pub 1024 b2:69:82:2f:25:48:bb:fc:62:c7:9a:de:41:42:13:55 /etc/ssh/ssh_host_dsa_key.pub (DSA) $ ssh-keygen -lf /etc/ssh/ssh_host_ecdsa_key.pub 256 c0:cb:fd:07:33:e9:62:14:6b:fb:d5:26:54:f3:c5:0d /etc/ssh/ssh_host_ecdsa_key.pub (ECDSA) $ s
The rest of this page is on the live site.