Upstream software project

fwknop

A Single Packet Authorization (SPA) implementation

About fwknop

A Single Packet Authorization (SPA) implementation

This project links 4 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Fedora 43: 2 package records; Fedora 44: 2 package records. Catalog coverage diagram, not an application screenshot.fwknop: recorded package coverageFedora 432 recordsFedora 442 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
fwknop
Publisher
Not authoritatively mapped
Native package records
4
Operating systems
fedora-43, fedora-44
License expression
GPL-2.0-only
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

fwknop implements an authorization scheme known as Single Packet Authorization (SPA) that requires only a single encrypted packet to communicate various pieces of information including desired access through an iptables policy and/or specific commands to execute on the target system. The main application of this program is to protect services such as SSH with an additional layer of security in order to make the exploitation of vulnerabilities (both 0-day and unpatched code) much more difficult. The authorization server passively monitors authorization packets via libpcap and hence there is no "server" to which to connect in the traditional sense. Any service protected by fwknop is inaccessible (by using iptables to intercept packets within the kernel) before authenticating; anyone scanning for the service will not be able to detect that it is even listening. This authorization scheme offers many advantages over port knocking, include being non-replayable, much more data can be communicated, and the scheme cannot be broken by simply connecting to extraneous ports on the server in an effort to break knock sequences. The authorization packets can easily be spoofed as well, and this makes it possible to make it appear as though, say, www.yahoo.com is trying to authenticate to a target system but in reality the actual connection will come from a seemingly unrelated IP. Although the default data collection method is to use libpcap to sniff packets off the wire, fwknop can also read packets out of a file that is written by the iptables ulogd pcap writer or by a separate sniffer process.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package fwknop

    43 (Fedora 43) (Unspecified): A Single Packet Authorization (SPA) implementation

    2.6.11-5.fc43: aarch64 i686 x86_64

    Source: fwknop

  2. Package fwknop-devel

    43 (Fedora 43) (Unspecified): The fwknop library, header and API docs

    2.6.11-5.fc43: aarch64 i686 x86_64

    Source: fwknop

Fedora 44

  1. Package fwknop

    44 (Fedora 44) (Unspecified): A Single Packet Authorization (SPA) implementation

    2.6.11-6.fc44: aarch64 i686 x86_64

    Source: fwknop

  2. Package fwknop-devel

    44 (Fedora 44) (Unspecified): The fwknop library, header and API docs

    2.6.11-6.fc44: aarch64 i686 x86_64

    Source: fwknop

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.