{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihy6dytinfyk3cnzunsdyxiha67brgplicog33m7gvn3ith55tmdu",
    "uri": "at://did:plc:q4ojgz2yeizcgk2i5gehgmtm/app.bsky.feed.post/3mn4qhiavh2u2"
  },
  "path": "/post/6072908",
  "publishedAt": "2026-05-30T19:29:54.000Z",
  "site": "https://lemmy.org",
  "tags": [
    "Cybersecurity",
    "umutcamliyurt",
    "10 comments",
    "github.com/umutcamliyurt/PortTripper"
  ],
  "textContent": "submitted by umutcamliyurt to cybersecurity\n49 points | 10 comments\n\nSource code and details: github.com/umutcamliyurt/PortTripper\n\n##### How it works\n\nOn startup PortTripper:\n\n  1. Scans the configured port range and builds a whitelist of ports already in use by real services (first run only).\n  2. Binds TCP and UDP listeners on every port in the range that is not in the whitelist.\n  3. On TCP: accepts connections, holds them open for a configurable duration, then drops them, wasting the scanner’s threads and file descriptors.\n  4. On UDP: reads and discards datagrams without replying, so ports appear `open|filtered` to scanners rather than `closed`.\n\n\n\nAll real service ports are untouched because they are already bound before PortTripper starts, and the auto-generated whitelist tells PortTripper to skip them.",
  "title": "A honeypot that binds to a large range of dummy TCP and UDP ports to frustrate network fingerprinting."
}