Expose options for logging to a file in mettle #16529
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow on from #16445 to leverage the same datastore options to enable/disable logging on mettle and optionally save those logs to a file
Removes the old datastore options, which were only available to be set for staged linux payloads, to be consistent with the recent additions of
MeterpreterDebugBuild
andMeterpreterDebugLogging
and to support allmettle
based payloadsVerification
use payload/linux/x86/meterpreter/reverse_tcp
)advanced
and observe the two optionsMeterpreterDebugBuild
andMeterpreterDebugLogging
set MeterpreterDebugBuild true
andset MeterpreterDebugLogging rpath:./this_is_a_text_file.txt
to enable and configure the loggergenerate -f elf -o payload.elf
followed byto_handler
to generate your payload and start the appropriate handler