[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#836890: marked as done (Fix long description)



Your message dated Thu, 05 Oct 2017 19:04:18 +0000
with message-id <E1e0BRS-0004U8-7m@fasolo.debian.org>
and subject line Bug#836890: fixed in fwknop 2.6.9-2
has caused the Debian Bug report #836890,
regarding Fix long description
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
836890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836890
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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.
  .

--- End Message ---
--- Begin Message ---
Source: fwknop
Source-Version: 2.6.9-2

We believe that the bug you reported is fixed in the latest version of
fwknop, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 836890@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adam Borowski <kilobyte@angband.pl> (supplier of updated fwknop package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 05 Oct 2017 20:36:06 +0200
Source: fwknop
Binary: libfko3-dev libfko3 libfko-doc libfko-perl fwknop-server fwknop-client libfko-python fwknop-apparmor-profile
Architecture: source
Version: 2.6.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Adam Borowski <kilobyte@angband.pl>
Description:
 fwknop-apparmor-profile - FireWall KNock OPerator - Apparmor profile
 fwknop-client - FireWall KNock OPerator client side - C version
 fwknop-server - FireWall KNock OPerator server side - C version
 libfko-doc - FireWall KNock OPerator - documentation
 libfko-perl - FireWall KNock OPerator - Perl module
 libfko-python - FireWall KNock OPerator - Python module
 libfko3    - FireWall KNock OPerator - shared library
 libfko3-dev - FireWall KNock OPerator - development library
Closes: 836890
Changes:
 fwknop (2.6.9-2) unstable; urgency=medium
 .
   * QA upload.
   * Drop upstart system job.
   * s/libcap/libpcap/ in long descriptions. Closes: #836890.
   * debhelper compat 10.
   * Don't activate triggers twice.
Checksums-Sha1:
 4f8092d65d9f61e49242cb0ae94a51586e853772 2478 fwknop_2.6.9-2.dsc
 741244dc7389ff81fc0d06de8aec69c564ad78ce 24448 fwknop_2.6.9-2.debian.tar.xz
 d947e0154b0dbc672ca1a498e953780ae639d2fd 6001 fwknop_2.6.9-2_source.buildinfo
Checksums-Sha256:
 80490af9aad5e169b0898227dde5ef2ebb8c8459e27d5364a9578a6bf1473b42 2478 fwknop_2.6.9-2.dsc
 caaf6f56c1833e5bd2c113935588facfa8355cd38cd4043dcbaadd777ffdaf18 24448 fwknop_2.6.9-2.debian.tar.xz
 d03d3525e33b3443c1d7e5d7edd472e91a145aad5f2cf689a8f6e33844bc7a87 6001 fwknop_2.6.9-2_source.buildinfo
Files:
 a7723a3850eaa9482d3329f962a7f762 2478 admin extra fwknop_2.6.9-2.dsc
 c6f43de7400b2a26a937894815e42408 24448 admin extra fwknop_2.6.9-2.debian.tar.xz
 0a4c3a52dc9aea9f7e3c1182f712cbe8 6001 admin extra fwknop_2.6.9-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlnWe6UUHGtpbG9ieXRl
QGFuZ2JhbmQucGwACgkQweDZLphvfH4tSBAAiyLrbhUXfzftSJj3i17zYbXduacr
jcW2mFkNDgwbF8Ar9sUkj8YcyWC05tJsuC6ARYVzdLjEIGn/QHiniL/qnZ31IjMG
B0LrmgKLB9kXQZ6mfxkCOE0yM9LXqXih3kh7aXOA9zsqr8cIZjHfW0ZFI0AlZCny
OIWsQm/Jp+Nnt4ywq5Bgfba4omNy+l7cDid8vkpPwx1/8c5iccF3iqGw2mNU9Jyr
0Lf/DznFhNyXYkuGZO105MKY5ZQVnx1igsFz623ixqQoopxnrSY+THrqEEKLB5eg
RF5WWmvZ6leIfJEesdPnCntJ6BeolJWPedXiDuDfqgxxNJqRyXWq/vdiibMiAaH7
AMsStN8+xJr0dAQ0a/IshMv+eQxp1/4VfvCjBsZouWBDKPINBzimuXrjESx2uvQ5
0xgLDfSForvMtFbMc4NQUNC7tTVyvB4qlStp1DrTibQEna7Ta3GR8nxvbKZLvLgI
dVmjLuiVGZ3COOyUfnv7Bh6aVrRelATxH7s+KLyZpr1QHXozoayaunK59ud1ajd1
LDTTq9Fqp8IMRKGpMPUFoQ7fY8Mlv+ya9pZnbAR0L45wOh9v7QucJ4/ujuJtWDVj
7muyPwjUliRnakwsPQ+HPa3LR5HPgma8xEmtlywNq3lc3SNVezU6UffRz2utOvwx
RDqnHEC0NHW89Hk=
=DzFd
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: