Re:A sane SSH(1) key management example
by EduardoRT on Thursday August 18, 2022 @11:27AM
(#32510992)
Not a big deal at all considering that they're public keys, there's no security concern there.
Feels weird, but it's like going into a building that requires a badge and showing proof that you actually own several keys, then the building guard telling you he needs X key to enter since that's the one they know, and it's authorized.
All your public keys in your GitHub account are accessible through a link, just <github.com/<username>.keys>
> Not a big deal at all considering that they're public keys, there's no security concern there.
I might be pushing the analogy too far, but: all the URLs I have visited are public and are not identifying me personally, yet uploading them all together to a third party feels like a breach of privacy.
Re:A sane SSH(1) key management example
by jonnycomputer on Thursday August 18, 2022 @12:52PM
(#32512097)
There is a privacy concern. And that might end up being a security concern depending on the threat model (e.g. social engineering attacks).
So, you'd ask someone to SSH into a server, and you'll get some of his public keys (I think the default limit is 5 keys), what would you do with that? You can also just go to their GitHub profile and fetch the keys or ask them to send you their public keys, they're meant to be public after all.
Here's one of my public keys, for free: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICIc3nOnSnsiAdkjAdH5WR9enQiPYWq1zAVsTDt60e91
Re:A sane SSH(1) key management example
by rgoulter on Thursday August 18, 2022 @11:36AM
(#32511106)
As well as .keys, there's .gpg for GPG keys, and .png for the profile picture.
Host *
IdentitiesOnly yes
To prevent
Re:A sane SSH(1) key management example
by trey-jones on Thursday August 18, 2022 @11:46AM
(#32511225)
It's definitely a convenience over security feature. My personal feeling is that the convenience is worth it in this case, and it's a sensible default.
Re:A sane SSH(1) key management example
by rogeliodh on Thursday August 18, 2022 @12:07PM
(#32511508)
remember CVE-2016-0777 (https://news.ycombinator.com/item?id=10901588)?
Never really thought about it. Feels kind of "leaky", even if necessary.