From b8edbec12501b6ffe6f5b418a0de635bc9eba481 Mon Sep 17 00:00:00 2001 From: Josh Hale Date: Sat, 16 Jul 2016 22:47:47 -0500 Subject: [PATCH] Minor change to module doc --- documentation/modules/post/windows/capture/keylog_recorder.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/modules/post/windows/capture/keylog_recorder.md b/documentation/modules/post/windows/capture/keylog_recorder.md index 4cbe233b74..f8e98bf98b 100644 --- a/documentation/modules/post/windows/capture/keylog_recorder.md +++ b/documentation/modules/post/windows/capture/keylog_recorder.md @@ -36,7 +36,7 @@ The Meterpreter session must be located in an appropriate process for keystroke It is recommended to run this module as a job using: `exploit -j` or `run -j`. As a job, the module runs in the background preventing it from tying up the Framework's user interface. To stop capturing keystrokes, kill the job using `jobs -k`. The module records the last few keystrokes before exit. Stopping the job can take up to 30 seconds. If the session is killed, the key log job shuts down automatically. ### TimeOutAction -This module has two actions it can take if SessionCommunicationTimeout is reached. This occurs with packet-based payloads like `reverse_http` or `reverse_https` when the target system stops responding to requests for a specific period of time. The default is 300 seconds. Communications can stop due to various events such as network problems, system shut down, system sleep, or user log off. +This module has two actions it can take if communication between the Framework and the session times out. This occurs with packet-based payloads like `reverse_http` or `reverse_https` when the target system stops responding to requests for a specific period of time. The default is 300 seconds. Communications can stop due to various events such as network problems, system shut down, system sleep, or user log off. - **WAIT** - With this option selected, the module suspends attempting to gather keystrokes after the timeout. It waits for the session to become active again, then resumes capturing keystrokes. The output log reflects that recording was suspended along with a timestamp. If the session becomes active again, the log indicates this along with a timestamp. The wait option allows keystrokes to be logged over multiple system sleep cycles. In the event that the session dies, the recording job is stopped automatically.