3 ms·
I've been using knockd[1] for the last 5 or so years. Also has prebuilt binaries (and in many repositories[2]) for almost every distro, including cygwin, native
by yareally 13y ago
I've been using knockd[1] for the last 5 or so years. Also has prebuilt binaries (and in many repositories[2]) for almost every distro, including cygwin, native windows and android.
[1] http://www.zeroflux.org/projects/knock/ http://www.zeroflux.org/projects/knock/
[2] http://packages.debian.org/wheezy/knockd http://packages.debian.org/wheezy/knockd
- narcissus 13y agoNot knowing much about this stuff, are there any clients that will 'automate' the knock for you? If so, can you make any suggestions? Or is this a matter of CLI SSH will do it, but I'm just not finding it?
- yareally 13y agohttps://help.ubuntu.com/community/PortKnocking https://help.ubuntu.com/community/PortKnocking (also the same config basically when using Debian) It's a client/server thing, so you have to have the server running on the PC you intend to connect to (like when using ssh). Never used it in any other way than with the CLI and not with every server I admin or use as there's other best practices also mentioned in the thread that are typically good enough without throwing in port knocking like: https://news.ycombinator.com/item?id=6384313 https://news.ycombinator.com/item?id=6384313 (and the child reply) https://news.ycombinator.com/item?id=6384418 https://news.ycombinator.com/item?id=6384418 https://news.ycombinator.com/item?id=6384457 https://news.ycombinator.com/item?id=6384457 Most things you can just use knocking and connect with ssh forwarding/proxy and tunnel everything through it like DB clients, IDE connections instead of having a bunch of ports open to internet. Assuming you don't kill the connection, then you can keep reusing it as a tunnel for anything else until rebooting or losing internet connection.