dissect.target.plugins.apps.shell.powershell#

Module Contents#

Classes#

PowerShellHistoryPlugin

Base class for plugins.

Attributes#

ConsoleHostHistoryRecord

dissect.target.plugins.apps.shell.powershell.ConsoleHostHistoryRecord#
class dissect.target.plugins.apps.shell.powershell.PowerShellHistoryPlugin(target)#

Bases: dissect.target.plugin.Plugin

Base class for plugins.

Plugins can optionally be namespaced by specifying the __namespace__ class attribute. Namespacing results in your plugin needing to be prefixed with this namespace when being called. For example, if your plugin has specified test as namespace and a function called example, you must call your plugin with test.example:

A Plugin class has the following private class attributes:

  • __namespace__

  • __record_descriptors__

With the following three being assigned in register():

  • __plugin__

  • __functions__

  • __exports__

Additionally, the methods and attributes of Plugin receive more private attributes by using decorators.

The export() decorator adds the following private attributes

  • __exported__

  • __output__: Set with the export() decorator.

  • __record__: Set with the export() decorator.

The internal() decorator and InternalPlugin set the __internal__ attribute. Finally. args() decorator sets the __args__ attribute.

Parameters:

target – The Target object to load the plugin for.

PATHS = ['AppData/Roaming/Microsoft/Windows/PowerShell/psreadline', '.local/share/powershell/PSReadLine']#
check_compatible() → None#

Perform a compatibility check with the target.

This function should return None if the plugin is compatible with the current target (self.target). For example, check if a certain file exists. Otherwise it should raise an UnsupportedPluginError.

Raises:

UnsupportedPluginError – If the plugin could not be loaded.

powershell_history()#

Return PowerShell command history for all users.

The PowerShell ConsoleHost_history.txt file contains information about the commands executed with PowerShell in a terminal. No data is recorded from terminal-less PowerShell sessions. Commands are saved to disk after the process has completed. PSReadLine does not save commands containing ‘password’, ‘asplaintext’, ‘token’, ‘apikey’ or ‘secret’.

References