Bug#836890: Fix long description

[Franck Joncourt <franck.joncourt@gmail.com>]

Package: fwknop
Version: 2.6.9-1
Severity: normal

Here is a patch to fix fwknop description s/libcap/libpcap/.
Thanks Justin B Rye (l10n*-english team) for catching this.

A reminder the time I can get access to collab maint :)

Regards,

--
Franck

--- a/debian/control
+++ b/debian/control
@@ -28,7 +28,7 @@
  vulnerabilities (both 0-day and unpatched code) much more difficult.
  .
  The authorization server passively listens for authorization packets via
- libcap, so there is no service listening for network connections on the
+ libpcap, so there is no service listening for network connections on the
  traditional port. Access to a protected service is only granted after a
  valid encrypted and non-replayed packet is detected. 
  .
@@ -50,7 +50,7 @@
  vulnerabilities (both 0-day and unpatched code) much more difficult.
  .
  The authorization server passively listens for authorization packets via
- libcap, so there is no service listening for network connections on the
+ libpcap, so there is no service listening for network connections on the
  traditional port. Access to a protected service is only granted after a
  valid encrypted and non-replayed packet is detected. 
  .
@@ -69,7 +69,7 @@
  vulnerabilities (both 0-day and unpatched code) much more difficult.
  .
  The authorization server passively listens for authorization packets via
- libcap, so there is no service listening for network connections on the
+ libpcap, so there is no service listening for network connections on the
  traditional port. Access to a protected service is only granted after a
  valid encrypted and non-replayed packet is detected. 
  .
@@ -89,7 +89,7 @@
  vulnerabilities (both 0-day and unpatched code) much more difficult.
  .
  The authorization server passively listens for authorization packets via
- libcap, so there is no service listening for network connections on the
+ libpcap, so there is no service listening for network connections on the
  traditional port. Access to a protected service is only granted after a
  valid encrypted and non-replayed packet is detected. 
  .
@@ -109,7 +109,7 @@
  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
+ libpcap, 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.
 
@@ -142,7 +142,7 @@
  vulnerabilities (both 0-day and unpatched code) much more difficult.
  .
  The authorization server passively listens for authorization packets via
- libcap, so there is no service listening for network connections on the
+ libpcap, so there is no service listening for network connections on the
  traditional port. Access to a protected service is only granted after a
  valid encrypted and non-replayed packet is detected.
  .