Closed mort666 closed 8 years ago
Hi there, I can reproduce the bug.
Running dawn the same parameter you used but specifying the target path, I have this execution.
$ ruby -I lib bin/dawn --html -F ../report.html ~/src/hacking/dawn-test/blogcast
I, [2016-02-03 08:00:10#35367] INFO -- : dawn v1.5.2 is starting up
I, [2016-02-03 08:00:12#35367] INFO -- : /Users/thesp0nge/dawnscanner/results/blogcast/20160203/report.html created (30812 bytes)
I, [2016-02-03 08:00:12#35367] INFO -- : /Users/thesp0nge/dawnscanner/db/dawnscanner.db updated with scan infos
I, [2016-02-03 08:00:12#35367] INFO -- : dawn is shutting down
Using '.' as target argument will raise the error.
Everything should work as expected and your CI env will be back to work with next release
It seems the new reporting code for v1.5.2 is broken and unable to output HTML reports in this version.
When running a scan with the HTML report output the following is generated
It seems that dawn is attempting to open within Rails.root directory the file 'support/bootstrap.js'.
This file doesn't exist in the source tree of the rails app, additionally I do want the support files within the source for the application, which seems to be the only way to make it work. It also occurs when scanning gems and the like.
These static assets for bootstrap it would be better to have these pulled in from a CDN such as pulling them from BootstrapCDN. It would negate the need to have random old copies of bootstrap laying around the source tree.
Secondly, it appears after inspecting the code dawn does not honour the output filename either for the output of the HTML report either. This breaks the use of dawn within our CI system (Circle CI and Travis) too as we need to be able to specify the location of the output and dawn in it's current form is attempting to drop the output within the users home directory, this will not work within the CI system.