On Fri, Jan 31, 2014 at 9:34 AM, Daniela Engert
Am 31.01.2014 15:53 schrieb Paul A. Bristow:
Is it worth continuing to try to get the SSH method to work? I've had another go at using SSH, and got it working> But it now asks for passphrase for every module which is clearly intolerable.
So true, but you just need a pageant (-like) helper to leave this annoying passphrase thing behind you. I'm running KeePass as secure password/certificate store with the KeeAgent plugin to serve ssh certificates. Both commandline git and TortoiseGit are configured using TortoisePLink (which is the default afaik). Annoyance-Be-Gone!
My git configs contain lines similar to
[remote "origin"] url = git@github.com:boostorg/boost.git pushurl = boost-is-read-only
With all of this in place you get security, ease-of-use, and the most effective transport mechanism.
Ciao Dani
One advantage of http(s) over ssh is that it is more likely to get through any company firewalls you might have in your way. After you get an ssh helper working as described above, you might want to follow these GitHub instructionshttps://help.github.com/articles/using-ssh-over-the-https-port to do ssh through an http(s) port. Michael
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost