home.social

#portknocking — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #portknocking, aggregated by home.social.

  1. @ireneista @darkuncle @tg

    Just curious, does anyone still use #PortKnocking, or has stuff like Tailscale relegated that to the bitbucket of #infosec praxis?

  2. When #PortKnocking was first introduced, somebody made a fork of #PuTTY which had it built in. We didn't take the patch upstream, because it seemed so likely that port knocks would keep evolving and we'd have to run to keep up; we thought a better design would be to delegate to a "make my connection, with any necessary knocks" sub-tool.

    But the best thing about this fork was its name. The author called it PoTTY. And it came with a full suite of supporting tools with names like Pogeant and Plonk. Top marks!

  3. When #PortKnocking was first introduced, somebody made a fork of #PuTTY which had it built in. We didn't take the patch upstream, because it seemed so likely that port knocks would keep evolving and we'd have to run to keep up; we thought a better design would be to delegate to a "make my connection, with any necessary knocks" sub-tool.

    But the best thing about this fork was its name. The author called it PoTTY. And it came with a full suite of supporting tools with names like Pogeant and Plonk. Top marks!

  4. When was first introduced, somebody made a fork of which had it built in. We didn't take the patch upstream, because it seemed so likely that port knocks would keep evolving and we'd have to run to keep up; we thought a better design would be to delegate to a "make my connection, with any necessary knocks" sub-tool.

    But the best thing about this fork was its name. The author called it PoTTY. And it came with a full suite of supporting tools with names like Pogeant and Plonk. Top marks!

  5. When #PortKnocking was first introduced, somebody made a fork of #PuTTY which had it built in. We didn't take the patch upstream, because it seemed so likely that port knocks would keep evolving and we'd have to run to keep up; we thought a better design would be to delegate to a "make my connection, with any necessary knocks" sub-tool.

    But the best thing about this fork was its name. The author called it PoTTY. And it came with a full suite of supporting tools with names like Pogeant and Plonk. Top marks!

  6. This is an interesting piece about port-knocking backdoors in Juniper routers. Ineligible for the bingo, but interesting nonetheless.

    heise.de/-10258876

    Portknocking is not a new concept - I encountered it in the early 2000s and wrote my very first article in c't about it, while spending some evenings in the CCC Hannover's meeting room which I remember as a very "old school hacker den", in the literal sense (it was in a school's attic).
    #backdoor #juniper #apt #portknocking

  7. #heise erklärt (natürlich hinter der Paywall) wie man #Portknocking einrichtet. Habe noch nie davon gehört, ist das so sinnlos wie das klingt? Hat starke "How to send Hackers to SSH-jail" vibes.

    heise.de/ratgeber/Raspi-Projek