-
Notifications
You must be signed in to change notification settings - Fork 915
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing faraday-client v3.11 ? #402
Comments
Found that report can be uploaded via API server but I cannot find the needed csrf-token parameter |
Hi! Thanks! |
Hi Ilazzaro, Thanks but I am afraid the link that you sent is incorrect ... it is about "Walking tour Deoksugung Palace | Seoul, South Korea" I tried to upload reports using the API but I got 403 because I am missing the csrf_token ? and I don't know where to get it ? |
Can you check again, I updated the link |
Yes much better. Thanks I will look into it |
It worked. I would be fine with that for now and integrate it into my scanning wrapper Thanks for having updated the wiki |
Upload report via API on Kali worked fine however I have faraday installed on Ubuntu 18.04 via Katoolin on Azure as I cannot get Kali and when uploading report I got 400 Bad request instead. Any idea to troubleshoot this ? I have run faraday-server in debug mode but nothing useful displayed |
make sure that all request uses the same server address and that the workspace in the url exists. |
I love the work that the Infobyte team have performed. However, I would agree with this very being beneficial to have the client for each release. I've resorted to using an older version of Faraday just to be able to use the CLI opposed to the API. |
I used the same script and same workspace name that worked with Kali on Ubuntu and still get "Bad Request". I got both cookie and csrf_token, see below. I noticed also that whatever is sent when uploading report (no cookie, wrong ws, no csrf) I always got Bad Request on Ubuntu
|
We just released v1.0.0 of faraday-client, you can download the installers from here. You can also check the source code here. We create a request a ticket for adding the client into kali here I will try to provide a script for uploading the reports soon. Thanks! |
Got a conflict with python-faraday package already installed on Kali when installing the client |
Hi, |
Are you using the server in the same machine as the client? In that case we need to review the conflict from our side. |
Yes, the server and client are on the same machine. Below is the detail of the conflict apt list faraday dpkg: error processing archive faraday-client_amd64.deb (--install): |
glad I found this, been going nuts trying to set this up on a new Kali build. Same issue here: I hadn't realized the conflict til I tried dpkg -i instead of apt install dpkg: error processing archive faraday-client_amd64(1).deb (--install): Trying to run client and server on the same box. |
Hi guys! We uploaded a faraday-client installer without the server conflict. Could you try it again, please? Let us know if did it work for you. Thanks in advance, Diego |
Hi Diego, I installed the faraday-client successfully on Kali and being able to upload a report. Thanks for the good work! |
Hi Thierry, We are glad it worked as expected, so I'll close this issue. For any other problem, feel free to open a new issue or re-open this one. Thanks! |
root@kali:~# faraday-manage status-check
Showing faraday server configuration
version: 3.11.1
bind_address: localhost
port: 5985
websocket_port: 9000
debug: False
Showing faraday plugins data
version: 1.2
Showing dashboard configuration
show_vulns_by_price: False
Showing storage configuration
path: /root/.faraday/storage
Checking if postgreSQL is running...
[+] PostgreSQL is running and up to date
[+] PostgreSQL lock not detected.
[+] PostgreSQL encoding: UTF8
Checking if Faraday is running...
[+] Faraday Server is running. PID:44672
Checking Faraday config...
[+] /.faraday/storage -> Permission accepted
[+] Port 5985 in localhost is open
faraday-client package is missing so it is no more possible to upload reports in Kali.
The text was updated successfully, but these errors were encountered: