From b3d88de8599d0908a02fa71eacaba66369ef8067 Mon Sep 17 00:00:00 2001 From: rootTHC <57636391+rootTHC@users.noreply.github.com> Date: Fri, 24 Jan 2020 16:13:18 +0000 Subject: [PATCH] Update README.md typo. link. --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 59818ae..bd68fe8 100644 --- a/README.md +++ b/README.md @@ -24,7 +24,7 @@ Got tricks? Send them to root@thc.org or submit a pull request. 1. [uuencode](#feu-anchor) 1. [openssl](#feo-anchor) 1. [xxd](#fex-anchor) - 1. [Multiple binaries](#xeb-anchor) + 1. [Multiple binaries](#feb-anchor) 1. [File transfer using screen from REMOTE to LOCAL](#ftsrl-anchor) 1. [File transfer using screen from LOCAL to REMOTE](#ftslr-anchor) 5. [Reverse Shell / Dumb Shell](#rs-anchor) @@ -197,7 +197,7 @@ Decode: $ xxd -p -r >issue.net-COPY ``` -**4.iii. File Encoding - Multiple Binaries** +**4.iv. File Encoding - Multiple Binaries** Method 1: Using *shar* to create a self extracting shell script with binaries inside: ``` @@ -219,7 +219,7 @@ $ openssl base64 -d | tar xfz - ``` -**4.iv. File transfer - using *screen* from REMOTE to LOCAL** +**4.v. File transfer - using *screen* from REMOTE to LOCAL** Transfer a file FROM the remote system to your local system: @@ -246,7 +246,7 @@ $ rm -rf screen-xfer.txt ``` -**4.v. File transfer - using *screen* from LOCAL to REMOTE** +**4.vi. File transfer - using *screen* from LOCAL to REMOTE** On your local system (from within a different shell) encode the data: ```