Well, in the original quote that was cited from "scary crypto stuff" was surrounded with: Last I checked they[GitHub] made you perform a bunch of scary crypto

Well, in the original quote that was cited from "scary crypto stuff" was surrounded with: Last I checked they[GitHub] made you perform a bunch of scary crypto stuff on your local machine before they'd let you in. If performing `ssh-keygen` and entering in an (optional) password from a command line constitutes "scary crypto", then maybe Git and GitHub isn't for everyone. Not that anyone needs to know how PKI works, but they might be better off knowing that `ssh-keygen` generates an ssh key pair, a pretty essential component of the `git` workflow. Maybe that's why SVN is so strong in older development shops. Outside of the effort required to convert an SVN repo to a Git repo, all those developers already have all the tools necessary on their machines (Windows is high on that list) and in many cases inside a VPN like my division we just use WebDAV anyways, completely bypassing the need for SSH Keys in favor of ActiveDirectory.