summaryrefslogtreecommitdiffstats
path: root/README.txt
diff options
context:
space:
mode:
authorMalfurious <m@lfurio.us>2023-03-30 02:46:44 -0400
committerdusoleil <howcansocksbereal@gmail.com>2023-03-31 22:23:34 -0400
commitdd243d60cf75813812ac0115b6373b108b6b0ed8 (patch)
treed588d3e342dd69464e0870ecab8337ea3f8280bb /README.txt
parentde95a406075f87704ac3a884f3750d3656058891 (diff)
downloadsploit-dd243d60cf75813812ac0115b6373b108b6b0ed8.tar.gz
sploit-dd243d60cf75813812ac0115b6373b108b6b0ed8.zip
Allow control of named pipe location via command-line
Add the ability to select which location to create FIFOs when running in pipes mode, by passing the directory name to sploit where a target executable would usually go. This has been an API feature from the start, but not exposed via the sploit runner command-line interface. There are a couple new use-cases where this is very convenient, including scriptifying sploit in pipes mode (testing, for example) and when running sploit under Docker. If pipes are placed in the working directory, all project files can be shared with a single bind mount. Signed-off-by: Malfurious <m@lfurio.us> Signed-off-by: dusoleil <howcansocksbereal@gmail.com>
Diffstat (limited to 'README.txt')
-rw-r--r--README.txt8
1 files changed, 8 insertions, 0 deletions
diff --git a/README.txt b/README.txt
index 7684815..8a0e531 100644
--- a/README.txt
+++ b/README.txt
@@ -35,6 +35,14 @@ and against any target source regardless of how it exposes its stdio.
$ sploit exploit.py
```
+The pipe FIFOs are normally located in a temporary directory. However, if a
+directory name is given, sploit will use that location instead. A particularly
+useful way to use this is to store the pipes in the current directory for working
+with Docker.
+```
+$ sploit exploit.py .
+```
+
When running in Pipes mode, sploit will wait for something to connect on the
FIFOs before actually executing the exploit script. Once it has finished, it
will go back to waiting and run the script again the next time it connects.