com/project.git does not suffer from the same problem (unless the attacker can provide a TLS certificate for example.com). Running git clone git@example.com:project.git only suffers from this problem follow along is to tell Git not to verify SSL certificates. The Git Fusion image comes with a certificate, but it’s for a domain that won’t match your virtual machine’s IP address, so Git will reject to be a permanent installation, consult the Perforce Git Fusion manual to install a different certificate; for our example purposes, this will suffice: $ export GIT_SSL_NO_VERIFY=true Now we can test

com/project.git does not suffer from the same problem (unless the attacker can provide a TLS certificate for example.com). Running git clone git@example.com:project.git only suffers from this problem follow along is to tell Git not to verify SSL certificates. The Git Fusion image comes with a certificate, but it’s for a domain that won’t match your virtual machine’s IP address, so Git will reject to be a permanent installation, consult the Perforce Git Fusion manual to install a different certificate; for our example purposes, this will suffice: 386 $ export GIT_SSL_NO_VERIFY=true Now we can

com/project.git does not suffer from the same problem (unless the attacker can provide a TLS certificate for example.com). Running git clone git@example.com:project.git only suffers from this problem follow along is to tell Git not to verify SSL certificates. The Git Fusion image comes with a certificate, but it’s for a domain that won’t match your virtual machine’s IP address, so Git will reject to be a permanent installation, consult the Perforce Git Fusion manual to install a different certificate; for our example purposes, this will suffice: $ export GIT_SSL_NO_VERIFY=true Now we can test