fwknop 1.9.12-3 source package in Ubuntu
Changelog
fwknop (1.9.12-3) unstable; urgency=low * Added patch from Serafeim Zanikolas to add network lsb facility in init script. (Closes: #599745) * Bumped up Standards-Version to 3.9.1 (no changes). -- Ubuntu Archive Auto-Sync <email address hidden> Sun, 07 Nov 2010 11:49:30 +0000
Upload details
- Uploaded by:
- Ubuntu Archive Auto-Sync
- Uploaded to:
- Natty
- Original maintainer:
- thialme
- Architectures:
- any
- Section:
- admin
- Urgency:
- Low Urgency
See full publishing history Publishing
Series | Published | Component | Section | |
---|---|---|---|---|
Precise | release | universe | admin |
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
fwknop_1.9.12.orig.tar.gz | 264.1 KiB | a67242f25d09c4cdc3c0c449f1a71a3a52db61c79692bbf1a4e90ce9324f32b0 |
fwknop_1.9.12-3.debian.tar.gz | 16.7 KiB | e9f5acb09888e3d6e4baf39f72585195b4a41a842d70f2dca27c7e148f39def2 |
fwknop_1.9.12-3.dsc | 1.2 KiB | 752302df6440a44bcf27e8ea15f830df5f936453cf47b73ba06df92f45c9c916 |
Available diffs
- diff from 1.9.12-2 to 1.9.12-3 (761 bytes)
Binary packages built by this source
- fwknop-client: FireWall KNock OPerator client side
The FireWall KNock OPerator implements an authorization scheme called
Single Packet Authorization (SPA), based on Netfilter and libpcap.
.
Its main application is to protect services such as OpenSSH with
an additional layer of security in order to make the exploitation of
vulnerabilities (both 0-day and unpatched code) much more difficult.
.
This is the client program responsible for accepting password input
from the user, constructing SPA packets that conform to the fwknop
packet format, and encrypting packet data.
- fwknop-server: FireWall KNock OPerator server side
The FireWall KNock OPerator implements an authorization scheme called
Single Packet Authorization (SPA), based on Netfilter and libpcap.
.
Its main application is to protect services such as OpenSSH 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 listens for authorization packets via
libcap, thus preventing any connections from being processed on the
traditional port. Access to a protected service is only granted after a
valid encrypted and non-replayed packet is detected.