| > You'd need to have the same private key on every computer you use. No you don't. You use different private keys on different computers, they are really not that expensive to mint. This also simplifies revocation. > "how do I transfer my key?" If you really, really need that, it's very simple: curl https://github.com/Joker-vD/keepassdb/raw/master/Joker_vD.kd... > I prefer that most things I needs SSH for on a particular computer use the default private key Okay? You use non-default keys for hosts that host git repos, everything else gets the default key. I actually use exactly this configuration: my ~/.ssh/config has 4 entries, 3 of them for git servers I have push access to, and the fourth one is for a personal VPS. Everything else gets offered ~/.ssh/id_rsa > There are downsides from the server admin perspective too. That's the server admins' problem, not mine. > SSH can be very finicky when it comes to timeouts, encodings and a bunch of other options Can't really relate here, maybe you're right. But in my experience, it either just works fine, or doesn't work at all, no middle ground. Also, "encodings"? All in all, my experience have been that Git over SSH Just Works™ while Git over HTTPS has all kinds of strange problems, inlcuding half-assedly written HTTP-proxies somewhere in the middle. |