4 ms·
As has been mentioned (repeatedly) this obviously has no use for people using SSH. Indeed, the goal of this tool is explicitly to be helpful for cloud-hosted r
by ethomson 11y ago
As has been mentioned (repeatedly) this obviously has no use for people using SSH. Indeed, the goal of this tool is explicitly to be helpful for cloud-hosted repositories in Visual Studio Team Services (formerly Visual Studio Online). This is helpful for teams that enforce two-factor authentication over HTTPS. The article assumes a bit of knowledge about this, but does indeed mention this:
> We ported this tool to Mac and Linux to simplify their authentication to remote Git repositories, in particular those hosted in Visual Studio Team Services (VSTS).
- tjohns 11y agoI'm curious why they don't add SSH support to Visual Studio Team Services then. :) Edit: Apparently they are. But I still think it would've been better to layer two-factor auth on top of SSH keys, since that can be done securely in a 100% offline manner. Perhaps it's just a cultural difference, since Windows doesn't ship with an SSH client?
- ethomson 11y agoEdit: SSH is coming soon. These are (roughly) orthogonal issues: regardless of whether we support SSH or not, we are going to support HTTPS access to Git repositories. And if we support HTTPS, we must support two-factor authentication. A lot of organizations require this. (In fact, Microsoft itself requires this internally: our authentication to any internal web site uses 2FA.) So Visual Studio Team Services must support HTTPS with two-factor authentication. This is awfully painful to use git core on the command-line without a credential manager to assist you.
- deleted 11y ago[deleted]