From bede53ee5ac3d7ecfe4bfe80bd6bee5947d4ea16 Mon Sep 17 00:00:00 2001 From: James Lee Date: Thu, 23 Feb 2017 17:55:14 -0600 Subject: [PATCH] whitespace --- Meterpreter.md | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/Meterpreter.md b/Meterpreter.md index 532830e215..d2fabc05ff 100644 --- a/Meterpreter.md +++ b/Meterpreter.md @@ -32,13 +32,9 @@ Got dead Meterpreter sessions? Read this: [[Debugging Dead Meterpreter Sessions] To avoid confusion, the victim running meterpreter is always called the server and the ruby side controlling it is always called the client, regardless of the direction of the network transport connection. The Meterpreter server is broken into several pieces: - - `metsrv.dll` and `meterpreter.{jar,php,py}` - this is the heart of - meterpreter where the protocol and extension systems are - implemented. - - `ext_server_stdapi.{dll,jar,php,py}` - this extension implements - most of the commands familiar to users. - - `ext_server_*.{dll,jar,php,py}` - other extensions provide further - functionality and can be specific to particular environments. + - `metsrv.dll` and `meterpreter.{jar,php,py}` - this is the heart of meterpreter where the protocol and extension systems are implemented. + - `ext_server_stdapi.{dll,jar,php,py}` - this extension implements most of the commands familiar to users. + - `ext_server_*.{dll,jar,php,py}` - other extensions provide further functionality and can be specific to particular environments. ## Delivering Meterpreter