The dynamic infrastructure framework for everybody! Distribute the workload of many different scanning tools with ease, including nmap, ffuf, masscan, nuclei, meg and many more!
MIT License
4.06k
stars
645
forks
source link
bug when two instances share the same $gen_name #487
there is a bug when two cloud instances have the same $gen_name, axiom generates a malformed ssh config file which prevents using any instance. Logic should be added that regenerates the name if a collision occurs.
tmp workaround:
option 1:
log into cloud provider web dashboard (or via the CLI) and manually delete instances with duplicate hostnames.
option 2:
edit the local ssh config axiom uses (~/.axiom/.sshconfig) to remove the duplicate entries, then run axiom-ssh --just-generate cache to permanently lock/prevent axiom from regenerating the ssh config. ( to revert run axiom-ssh --just-generate or axiom-ssh --just-generate public
there is a bug when two cloud instances have the same $gen_name, axiom generates a malformed ssh config file which prevents using any instance. Logic should be added that regenerates the name if a collision occurs.
tmp workaround: option 1: log into cloud provider web dashboard (or via the CLI) and manually delete instances with duplicate hostnames. option 2: edit the local ssh config axiom uses (~/.axiom/.sshconfig) to remove the duplicate entries, then run
axiom-ssh --just-generate cacheto permanently lock/prevent axiom from regenerating the ssh config. ( to revert runaxiom-ssh --just-generateoraxiom-ssh --just-generate public