pry0cc/axiom

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!

axiom's Issues

Packer Build Hangs / Fails

Every now and then a build fails with a command mentioning GPG keyservers.

This occurs because of a bug with dirnmgr (I think), this happens so sporadically so I have no idea if it has been fixed yet.

If you get a build fail - just rerun the commands:

axiom-update && axiom-build

Tool gf requires additional setup steps to function as intended

According to https://github.com/tomnomnom/gf after installing it using Go, you need to create a ~/.gf/ folder and copy the .json files from /examples folder there. Then, for the autosuggestion/autocomplete function to work you need to source a specific file. Additional filters can be found here: https://github.com/1ndianl33t/Gf-Patterns which would also be nice to include :)

Running axiom-fleet deletes input file

I have been trying out axiom-fleet and I noticed that axiom-fleet "host/path/to/domains.txt" -m=amass -o=outfile.txt deletes "host/path/to/domains.txt"

I think this is because of rm $src here:

axiom/interact/includes/functions.sh

Line 229 in 87eabe4

rm $src

Please let me know if I'm doing it wrong 😅

Huge fan of axiom, I'll try and contribute to this project soon! Cheers!

Password required for created droplets

The problem I'm experiencing is similar to #37, except that when I run axiom-fleet all the instances created ask me to actually fill in the password. That doesn't work well during automation.

Did I make a configuration mistake?

Hope someone knows what goes wrong. Thanks in advance.

axiom-configure fails due to missing 'packer' package on Ubuntu server 20.04.1

The following text is repeated forever:

Building image axiom... This can take up to 25 minutes so please be patient!
Ocassionally this will fail, we  don't know why, but it should auto-restart.
/root/.axiom/interact/axiom-build: line 46: packer: command not found
Your build failed :( Please take a look at the errors!
Builds may fail every now and then, there are some known bugs in Ubuntu Server that cause this.
Im sorry, but it just fails sometimes, just sit back and relax and we'll try again until  it works ;) 

The "packer" package is available in debian's, ubuntu's and arch's default repos. If someone can verify that manjaro, fedora and ubuntuwsl also have it in their default repos, I'll send a pull request to update axiom-configure.

Add an ability to select a region during axiom-configure

By default, it's "San Francisco, United States", so please let us select different locations or add an automated selection based on ping measurement.

Running nuclei via axiom-exec hangs

Hello,
I have an issue with axiom : when I try to run nuclei from axiom-exec it hangs after a few lines printed.
I run the following command :

axiom-exec "~/go/bin/nuclei -l ~/urls.txt -t /home/op/templates -o /home/op/work/nuclei.txt" droplet_name

I attached a screenshot which may be more clear

and it nevers finish the command, but it work if I connect via ssh on it and type the same command.

Best regards,
Neolex

New box username & onetime password in email

Hi @pry0cc,

Thank you for this awesome tool!

I've noticed some strange/unnecesary behaviour when starting up new boxes.

Example: axiom-init hades --restore=hades && axiom-ssh --tmux && axiom-rm hades -f (Economics)

Whenever I run this command and detach from tmux the box is destroyed. Now, when I'm executing the same command again everything works just fine. No passwords etc have been provided etc because the system works with ssh. Nothing strange so far.

However, when checking my inbox I noticed that I've received a couple of emails from Digital Ocean containing the information for my new box:

Your new Droplet is all set to go! You can access it using the following credentials:

Droplet Name: pain
IP Address: 1.1.1.1 (dummy)
Username: root
Password: deadbeefdeadbeefdeadbeef

For security reasons, you will be required to change this Droplet’s root password when you login. You should choose a strong password that will be easy for you to remember, but hard for a computer to guess. You might try creating an alpha-numerical phrase from a memorable sentence (e.g. “I won my first spelling bee at age 7,” might become “Iwm#1sbaa7”). Random strings of common words, such as “Mousetrap Sandwich Hospital Anecdote,” tend to work well, too.

As an added security measure, we also strongly recommend adding an SSH key to your account.

Is it possible to disable this? Axiom does not use the root user with password authentication as far as I'm aware of and the SSH key has been added during setup.

Kind regards,
x1m

The installation is not stopping

I am trying to install axiom in Ubuntu 20.04 .
It needed "apt-get install libnotify-bin" to start .

After that the installation goes on for hours .In the the digital ocean activity tab its showing like this

more than 20 times

thanks
siLLyDaddy

axiom-configure fails on nuclei installation

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...

install fails on kali 2020

everything goes well until

==> digitalocean: W: GPG error: http://archive.ubuntu.com/ubuntu eoan InRelease: Splitting up /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_eoan_InRelease into data and signature failed                                                                                                                                                                          
==> digitalocean: E: The repository 'http://archive.ubuntu.com/ubuntu eoan InRelease' is not signed.
==> digitalocean: W: GPG error: http://archive.ubuntu.com/ubuntu eoan-updates InRelease: Splitting up /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_eoan-updates_InRelease into data and signature failed                                                                                                                                                          
==> digitalocean: E: The repository 'http://archive.ubuntu.com/ubuntu eoan-updates InRelease' is not signed.
==> digitalocean: W: GPG error: http://archive.ubuntu.com/ubuntu eoan-backports InRelease: Splitting up /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_eoan-backports_InRelease into data and signature failed                                                                                                                                                      
==> digitalocean: E: The repository 'http://archive.ubuntu.com/ubuntu eoan-backports InRelease' is not signed.
==> digitalocean: Provisioning step had errors: Running the cleanup provisioner, if present...
==> digitalocean: Destroying droplet...
==> digitalocean: Deleting temporary ssh key...
Build 'digitalocean' errored: Script exited with non-zero exit status: 100.Allowed exit codes are: [0]

==> Some builds didn't complete successfully and had errors:
--> digitalocean: Script exited with non-zero exit status: 100.Allowed exit codes are: [0]

==> Builds finished but no artifacts were created.

Issued with axiom commands

Im quite possibly a moron. I'm running on OSx.

I was able to use the bash oneline to provision the instance, but i do not seem to have the axiom command on my machine

❯ axiom-init
zsh: command not found: axiom-init
❯ axiom

Uploading local files

Hi,
Is there any way we can upload local files to the droplets? I tried scp but getting the following error:
ssh: connect to host x.x.x.x port 22: Connection refused

Temporary failure resolving mirrors.digitalocean.com

Running the script on arch (with doctl installed)

digitalocean: Err:1 http://security.ubuntu.com/ubuntu eoan-security InRelease
digitalocean: Temporary failure resolving 'security.ubuntu.com'
digitalocean: Err:2 http://dl.google.com/linux/chrome/deb stable InRelease
digitalocean: Temporary failure resolving 'dl.google.com'
digitalocean: Err:3 http://ppa.launchpad.net/longsleep/golang-backports/ubuntu eoan InRelease
digitalocean: Temporary failure resolving 'ppa.launchpad.net'
digitalocean: Err:4 http://apt.vulns.sexy stable InRelease
digitalocean: Temporary failure resolving 'apt.vulns.sexy'
digitalocean: Err:5 https://download.docker.com/linux/ubuntu eoan InRelease
digitalocean: Temporary failure resolving 'download.docker.com'
digitalocean: Err:6 http://mirrors.digitalocean.com/ubuntu eoan InRelease
digitalocean: Temporary failure resolving 'mirrors.digitalocean.com'
digitalocean: Err:7 http://mirrors.digitalocean.com/ubuntu eoan-updates InRelease
digitalocean: Temporary failure resolving 'mirrors.digitalocean.com'
digitalocean: Err:8 http://mirrors.digitalocean.com/ubuntu eoan-backports InRelease
digitalocean: Temporary failure resolving 'mirrors.digitalocean.com'
digitalocean: Reading package lists...
digitalocean: W: Failed to fetch http://mirrors.digitalocean.com/ubuntu/dists/eoan/InRelease Temporary failure resolving 'mirrors.digitalocean.com'
digitalocean: W: Failed to fetch http://mirrors.digitalocean.com/ubuntu/dists/eoan-updates/InRelease Temporary failure resolving 'mirrors.digitalocean.com'
digitalocean: W: Failed to fetch http://mirrors.digitalocean.com/ubuntu/dists/eoan-backports/InRelease Temporary failure resolving 'mirrors.digitalocean.com'
digitalocean: W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/eoan-security/InRelease Temporary failure resolving 'security.ubuntu.com'
digitalocean: W: Failed to fetch http://apt.vulns.sexy/dists/stable/InRelease Temporary failure resolving 'apt.vulns.sexy'
digitalocean: Installing sn0int
digitalocean: W: Failed to fetch https://download.docker.com/linux/ubuntu/dists/eoan/InRelease Temporary failure resolving 'download.docker.com'
digitalocean: W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/InRelease Temporary failure resolving 'dl.google.com'
digitalocean: W: Failed to fetch http://ppa.launchpad.net/longsleep/golang-backports/ubuntu/dists/eoan/InRelease Temporary failure resolving 'ppa.launchpad.net'
digitalocean: W: Some index files failed to download. They have been ignored, or old ones used instead.
digitalocean: Reading package lists...
digitalocean: Building dependency tree...
digitalocean: Reading state information...
digitalocean: E: Unable to locate package sn0int
digitalocean: Provisioning step had errors: Running the cleanup provisioner, if present...
digitalocean: Destroying droplet...
digitalocean: Deleting temporary ssh key...
Build 'digitalocean' errored: Script exited with non-zero exit status: 100.Allowed exit codes are: [0]

Error occurs shortly after creating the GPG pubkey
Build fails because the urls are not resolving on the box.

Error: 422 You specified an invalid image for Droplet creation.

==> digitalocean: Creating droplet...
==> digitalocean: Error creating droplet: POST https://api.digitalocean.com/v2/droplets: 422 You specified an invalid image for Droplet creation.

This worked initially. Retried with fresh git clone of repo. Same issue persists.

Errors from digitalocean during the droplet installation

digitalocean: # Executing docker install script, commit: 26ff363bcf3b3f5a00498ac43694bf1c7d9ce16c
==> digitalocean: + sh -c apt-get update -qq >/dev/null
==> digitalocean: + sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
==> digitalocean: + sh -c curl -fsSL "https://download.docker.com/linux/ubuntu/gpg" | apt-key add -qq - >/dev/null
==> digitalocean: Warning: apt-key output should not be parsed (stdout is not a terminal)
==> digitalocean: + sh -c echo "deb [arch=amd64] https://download.docker.com/linux/ubuntu eoan stable" > /etc/apt/sources.list.d/docker.list
==> digitalocean: + sh -c apt-get update -qq >/dev/null
==> digitalocean: + [ -n  ]
==> digitalocean: + sh -c apt-get install -y -qq --no-install-recommends docker-ce >/dev/null
==> digitalocean: debconf: unable to initialize frontend: Dialog
==> digitalocean: debconf: (TERM is not set, so the dialog frontend is not usable.)
==> digitalocean: debconf: falling back to frontend: Readline
==> digitalocean: debconf: unable to initialize frontend: Readline
==> digitalocean: debconf: (This frontend requires a controlling tty.)
==> digitalocean: debconf: falling back to frontend: Teletype
==> digitalocean: dpkg-preconfigure: unable to re-open stdin:
==> digitalocean: + sh -c docker version

Updating error

When trying to do the latest update I get the following error message:

Updating 3c153dc..185443b
error: Your local changes to the following files would be overwritten by merge:
configs/authorized_keys
Please commit your changes or stash them before you merge.
Aborting

Not sure what I should do here.

/dev/fd/63: line 62: [Ubuntu: command not found

root@xxxxxx:~# bash <(curl -s https://raw.githubusercontent.com/pry0cc/axiom/master/interact/axiom-configure)
Hello! Welcome to Axiom configuration :)
To begin, I will ask you a few questions
Press enter to continue
Installing deps! Please wait :)
/dev/fd/63: line 62: [Ubuntu: command not found

on ubuntu 18.04

installation continues, but the script does not have permissions to create folders

Error from digitalocean diring the droplet installation:

==> digitalocean:   Failed building wheel for pipsi

Add support to use bitlaunch API for DO

bitlaunch can do cryptocurrency payment for DO, no annoying check, pretty cool for Axiom.
DO payment is really a painful thing especially student like me.

Feature Request: New tools to include

Hackerone has released a list of tools:

https://www.hackerone.com/blog/100-hacking-tools-and-resources

It would be a great addition to axiom to include some of these tools :)

axiom-build takes a while

Is it possible to source some files from github other than from the locally cloned repo? to reduce setup time.

I noticed this part takes a while to complete and it's just uploading files from my machine esp the last 2 files.

Configuration change makes configure hang

I am stuck while configuring my axiom machine with following log

digitalocean: snapd.failure.service is a disabled or a static unit, not starting it.
digitalocean: snapd.snap-repair.service is a disabled or a static unit, not starting it.
digitalocean: Setting up openssh-sftp-server (1:8.0p1-6ubuntu0.1) ...
digitalocean: Setting up openssh-server (1:8.0p1-6ubuntu0.1) ...
digitalocean: debconf: unable to initialize frontend: Dialog
digitalocean: debconf: (TERM is not set, so the dialog frontend is not usable.)
digitalocean: debconf: falling back to frontend: Readline
digitalocean: Configuring openssh-server
digitalocean: --------------------------
digitalocean:
digitalocean: A new version (/tmp/fileqFciuG) of configuration file /etc/ssh/sshd_config is
digitalocean: available, but the version installed currently has been locally modified.
digitalocean:
digitalocean: 1. install the package maintainer's version
digitalocean: 2. keep the local version currently installed
digitalocean: 3. show the differences between the versions
digitalocean: 4. show a side-by-side difference between the versions
digitalocean: 5. show a 3-way difference between available versions
digitalocean: 6. do a 3-way merge between available versions
digitalocean: 7. start a new shell to examine the situation
digitalocean:

Any fix for that?

Warning from digitalocean during the droplet installation

==> digitalocean: Don't run Bundler as root. Bundler can ask for sudo if it is needed, and
==> digitalocean: installing your bundle as root will break this application for all non-root
==> digitalocean: users on this machine.

This makes sense, isn't it?

Issue with axiom-init on ParrotSecOS

So, I've been running this on Ubuntu and it runs great. Today, I tried to install on a Parrot OS VM and have been having some issues, but I'm running into this permission error and I'm trying to find a way around it. It allows me to run the bash one-liner in Tilix emulator but not in Konsole and not on either while in tmux. When I run one-liner in Tilix, it will install the commands in Konsole, but they will not work in Tilix, after restarting Tilix, obviously. The one liner runs through just like in Ubuntu( I did not compare them line by line, but the final output is the same.) I know this must be a configuration error on my end, and I can see that I don't have permissions to /tmp/packer-xxxx..., but I'm stuck. I'm also have a problem with zsh and tilix where my zsh config is only sourced and in Tilix, but opening up Konsole, displays the default shell for Parrot. I'm assuming the two are linked in some way. Any help would be greatly appreciated.

└──╼ $./axiom-configure
Hello! Welcome to Axiom configuration :)
To begin, I will ask you a few questions
Press enter to continue

Installing deps! Please wait :)
go: /usr/bin/go /usr/lib/go /usr/share/go /usr/share/man/man1/go.1.gz
warning: Pulling without specifying how to reconcile divergent branches is
discouraged. You can squelch this message by running one of the following
commands sometime before your next pull:

git config pull.rebase false # merge (the default strategy)
git config pull.rebase true # rebase
git config pull.ff only # fast-forward only

You can replace "git config" with "git config --global" to set a default
preference for all repositories. You can also pass --rebase, --no-rebase,
or --ff-only on the command line to override the configured default per
invocation.

Already up to date.
What is your DigitalOcean API key?
Key >> xxxxx...
Setting up doctl!...
Using token [xxxxx...]

Validating token... OK

Detected SSH public key, would you like me to install this for your axiom setup? y/n
y
You're running Bash! Installing Axiom to $PATH...
Beginning first packer build...
Failed to initialize build 'digitalocean': error initializing builder 'digitalocean': Unrecognized remote plugin message: Error starting plugin server: listen unix /tmp/packer-plugin428766856: listen: operation not permitted
digitalocean output will be in this color.

==> Builds finished but no artifacts were created.

axiom-scp issue

There appears to be an issue with axiom-scp which affects the command when the instance names are similar to the files that are being extracted.

This was shown with the instance: "mog*" and the files "tcp.common.nmap" which resulted in the following:

scp: /home/op/tcp.commog01n.nmap: No such file or directory
scp: /home/op/tcp.commog02n.nmap: No such file or directory

Renaming the file to tcp.random.nmap fixed the issue temporarily.

pkg_resources.DistributionNotFound: The 'tqdm==4.36.1'

Hi,

I am seeing an error when in run the axiom-scan command.

configutation error makes axiom fails to ssh

I have few instances which is tied to private VPC, so that axiom adds additional private IP field to .sshconfig. So it makes ssh configuration errors in while connecting to instance. I tried re-configuring it manually but axiom updates the config as I run the command

Here is my .sshconfig

Host server
HostName

User op
Port 2266

Host recon
HostName

User op
Port 2266

Host jackson14
HostName
User op
Port 2266

NOTE: jackson14 was created using axiom others are my old instances

This should be installed on a local machine or VPS ?

Hello,

In addition to the question in the title, here is another one:
Can we add more packages than the default ones ? is there any flexibility there ?

Thanks in advance,

no such file or directory: packer.json

So, I'm attempting to run the bash one liner on a new install of Linux and it looks like the packer json file is no longer in the repo. I noticed this earlier when I ran axiom-update on another machine and then went to run axiom-build and got this same issue. I luckily had a pull from a few weeks back and just copied the packer.json into .axiom directory. I'm I doing something wrong here or is this a mistake?

