<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Collaboration / CTF :: goshs Documentation</title>
    <link>https://goshs.de/en/usage/collaboration/index.html</link>
    <description>goshs includes a set of server capabilities tailored for penetration testing, red team operations, and CTF challenges. These features let you receive and inspect traffic from targets — DNS queries, emails, SMB authentication attempts, and HTTP redirects — all from within the same binary.&#xA;SMB Server — capture NTLM hashes and optionally crack them against a wordlist DNS Server — log all incoming DNS lookups and reply with a configurable IP SMTP Server — receive emails and attachments sent to your server Redirect Endpoint — serve HTTP 3xx redirects with custom headers Domain setup To receive real-world DNS callbacks and emails you need a registered domain with a few DNS records in place. The setup below uses Namecheap as an example, but the record types are the same with any registrar.</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Mon, 13 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://goshs.de/en/usage/collaboration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SMB Server</title>
      <link>https://goshs.de/en/usage/collaboration/smb/index.html</link>
      <pubDate>Mon, 13 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://goshs.de/en/usage/collaboration/smb/index.html</guid>
      <description>How to use goshs as an SMB server goshs can act as an SMB2 server. Any client that authenticates against it will trigger an NTLM authentication exchange, and goshs will capture and log the resulting NTLMv1/v2 hash. This is useful in penetration testing and CTF scenarios where you want to coerce a target into sending SMB credentials.&#xA;Starting the SMB server goshs -smbThis starts an SMB listener on port 445 (default) using the share name goshs and domain GOSHS.</description>
    </item>
    <item>
      <title>DNS Server</title>
      <link>https://goshs.de/en/usage/collaboration/dns/index.html</link>
      <pubDate>Mon, 13 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://goshs.de/en/usage/collaboration/dns/index.html</guid>
      <description>How to use goshs as a DNS server goshs includes a lightweight DNS server that logs every incoming DNS query. This is useful in penetration testing and CTF scenarios where you want to detect out-of-band DNS interactions — for example when testing for SSRF, XXE, blind injection, or similar vulnerabilities.&#xA;Tip To receive DNS callbacks from the internet you need a registered domain with an NS delegation record pointing to your server. See Domain setup for the full configuration.</description>
    </item>
    <item>
      <title>SMTP Server</title>
      <link>https://goshs.de/en/usage/collaboration/smtp/index.html</link>
      <pubDate>Mon, 13 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://goshs.de/en/usage/collaboration/smtp/index.html</guid>
      <description>How to use goshs as an SMTP server goshs includes a lightweight SMTP server that receives and logs incoming emails including attachments. This is useful in penetration testing and CTF scenarios where you want to capture emails triggered by password resets, alert mechanisms, or other server-side email functionality.&#xA;Tip To receive emails from the internet you need a registered domain with an A record pointing to your server. See Domain setup for the full configuration.</description>
    </item>
    <item>
      <title>Redirect Endpoint</title>
      <link>https://goshs.de/en/usage/collaboration/redirect/index.html</link>
      <pubDate>Mon, 13 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://goshs.de/en/usage/collaboration/redirect/index.html</guid>
      <description>How to use the redirect endpoint goshs can serve HTTP 3xx redirects via a special URL query parameter. This is useful in penetration testing and CTF scenarios where you want to redirect a victim’s browser or server-side request to an arbitrary target — for example when testing open-redirect vulnerabilities or chaining SSRF attacks.&#xA;Triggering a redirect Append ?redirect to any goshs URL and provide the target via ?url=:&#xA;http://&lt;your-ip&gt;:8000/?redirect&amp;url=https://example.comgoshs will respond with an HTTP 302 redirect to https://example.com.</description>
    </item>
  </channel>
</rss>