commands_that_can_be_executed_in_file_based_malware_simulations
Differences
This shows you the differences between two versions of the page.
Last revisionBoth sides next revision | |||
commands_that_can_be_executed_in_file_based_malware_simulations [2016/06/28 08:26] – created lucy | commands_that_can_be_executed_in_file_based_malware_simulations [2019/05/22 17:45] – lucy | ||
---|---|---|---|
Line 3: | Line 3: | ||
LUCY comes with three tools that will access the windows command shell and enable you to execute commands: | LUCY comes with three tools that will access the windows command shell and enable you to execute commands: | ||
- | * **ConsolePost**: | + | * **ConsolePost**: |
* **ConsoleOutlook**: | * **ConsoleOutlook**: | ||
Line 24: | Line 24: | ||
- | In the commercial edition there are no limitations. Commercial editions allow any command to be executed using this syntax: | + | In the commercial edition, there are no limitations. Commercial editions allow any command to be executed using this syntax: |
- | cmd.exe /c "YOUR COMMAND GOES HERE" (some commands in Windows are not executable. They are built into the command line. Example of command with executable: whoami. If you need to use a command which is a built in command line, then you should call cmd directly. Example | + | cmd.exe /c "YOUR COMMAND GOES HERE" (some commands in Windows are not executable. They are built into the command line. Example of command with executable: whoami. If you need to use a command which is a built-in command line, then you should call cmd directly. Example |
So, for example, standard cmd.exe commands are accessible like: | So, for example, standard cmd.exe commands are accessible like: |
commands_that_can_be_executed_in_file_based_malware_simulations.txt · Last modified: 2019/07/25 12:49 by 127.0.0.1