4 ms·
I know this is positioned as a hacking tool, but it seems actually pretty useful. It's pretty easy to lose track of where your keys are used and how you might p
by godelski 3y ago
I know this is positioned as a hacking tool, but it seems actually pretty useful. It's pretty easy to lose track of where your keys are used and how you might perform hops. Having that diagram be generated for you really looks useful and can help you navigate this.
I'm sure there are good practices to solve this (and please suggest them, I'm always looking to learn more), but I'm no expert. I do daily drive linux and am terminally terminal, so it wouldn't surprise me if the GUI people are even worse. I think this is a general problem with a lot of terminal based tools, is that there are far higher expectations to read the documentation and less focus on design (and importantly, design that makes sense to someone that isn't you). Totally fine for hacky projects but with something as mature as ssh it seems like we'd have far better tools built in or to exist. I'm sure many do exist, but are they well known? (I'm happy to see any tools if you all have some suggestions)
- chaps 3y agoYes, it is a very useful tool. Used to do very similar when I worked as a sysadmin in larger infrastructures that largely get managed over ssh. A surprisingly large number of infrastructures have keys setup for individual sysadmins across all hosts, through straight sshd user auth. One problem this helps with is getting into older servers with an unknown password and can't be rebooted for business reasons. At some point, some person may have setup keys to that host, and the only way to find out which is to basically try all hosts and all users. So having something that snakes through an infrastructure like this would help get into that host.