Enumerate expected exposed ports in device configuration file about daq HOT 8 CLOSED

Understood about the use case, but unlikely to be a common data store. What's needed is an if-then capability with parameters. Directly exposing a data-store breaks encapsulation.

from daq.

Would like to identify an exact use-case where this is desirable. The example of "should run brute or not" I think it better handled through explicit configuration, not dynamic adjustment.

I realized there are provisions for doing this already, but I wouldn't want it to be used unless it was demonstrably the right thing to do.

from daq.

The idea of conditional tests sounds good in this specific instance.
I think that the sequence of operations could be:
nmap scans ports
for each port that is open, execute brute test on that port using the relevant protocol(s)
save output log and test results to report

I think that the data store could be useful though for storing results of soak tests and let a soak test module parse them and create a "cumulative" report.
But this can also be done perhaps by adding a docker bind mount to the inst/ folder? Any problem with any of these approaches?

from daq.

from daq.

OK, thanks Trevor. So shall we say this can be closed by acknowledging the appropriate action is to add support for a device configuration file that has test configuration options?

from daq.

I updated the title to reflect the desired work -- we can keep this issue open.

Summary: I will implement the capability to explicitly specify exposed ports for a device, and that device configuration can then be used to guide which ports are probed by a given test.

from daq.

I've moved this issue to the pressing items, noting we're targeting completing the brute module soon.
The understanding is that this will be implemented as an additional per-device configuration file in the daq/misc/test_site/mac_addrs/9a02571e8f01/ folder, or similar folder.

from daq.

Fixed/enabled/demonstrated in grafnu#123

from daq.