-
Notifications
You must be signed in to change notification settings - Fork 79
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
New Module: server mode #18
Comments
Hi, I'm interested in this. I haven't used gOSINT before, how would you like to structure the REST API? Do you have any specification in mind? |
Hi, thanks for the interest in this project. I would like to serve one endpoint to trigger scans specifying the type of scan with a special parameter (something like Another endpoint will answer the scan result stored in the database for a single target (if they exists) and, passing the timestamp of the scan the target as parameters will answer with the scan result. The output will be JSON-encoded. Nothing really complex after all, if you are familiar with [GraphQL}(https://graphql.org/) we could just use it instead of REST. Other suggestions are well accepted :) |
Thanks for the highlight. I have read and experimented with GraphQL in the past but for the moment I'd be more confident using REST. Do you have any preference for the Database? |
MySQL would be good but I would like to have an interface for others DBMS leaving freedom to the users |
I've started developing it here: https://github.com/jkomyno/gOSINT/tree/feature/18-server-mode-module |
In order to expose a server, I will need to refactor how the modules function are exported. That means taking them away from the |
There is a big issue here, you started working on a fork of the master branch, note that you should always start from the dev branch (A LOT of stuff have changed, including modules logic) |
My bad, sorry for not noticing earlier. Thanks for pointing it out |
I would add a module that let run gOSINT as a web service exposing REST API
The text was updated successfully, but these errors were encountered: