You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all, I downloaded ArcherySec today following the instructions given in the documentation: git clone https://github.com/archerysec/archerysec.git cd archerysec NAME=<NAME OF USER> EMAIL=<EMAIL ID OF USER> PASSWORD=<USER ACCOUNT PASSWORD> bash setup.sh
I subsequently use the command: bash run.sh
and going to the specific address and port, I get the classic screen where I login, so everything seems to be working correctly for the time being.
Reading the documentation it is specified that you have to set up the connectors and the ones I used are Zaproxy and OpenVas.
For Zaproxy I have no problem but when I go to create the one for OpenVas, once I enter the required information I get the following screen when I try to save:
(Before doing these operations, I have both servers active that allow the use of Zaproxy and OpenVas)
I use Kali Linux virtual machine and If there is anything I am doing wrong, please let me know I am not very knowledgeable about these things.
Second question
I tried using the API supported by ArcherySec, but I can't make the connection and I don't understand exactly what I should do:
Reading the documentation it is specified to download: pip install PyArchery
but once installed and trying later from a python script: from archery import api
I get the error indicating that there is no archery module.
Having this problem, I later tried using the API by directly using endpoints via a script in Python, I then tried translating the following CURL:
Using the following Script:
the response I get by running this script is error, It appears that the page is not found by returning a 404 error, If you know how I could solve these problems I would really appreciate it.
and a doubt I have if I'm using the right endpoint, that is 0.0.0.0:8000 is the host and port where Archery runs when I use the bash command run.sh, Is it right to use this?
The text was updated successfully, but these errors were encountered:
First question
Hi all, I downloaded ArcherySec today following the instructions given in the documentation:
git clone https://github.com/archerysec/archerysec.git
cd archerysec
NAME=<NAME OF USER> EMAIL=<EMAIL ID OF USER> PASSWORD=<USER ACCOUNT PASSWORD> bash setup.sh
I subsequently use the command:
bash run.sh
and going to the specific address and port, I get the classic screen where I login, so everything seems to be working correctly for the time being.
Reading the documentation it is specified that you have to set up the connectors and the ones I used are Zaproxy and OpenVas.
For Zaproxy I have no problem but when I go to create the one for OpenVas, once I enter the required information I get the following screen when I try to save:
(Before doing these operations, I have both servers active that allow the use of Zaproxy and OpenVas)
I use Kali Linux virtual machine and If there is anything I am doing wrong, please let me know I am not very knowledgeable about these things.
Second question
I tried using the API supported by ArcherySec, but I can't make the connection and I don't understand exactly what I should do:
Reading the documentation it is specified to download:
pip install PyArchery
but once installed and trying later from a python script:
from archery import api
I get the error indicating that there is no archery module.
Having this problem, I later tried using the API by directly using endpoints via a script in Python, I then tried translating the following CURL:
Using the following Script:
the response I get by running this script is error, It appears that the page is not found by returning a 404 error, If you know how I could solve these problems I would really appreciate it.
and a doubt I have if I'm using the right endpoint, that is 0.0.0.0:8000 is the host and port where Archery runs when I use the bash command run.sh, Is it right to use this?
The text was updated successfully, but these errors were encountered: