4 ms·
[dupe] of https://news.ycombinator.com/item?id=38877185 https://news.ycombinator.com/item?id=38877185 (I'm the author)
by mmsc 3y ago
[dupe] of https://news.ycombinator.com/item?id=38877185 https://news.ycombinator.com/item?id=38877185 (I'm the author)
- frumiousirc 3y agoTraversal progress is blocked by a hashed `authorized_keys` file, right?
- mmsc 3y agoAssuming you mean `known_hosts`, no. It uses various data sources to determine where to try to connect with discovered keys: https://github.com/MegaManSec/SSH-Snake/blob/main/SETTINGS.md#ssh-host-discovery-strategies https://github.com/MegaManSec/SSH-Snake/blob/main/SETTINGS.m... lists all of them (which can be enabled and disabled by the user). https://github.com/MegaManSec/SSH-Snake/blob/main/SETTINGS.md#use_find_from_bash_history https://github.com/MegaManSec/SSH-Snake/blob/main/SETTINGS.m... is particularly interesting.
- frumiousirc 3y agoErr brain fart, yes, `known_hosts`. Thanks for the answer. It seems there is room to expand from checking Bash history to also other popular shells (eg `fish`).