clone.sh requires special permissions

[Caerbannog]

Running clone.sh when you have no github account or no special permission results in the following command being executed:

$ git clone git@github.com:RangeNetworks/asterisk.git
Cloning into 'asterisk'...
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

The solution could be change the script to clone over HTTP. Alternatively the permissions of the repositories could be changed.

[iedemam]

There aren't any special permissions required, this is merely a side-effect of each repo using SSH clone addresses.

I will add a --read-only clone mode to the scripts so non-githubbers can at least pull the code down.

[Caerbannog]

Right, thank you.

[dannyiland]

I also saw this error. As iedemam mentioned, adding my ssh key to my github account allowed the command to run successfully.

[yuvadm]

Please change all the remote URLs to use the HTTPS transport. Using SSH transport in this case is error prone and a bad practice. There is no reason not to change to HTTPS which is fully supported and will never request credentials for read-only operations.

[iedemam]

A patch provided by @ttsou to clone.sh reminded this is still a pain for people. I've swapped all submodule references to use HTTPS and applied his patch to the dev script. Things should be clone-able without need for SSH keys now.