Your Ansible Tower instance url and credentials were supplied to you on the page created for this workshop. Going to focus on a few of the key constructs that are required for this Multi-tenancy, notifications, scheduling, etc. More details on the vulnerability can be found in the official Git mailing list announcement and on the git-blame blog.There are a number of constructs in the Ansible Tower UI that enable Third party software using these libraries is strongly encouraged to update. The two major Git libraries, libgit2 and JGit, have released maintenance versions with the fix.Git for Windows (also known as MSysGit) has released maintenance version 1.9.5.The Git core team has announced maintenance releases for all current versions of Git (v1.8.5.6, v1.9.5, v2.0.5, v2.1.4, and v2.2.1).In addition, the following updated versions of Git address this vulnerability:

Updated versions of GitHub for Windows and GitHub for Mac are available for immediate download, and both contain the security fix on the Desktop application itself and on the bundled version of the Git command-line client. This work is an extension of the data-quality checks we have always performed on repositories pushed to our servers to protect our users against malformed or malicious Git data. We have also completed an automated scan of all existing content on to look for malicious content that might have been pushed to our site before this vulnerability was discovered. Repositories hosted on cannot contain any of the malicious trees that trigger the vulnerability because we now verify and block these trees on push. We strongly encourage all users of GitHub and GitHub Enterprise to update their Git clients as soon as possible, and to be particularly careful when cloning or accessing Git repositories hosted on unsafe or untrusted hosts. Linux clients are not affected if they run in a case-sensitive filesystem. Git clients running on OS X (HFS+) or any version of Microsoft Windows (NTFS, FAT) are exploitable through this vulnerability. git/config file when cloning or checking out a repository, leading to arbitrary command execution in the client machine. An attacker can craft a malicious Git tree that will cause Git to overwrite its own.

The vulnerability concerns Git and Git-compatible clients that access Git repositories in a case-insensitive or case-normalizing filesystem. Because this is a client-side only vulnerability, and GitHub Enterprise are not directly affected. A critical Git security vulnerability has been announced today, affecting all versions of the official Git client and all related software that interacts with Git repositories, including GitHub for Windows and GitHub for Mac.

Tower git client