i have added ssh key without password at

~/.ssh/id_rsa.pub ~/.axiom/configs/authorized_keys

and build the instance axiom-build

when axiom-init all new instances are asking for password, though the ssh key has no password set

need help

I ran the following

axiom-scan mysubs.out -m nuclei --spinup 150 -nuclei-templates nuclei-templates-custom/ -anew outputfile.txt -anew output.txt 

This is what I got:

I'm using Linode. I'm using axiom with docker latest version. Why this is happening, is there any solution for it?

I've been running axiom-scan using linode instances and I constantly face the following issue:

One or more instances have a very low performance, for instance, using nuclei some instances run at 140 RPS (requests per second) while others run at 5 or less RPS. I've recreated the instances and I can't figure out why this is happening. I didn't have this type of issues using Digital Ocean.

Is anyone having the same issue?

Sometimes when running scans I get the below message and I need to delete instances and run evertyhing again. But I am not sure why this happens, it doesn't happen to often tho.

ssh: connect to host 45.33.92.201 port 2266: Connection timed out                                                                                                                                           
ssh: connect to host 173.255.233.46 port 2266: Connection timed out                                                                                                                                         
ssh: connect to host 173.255.233.99 port 2266: Connection timed out                                                                                                                                         
ssh: connect to host 173.255.233.93 port 2266: Connection timed out                                                                                                                                         
ssh: connect to host 173.255.233.48 port 2266: Connection timed out                                                                                                                                         
ssh: connect to host 173.255.233.106 port 2266: Connection timed out                                                                                                                                        
ssh: connect to host 173.255.233.67 port 2266: Connection timed out                                                                                                                                         
ssh: connect to host 45.33.92.174 port 2266: Connection timed out

When you run nmap with naabu, You cannot download the XML output as only one extension is allowed. This module is registered as a directory extension, So it could get all files. The Nmap output should be placed in the output directory and it automatically processes the backups created by cp while merging with mmv and creating a sorted list of naabu ports, Nmap merged XML and Nmap merged output.

Example

axiom-scan ~/check.txt -m naabu-nmap -p - -rate 10000 -c 50 -nmap-cli $'\"nmap -sV -A -T4 -oX output/nmap.xml\"' -o out/

WARNING: Command group 'vm' is experimental and under development. Reference and support levels: https://aka.ms/CLI_refstatus ssh: Could not resolve hostname moser15: nodename nor servname provided, or not known

Looks like whatever az commands axiom is using have been changed. :-/

Hello,

My axiom-configure job has ran three times and failed at the same spot each time.

    digitalocean: Installing nuclei
==> digitalocean: go: downloading github.com/projectdiscovery/nuclei v1.1.7
==> digitalocean: go get github.com/projectdiscovery/nuclei/v2/cmd/nuclei: module github.com/projectdiscovery/nuclei@upgrade found (v1.1.7), but does not contain package github.com/projectdiscovery/nuclei/v2/cmd/nuclei
==> digitalocean: Provisioning step had errors: Running the cleanup provisioner, if present...
==> digitalocean: Destroying droplet...
==> digitalocean: Deleting temporary ssh key...

Using restore backup ‘pry0cc/lazy’
Initializing ‘raman18’
Error: open /tmp/raman18.sh: no such file or directory
Initialized! Instance accessible at ‘’!
To connect, run ‘axiom-ssh raman18’
Waiting 65 seconds before restore…
Restoring pry0cc-lazy to raman18 at ’ ’
ssh: Could not resolve hostname : Name or service not known
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(235) [sender=3.1.2]```

This occurs because there is no valid image detected, you need to run `axiom-build` and receive a successful build for your currently selected region.

This is because axiom now checks for axiom-$region as apposed to axiom* in your images, running `axiom-build` will however resolve this.

I did a fresh build, doing:

axiom-update && axiom-build

then

axiom-fleet -i=20

And I get

The other problem I have is that I don't know how to get out of that screen, I keep pressing CONTROL+C and more password prompts appear.

Not really a problem with the tool, but I usually keep a fork of this repo without your public key ;)

~~Haven't looked to see if the program needs configs/authorized_keys to exist. If not, you could probably add it to .gitignore without an issue.~~

Update: axiom-configure seems to work fine without authorized_keys, it created it for me.

notify-send only works on Ubuntu like systems but not e.g. on OSX.

In this PR I extracted the command so we can source it from interact/includes/system-notification.sh as $NOTIFY_CMD already fitted to the current host OS (now Ubuntu likes and OSX).

Many scanning tools such as nmap and httpx support the capability to exclude targets, e.g. --excludefile and -deny, respectively. It'd be nice if an exclusion file could be supplied and transferred up to the instances and used with axiom-scan.

Setting up Axiom for a 2nd time (previously used it) and now getting errors during setup. Would be ideal if this were handled gracefully.

An error occurred (InvalidGroup.Duplicate) when calling the CreateSecurityGroup operation: The security group 'axiom' already exists for VPC 'vpc-HEX_ID_HERE'

An error occurred (InvalidGroupId.Malformed) when calling the AuthorizeSecurityGroupIngress operation: The security-group ID '' is malformed

A web browser has been opened at https://login.microsoftonline.com/organizations/oauth2/v2.0/authorize. Please continue the login in the web browser. If no web browser is available or if the web browser fails to open, use device code flow with az login --use-device-code.

No browser opens. Also where is the code that I need to enter?

Hi ,

I have a request to add DSXS tool in the default provision. This tool is similar to kxss but way more useable and with very less Flase positives.

Here is the link https://github.com/stamparm/DSXS.

Thanks Kind regards

Hi,

Trying to spawn several instances in a single AWS region, nothing fancy, I get this error:

An error occurred (InvalidKeyPair.NotFound) when calling the RunInstances operation: The key pair 'axiom' does not exist

This is a fresh install, axiom version is from Oct 15, 2022.

Any ideas about how this can be resolved?

Thanks!