From bc6a3b1bc87100ed17ed6623dbe4100812ff5472 Mon Sep 17 00:00:00 2001 From: fluffy-kaiju Date: Tue, 19 Nov 2024 09:32:20 +0100 Subject: [PATCH] docs(smbexec): update doc dead link * Update the blog link to web.archive.org --- ChangeLog.md | 2 +- examples/smbexec.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/ChangeLog.md b/ChangeLog.md index af17afe3f..a927527dc 100644 --- a/ChangeLog.md +++ b/ChangeLog.md @@ -722,7 +722,7 @@ As always, thanks a lot to all these contributors that make this library better UUIDs used and that information is included as well. This could be helpful when reading a portmap output and to develop new functionality to interact against a target interface. * `smbexec.py`: Another alternative to psexec. Less capabilities but might work on tight AV environments. Based on the - technique described at https://www.optiv.com/blog/owning-computers-without-shell-access. It also + technique described at https://web.archive.org/web/20190515131124/https://www.optiv.com/blog/owning-computers-without-shell-access. It also supports instantiating a local smbserver to receive the output of the commandos executed for those situations where no share is available on the other end. * `smbrelayx.py`: It now also listens on port 80 and forwards/reflects the credentials accordingly. diff --git a/examples/smbexec.py b/examples/smbexec.py index 3f1627ba7..4985e9486 100755 --- a/examples/smbexec.py +++ b/examples/smbexec.py @@ -11,7 +11,7 @@ # # Description: # A similar approach to psexec w/o using RemComSvc. The technique is described here -# https://www.optiv.com/blog/owning-computers-without-shell-access +# https://web.archive.org/web/20190515131124/https://www.optiv.com/blog/owning-computers-without-shell-access # Our implementation goes one step further, instantiating a local smbserver to receive the # output of the commands. This is useful in the situation where the target machine does NOT # have a writeable share available.