Bug when running axiom-init, Error: open /tmp/raman18.sh: no such file or directory

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.

Error: (droplet.create.image) command is missing required arguments

I am trying to axiom-init and it is gives me :
Error: (droplet.create.image) command is missing required arguments

Clean axiom-configure does not include interlace install needed to use axiom-scan.

Problem:
After installing axiom and running axiom-scan for the first time it can't find interlace.

Solution:
Add interlace install to axiom-configure or provide a notice to install interlace.

Partly copied from your setup in the packer build.

git clone https://github.com/codingo/Interlace.git /tmp/interlace 
cd /tmp/interlace && sudo python3 setup.py install

Note this was run on a Parrot OS machine.

Detect id_ed25519.pub key

hey! right now there's only a check for:

if [ -f ~/.ssh/id_rsa.pub ]

it would be great if it would also check for non-rsa keys, the most popular being ed25519. So if ~/.ssh/id_rsa.pub doesn't exist you could check for ~/.ssh/id_ed25519.pub as a fallback. :)

You can test this by generating a keypair with ssh-keygen -t ed25519.

Golang install not detected on Mac OS installation

Looks like a great tool! Golang is not detected on my Mac OS install, see the following screenshot:

It is because I don't have $GOPATH explicitly set as an environment variable, despite having golang installed.

axiom-init: command not found

I've tried multiple time as getting the same outcome. Am I missing anything. I've set this up before and was working last week, now on a new droplet this is what I am receiving with no errors on build.

==> Builds finished. The artifacts of successful builds are:
--> digitalocean: A snapshot was created: 'axiom-sfo2-1599448086' (ID: 69684403) in regions 'sfo2'
Your build completed successfully!
To initialize an instance, run axiom-init
Pruning old Axiom images...
Deleting 'axiom-sfo2-1599445907'...
Old Snapshots deleted successfully!
root@axiombox:~# axiom-init
axiom-init: command not found

Getting error while installing

Builds may fail every now and then, there are some known bugs in Ubuntu Server that cause this.
Im sorry, but it just fails sometimes, just sit back and relax and we'll try again until it works ;)
Building image full for provider do... This can take up to 25 minutes so please be patient!
Ocassionally this will fail, we don't know why, but it should auto-restart.
/root/.axiom/interact/axiom-build: line 44: packer: command not found

Arch Question

Hello, This issue might be because I am on Arch.
But will ask anyway, I ensured all dependency is installed and got the DigitalOcean key.. looks okay then this:

/dev/fd/63: line 185: 230812 Killed packer build -var-file ~/.axiom/axiom.json ~/.axiom/packer.json

The full output here: https://pastebin.com/QAizNMaQ

I'll spin up ubuntu if I have to, but any advice would be great.

Nuclei v2 Update

Nuclei v2 has been released, is it possible to update the build?

Feature Request : zsh shell customizations sync

Currently the backup/sync functionality only syncs non image default values so any customizations to the shell are not saved. It would be nice to have a flag to backup and restore changes to the shell and other dot files.

Feature Request - Hashcat

Is it possible to add Hashcat into Axiom?

Packer / axiom-configure build fails

Very occasionally, you'll get an error talking about Ubuntu and APT complaining that the build failed.

All you need to do in this case is rerun the script, it'll work. Keep running it until it does, it's an ubuntu bug, I'm sorry :(

Request: AWS EC2 Support

This looks like an cool project, but only being able to use Digital Ocean is a bit limited. Are there any plans to add AWS support? And what are the features / benefits of adding a Digital Ocean API key?

Zsh is not detected due to incorrect shell path

Currently, the user's default shell is detected by checking the $SHELL variable. The paths used to check the shells are hardcoded in axiom-configure. For any path that is not included in this file, the default shell is not detected.

e.g On my machine running Arch Linux, I've my Zsh installed through Pacman. The $SHELL variable is set to /bin/zsh for me. As a result, axiom-configure does not detect Zsh as my default shell, since the path is not hardcoded on line 180 of axiom-configure

A better method for checking the default shell is to consult the user's /etc/passwd entry and read the default shell from there. The following bash two liner quickly solves the issue.

user_entry=$(getent passwd | grep "^$USER")  # Grabs the user's passwd entry
user_shell=${user_entry##*/}  # Grabs the text after last slash of the passwd file (shell name)

The bash script outputs $user_shell as "zsh" on my Arch machine and "bash" on my Ubuntu WSL2, where bash is default.

Unable to ssh after axiom-configure

First off, great work!

After I run configure, I am unable to connect to the droplets that are created. I am on Mac OS Mojave. The same keys work for my existing droplets without any problem.

Any ideas why this could be happening? Any tips to troubleshoot?

jq & packer

Hello.

I've just tried setting up my first instance with axiom-configure as recommended in the readme. I'm running Linux Mint 19.3 ( Linux flagship 5.3.0-51-generic #44~18.04.2-Ubuntu SMP Thu Apr 23 14:27:18 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux).

On my first attempt I got an error with jq and packer being unknown commands:

You're running Bash! Installing Axiom to $PATH... /dev/fd/63: line 193: jq: command not found Beginning first packer build... /dev/fd/63: line 197: packer: command not found

I've installed them via apt. After that, I'm getting the following:

`You're running Bash! Installing Axiom to $PATH...
jq - commandline JSON processor [version 1.5-1-a5b5cbe]
Usage: jq [options] [file...]

jq is a tool for processing JSON inputs, applying the
given filter to its JSON text inputs and producing the
filter's results as JSON on standard output.
The simplest filter is ., which is the identity filter,
copying jq's input to its output unmodified (except for
formatting).
For more advanced filters see the jq(1) manpage ("man jq")
and/or https://stedolan.github.io/jq

Some of the options include:
 -c		compact instead of pretty-printed output;
 -n		use `null` as the single input value;
 -e		set the exit status code based on the output;
 -s		read (slurp) all inputs into an array; apply filter to it;
 -r		output raw strings, not JSON texts;
 -R		read raw strings, not JSON texts;
 -C		colorize JSON;
 -M		monochrome (don't colorize JSON);
 -S		sort keys of objects on output;
 --tab	use tabs for indentation;
 --arg a v	set variable $a to value <v>;
 --argjson a v	set variable $a to JSON value <v>;
 --slurpfile a f	set variable $a to an array of JSON texts read from <f>;
See the manpage for more options.

Beginning first packer build...
invalid value "/home/hostilenode/.axiom/axiom.json" for flag -var-file: Error reading variables in '/home/hostilenode/.axiom/axiom.json': EOF
Usage: packer build [options] TEMPLATE

Will execute multiple builds in parallel as defined in the template.
The various artifacts created by the template will be outputted.

Options:

-color=false Disable color output (on by default)
-debug Debug mode enabled for builds
-except=foo,bar,baz Build all builds other than these
-only=foo,bar,baz Build only the specified builds
-force Force a build to continue if artifacts exist, deletes existing artifacts
-machine-readable Machine-readable output
-on-error=[cleanup|abort|ask] If the build fails do: clean up (default), abort, or ask
-parallel=false Disable parallelization (on by default)
-var 'key=value' Variable for templates, can be used multiple times.
-var-file=path JSON file containing user variables.
`

Any thoughts? Mismatching jq / packer versions?

The repository is not signed.

Used command:-

bash <(curl -s https://raw.githubusercontent.com/pry0cc/axiom/master/interact/axiom-configure)

Output error:-

    digitalocean: Get:45 http://archive.ubuntu.com/ubuntu eoan-backports/multiverse amd64 c-n-f Metadata [116 B]
    digitalocean: Fetched 16.3 MB in 7s (2227 kB/s)
    digitalocean: Reading package lists...
==> digitalocean: W: GPG error: http://archive.ubuntu.com/ubuntu eoan InRelease: Splitting up /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_eoan_InRelease into data and signature failed
==> digitalocean: E: The repository 'http://archive.ubuntu.com/ubuntu eoan InRelease' is not signed.
==> digitalocean: W: GPG error: http://archive.ubuntu.com/ubuntu eoan-updates InRelease: Splitting up /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_eoan-updates_InRelease into data and signature failed
==> digitalocean: E: The repository 'http://archive.ubuntu.com/ubuntu eoan-updates InRelease' is not signed.
==> digitalocean: W: GPG error: http://archive.ubuntu.com/ubuntu eoan-backports InRelease: Splitting up /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_eoan-backports_InRelease into data and signature failed
==> digitalocean: E: The repository 'http://archive.ubuntu.com/ubuntu eoan-backports InRelease' is not signed.
==> digitalocean: Provisioning step had errors: Running the cleanup provisioner, if present...
==> digitalocean: Destroying droplet...
==> digitalocean: Deleting temporary ssh key...
Build 'digitalocean' errored: Script exited with non-zero exit status: 100.Allowed exit codes are: [0]

==> Some builds didn't complete successfully and had errors:
--> digitalocean: Script exited with non-zero exit status: 100.Allowed exit codes are: [0]

==> Builds finished but no artifacts were created.

axiom-execb can't find host

Hello,

After updating to the latest changes for Axiom and re-configuring everything, I noticed axiom-execb runs into errors.

axiom-execb "shuffledns -list domains.txt -r resolvers.txt -d example.com -o example.txt" "example01"

Results in

Executing in the background on example01 at  
ssh: Could not resolve hostname : Name or service not known
ssh: Could not resolve hostname : Name or service not known

I've verified I can connect to the host just fine using axiom-connect example01.

--restore=

When I do a --restore=existing box axiom has recently stopped loading the data from the existing box into the new one.

axiom-init failes with "doctl: command not found"

kusayu@desctop ~ $ axiom-init        
Initializing 'jang21'
/home/kusayu/.axiom/interact/axiom-init: line 103: doctl: command not found
/home/kusayu/.axiom/interact/axiom-init: line 107: doctl: command not found
>> T-Minus 59 to stage-1 Lift Off!
>> T-Minus 58 to stage-1 Lift Off!
/home/kusayu/.axiom/interact/axiom-init: line 121: doctl: command not found
Initialized! Instance accessible at ''!
To connect, run 'axiom-ssh jang21'
kusayu@desctop ~ $ 
kusayu@desctop ~ $ 
kusayu@desctop ~ $ axiom-ssh jang21
/home/kusayu/.axiom/interact/axiom-ssh: line 27: doctl: command not found
ssh: Could not resolve hostname : Name or service not known
kusayu@desctop ~ $ which doctl
doctl not found
kusayu@desctop ~ $ locate doctl
/home/kusayu/Disk/kusayu/.oh-my-zsh/plugins/doctl
/home/kusayu/Disk/kusayu/.oh-my-zsh/plugins/doctl/README.md
/home/kusayu/Disk/kusayu/.oh-my-zsh/plugins/doctl/doctl.plugin.zsh
/usr/share/oh-my-zsh/plugins/doctl
/usr/share/oh-my-zsh/plugins/doctl/README.md
/usr/share/oh-my-zsh/plugins/doctl/doctl.plugin.zsh
kusayu@desctop ~ $ uname -a
Linux desctop 5.7.10-arch1-1 #1 SMP PREEMPT Wed, 22 Jul 2020 19:57:42 +0000 x86_64 GNU/Linux
kusayu@desctop ~ $