Install fwknop with Homebrew

Project links

• Homepage
• Repository

Commands and aliases

• fwknop
• fwknopd

Project history

The official project page says fwknop began in 2004 as a port-knocking implementation and was the first tool to combine traditional encrypted port knocking with passive OS fingerprinting. The project later emphasized Single Packet Authorization as a stronger successor to port knocking.

The current C implementation includes libfko, client and server applications, and support for Linux iptables and firewalld, OpenBSD PF, FreeBSD and macOS ipfw, and custom scripts. The README describes the project state around the 2.5 release in July 2013, when libfko, the client, and fwknopd server formed the core distribution.

The official site continues to publish releases, with the project page listing 2.6.11 as the latest release and the blog showing a 2024 software release post.

Adoption history

fwknop became known in the security community through port-knocking and SPA discussions. The official project page notes two Slashdot appearances in 2004 and 2005, one about combining port knocking with OS fingerprinting and another about going beyond port knocking with single-packet access.

Package metadata shows fwknop in multiple Unix-like package ecosystems, and upstream documentation covers Linux, BSD, macOS, Windows under Cygwin, Android clients, and graphical clients. Its adoption is strongest among administrators who want SSH or internal services invisible to ordinary scans.

How it is used

A typical deployment generates encryption and HMAC keys, stores client settings in `~/.fwknoprc`, places shared authorization material in `/etc/fwknop/access.conf`, starts `fwknopd`, and keeps the protected service blocked by default firewall policy until a valid SPA packet arrives.

The tutorial focuses on SSH concealment, NAT gateway use, cloud environments, replay protection, HMAC authenticated encryption, and the operational tradeoff of needing both a client and a daemon.

Why package nerds care

fwknop is significant because it turns firewall access into a packageable client-server protocol with config files, manpages, libraries, distro packages, and alternate clients. It is not just a security script; it is an ecosystem around SPA packets and firewall rule orchestration.

For maintainers, fwknop is also a reminder that security packages often include sensitive config defaults, key files, init or service integration, firewall backend differences, and compatibility with old protocol modes.

Timeline

• 2004: Project begins as a port-knocking implementation.
• 2004: Project receives Slashdot attention for encrypted port knocking with OS fingerprinting.
• 2005: Single Packet Authorization direction receives further Slashdot attention.
• 2006: Single Packet Authorization with fwknop paper published in USENIX ;login: Magazine.
• 2011: GitHub repository created.
• 2013: README describes the 2.5 release with libfko, client, and server applications.
• 2016: Comprehensive tutorial updated.
• 2024: Official site announces fwknop 2.6.11.

Related projects

• fwknop is closely related to port-knocking tools but positions Single Packet Authorization as a stronger design.
• The official README names fwknop-gui and Android Fwknop2 as related clients.
• Other Cipherdyne projects listed near fwknop include psad, fwsnort, gpgdir, and IPTables parsing or chain-management modules.

Sources

• https://api.github.com/repos/mrash/fwknop
• https://github.com/mrash/fwknop
• https://raw.githubusercontent.com/mrash/fwknop/master/README.md
• https://www.cipherdyne.org/fwknop
• https://www.cipherdyne.org/fwknop/docs/SPA.html
• https://www.cipherdyne.org/fwknop/docs/fwknop-tutorial.html