Skip to content
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

Report generation #14

Open
bdamele opened this issue Jun 26, 2012 · 6 comments
Open

Report generation #14

bdamele opened this issue Jun 26, 2012 · 6 comments

Comments

@bdamele
Copy link
Member

bdamele commented Jun 26, 2012

Add support to generate a report, at least in XML/XSLT format.

@t1gor
Copy link

t1gor commented Sep 17, 2014

Any updates on report functionality?

@stamparm
Copy link
Member

@t1gor short answer: no. It's kind of complicated to convert current free-text format to anything "formatted". Sorry, but can't promise anything

@t1gor
Copy link

t1gor commented Sep 18, 2014

@stamparm, I get it, no problem. Thanks for the update

@tylercamp
Copy link

We're looking to ingest results from sqlmap into Code Dx, but lack of a common report format is the current major blocker for us. We did find a blog post for importing results into DefectDojo with some small source tweaks: https://xavi.blog/integrating-sqlmap-in-ci-cd-with-owasp-defectdojo

Would the linked approach of fetching data from kb.injections be sufficient for a results report? I'm not familiar enough with python or this codebase to assess whether this could potentially skip some injections or if it would lead to missing out on some important/directly-related data.

As in the link above, we're primarily concerned with discovered SQL injections. Metadata such as detected DB type isn't important for our case.

I've commented on this issue since it seems directly related. An injections-only export might also satisfy this issue, since our use-case may be common for others that want a well-formed report.

@stamparm
Copy link
Member

stamparm commented May 5, 2020

@tylercamp looking into "Code Dx" I can see that you have a nice business case. So basically, you are nagging that your business - where FOSS sqlmap is obviously used - is suffering because of lazy developers? Please, forgive me, but this is kind of sad

@stamparm
Copy link
Member

stamparm commented May 5, 2020

@tylercamp If you can imagine the scale of priority from 0 to 10, this has fell to -9000 on my list. This basically means that you can tell your executive manager that lazy open-source developer is kind of pissed off of you even commenting on this issue

@sqlmapproject sqlmapproject locked as off-topic and limited conversation to collaborators May 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants