Use a different method for getting engine versions #231
Conversation
The previous method of parsing the output of the "version engines" console command doesn't always work. The console command sometimes doesn't return data. This AJAX post method is what the web UI uses to get the engine data. It returns an array of engine data hash objects.
| versions << engdata | ||
| end | ||
| versions | ||
| JSON.parse(AJAX.post(self, "/data/engines"))['records'] |
There was a problem hiding this comment.
Prefer single-quoted strings when you don't need string interpolation or special symbols.
Hmm this seems like a bug to me. Will need to investigate it. cc @btrujillo-r7 |
|
@Red5d if/when you get a chance, can you let us know what kinda setup isn't returning data? Nexpose version, engine version, and the OS for each? we're under the impression that a console command should "always" return data. |
|
@sgreen-r7 Currently on Nexpose 6.2.10. Sometimes when the console is running slowly (while integrating a scan or something), the console command doesn't work. It may be a bug in Nexpose, but using this method through the AJAX api structures the data better and seems to always work from what I've seen. |
The previous method of parsing the output of the "version engines" console command doesn't always work. The console command sometimes doesn't return data. This AJAX post method is what the web UI uses to get the engine data. It returns an array of engine data hash objects.