4 ms·
My public keys are public for a reason though. I can’t imagine why you’d ever turn on ForwardAgent by default.
by Aeolun 4y ago
My public keys are public for a reason though.
I can’t imagine why you’d ever turn on ForwardAgent by default.
- colinsane 4y ago> My public keys are public for a reason though. in the ideal, yes. but it wasn’t long ago (start of covid really) that i kept my personal and work ssh keys under the same profile. both of those alone are “public”, but that they correspond to the same identity perhaps ought not to be. yeah, there are better ways to manage separate identities (separate users, VMs, VPNs)… and reminding people that `ssh host-name` can reveal all your ssh keys is a good way to push people toward those better solutions! :)
- Aeolun 4y ago> reminding people that `ssh host-name` can reveal all your ssh keys is a good way to push people toward those better solutions! I guess I just take issue with the fear mongering. People often make it sound like the end of the world to not be perfectly anonymous.
- datadeft 4y agoIs this the case with this config as well? Host one HostName one.of.the.server.sh User hn IdentityFile ~/.ssh/one.of.the.server.sh.key
- sneak 4y agoMisconfiguration, or lack of understanding of what the agent does and how it works. It's not always clear the inheritance priority of directives with wildcards in ssh_config or .ssh/config. I think it's the opposite of what one might assume is the default, if I recall correctly.
- Aeolun 4y agoI’m not sure, connecting to an unknown server and giving that remote session the same abilities as my local PC has always seemed like a bad idea to me. I guess you could misconfigure it, but it’s one of those things where I’d painstaking ensure I set it up correct because doing it wrong is not an option. Maybe it’s because I almost always go direct?
- chrismorgan 4y ago> My public keys are public for a reason though. You may reasonably not care, but it’s also reasonable to care. It’s not about them being public, it’s about announcing them. For me, running `ssh git.charm.sh` would have SSH essentially say “hi, I’m chris-morgan on GitHub (and here’s cryptographic proof)” as part of connecting. That’s a huge privacy leak. It’s disclosing all your identities automatically, including perhaps that you work for ACME Corporation, and isn’t that a valuable tid-bit for social engineering attacks, when you take all these things together. (I think it’s worth noting of your pithy line that the two words spelled “public” are homonyms, not at all the same. The first one I might call cryptographic-public, and the second socially-public. There’s no need to share a (cryptographic-)public key (socially-)publicly, and doing so can be actively undesirable.)
- Aeolun 4y agoAs a matter of connecting it’s announcing that I’m user bart.riepe. It’s not a big leap from there to figuring out who I am. A public key (to me) is public in the same sense that a client secret is public. You don’t have to advertise it to everyone, but if anybody finds it they can’t do anything bad with it (except confirm you are the person that has the private key).
- chrismorgan 4y agoThis isn’t a technical security vulnerability, because the cryptography is sound. But it is an information disclosure vulnerability, because it didn’t need to disclose your identity, and the typical user will not expect it to disclose all their identities. And the information that is disclosed opens heavy social vulnerabilities, because your activity can now be perfectly correlated with who you are, by an untrusted party. This is information that businesses put huge amounts of effort into attempting to do on the web, because it can be quite valuable (sometimes absurdly so). And SSH defaults to just giving them exactly what they want so they don’t even have to work for it.
- wootland 4y agoDo you feel the same way about GitHub/GitLab... because Git works over SSH and anytime you clone anything over the SSH protocol your public keys are sent to the server. Same thing with SSHing into AWS, Google Cloud, Azure consoles. I don't think exposing your public key has ever been an issue for most people, and for those that it is, they can configure SSH access as you have in your parent comments.