Arachni RPC call "service.output" returns nothing?
Dear Tasos:
We had some very old code that uses RPC call "service.output" to print live arachni output to the customer, but I examined it recently and found out that arachni always give out empty result. I have never seen the output from this call before(I assume that it was able to return something non-trivial, but the previous developer might be using very old arachni for testing), I need to confirm with you: is this call deprecated? If so, which calls can I use to retrieve live progress from arachni? Thanks.
PS: I also know the one "framework.progress_data", but arachni dumps out huge progress data, which is hard to represent to the webpage.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Tasos Laskos on 03 Apr, 2013 03:43 PM
service.outputis the same asframework.output[1] whose docs say that these messages are there to give some sense of process moving forwards but will be wildly inaccurate and out of sync with what's actually happening.There's just no good way to store and transmit those messages as they will easily go into the GBs and offer very little value.
You can have those messages rerouted to a logfile for debugging purposes but allowing transmission over RPC was a stupid idea and I do apologize for luring you down that rabbit hole.
Which is why, as of v0.4.2 (which will go out once Rails 4.0 stable and some other deps are released), those output methods will be deprecated.
I'll also introduce a much, much simpler API which will hopefully make your life easier and which will be documented up to its ears.
For now, prepare to get away from depending on the output because you can't.
[1] http://rubydoc.info/github/Arachni/arachni/Arachni/RPC/Server/Frame...
Tasos Laskos closed this discussion on 03 Apr, 2013 03:43 PM.