Your message dated Tue, 15 Oct 2024 11:32:27 +0000
with message-id <[email protected]>
and subject line Bug#1010718: fixed in portsentry 1.2-15
has caused the Debian Bug report #1010718,
regarding After installed portsentry doesn't create automatically
portsentry.history
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 [email protected]
immediately.)
--
1010718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010718
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: portsentry
Version: 1.2-14
Hi team,
I´m Michel Gabriel Ramirez Fournier, Cybersecurity engineer and Debian user
since many moons ago. I´m a passionate Linux predicator which loves to
recommend the good things of Debian as a server in search of security and
stability for PYMES. For that reason a few days ago i was showing to a
company the benefits of the integration of the application PORTSENTRY with
FAIL2BAN to block attackers efforts to scan the server target ports and at
same time blocking possible (future) brute force attacks coming from the
same aggressor or source.
The configuration is indeed very easy, but i detected a malfunction in
PORTSENTRY behavior when is installed, and this is caused because it
doesn´t create automatically (after being installed) the registry file
which stores the list of aggressor IPs detected:
*/var/lib/portsentry/portsentry.history*
This file is just created when a security event (like a port scan) trigger
the file creation by the active PORTSENTRY process. The absent file doesn´t
interfere the normal functioning of PORTSENTRY but if FAIL2BAN is enabled
with the jail to integrate with PORTSENTRY this scenario of missing file
will cause a FAIL2BAN crash:
*[portsentry]*
*logpath = /var/lib/portsentry/portsentry.history*
As part of an exercise i successfully started to use this flaw of
PORTSENTRY as part of an attack in a capture the flag simulation, and with
just erasing the file /var/lib/portsentry/portsentry.history and waiting a
few seconds for the demon reload the result is the subsequent crash of
FAIL2BAN.
I also recently send an email to the PORTSENTRY maintainer
[email protected] (but
still without answer) informing about the flaw detected because maybe this
malfunction of PORTSENTRY can be fixed just by creating the missing file
/var/lib/portsentry/portsentry.history after the installation and checking
if the file is present in the root folder after every daemon reload. By
doing this steps the dependence with FAIL2BAN won’t cause the FAIL2BAN
crash.
*I am using Linux debian 5.10.0-14-amd64.*
I appreciate all the help received from *[email protected]
<[email protected]>* to report this bug.
Respectfully
Michel
--- End Message ---
--- Begin Message ---
Source: portsentry
Source-Version: 1.2-15
Done: наб <[email protected]>
We believe that the bug you reported is fixed in the latest version of
portsentry, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
наб <[email protected]> (supplier of updated portsentry 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Fri, 04 Oct 2024 01:05:13 +0200
Source: portsentry
Architecture: source
Version: 1.2-15
Distribution: unstable
Urgency: medium
Maintainer: Dario Minnucci <[email protected]>
Changed-By: наб <[email protected]>
Closes: 894974 1010718 1028013 1039322 1081771
Changes:
portsentry (1.2-15) unstable; urgency=medium
.
* Team upload by debian/ team
Closes: #1081771
.
[ Jelmer Vernooij ]
* Migrate repository from alioth to salsa.
.
[ Andreas Tille ]
* debian/README.source: Replace redundant hint to quilt by hint how
to possibly get latest commits from Github as new upstream source
* debian/watch: Add comment to fetch latest upstream commit
* Standards-Version: 4.7.0 (routine-update)
* debhelper-compat 13 (routine-update)
* Reorder sequence of d/control fields by cme (routine-update)
* Secure URI in copyright format (routine-update)
* Remove trailing whitespace in debian/changelog (routine-update)
* Remove trailing whitespace in debian/control (routine-update)
* Remove trailing whitespace in debian/copyright (routine-update)
* Remove trailing whitespace in debian/rules (routine-update)
* Rules-Requires-Root: binary-targets
* Trim trailing whitespace.
* Create automatically portsentry.history
Closes: #1010718
* d/rules: drop useless boilerplate comment
* d/rules: short dh
* d/rules: Enable hardening options
.
[ Helmut Grohne ]
* Fix FTCBFS: (Closes: #894974)
+ Let dh_auto_build pass cross tools to make.
+ Defer all stripping to dh_strip.
.
[ Paulo Henrique de Lima Santana ]
* Updated d/po/pt_BR.po (Closes: #1028013)
.
[ наб ]
* d/rules: no need for `pwd` or `dh_listpackages`
* d/post{inst,rm}: stop supporting upgrades from 1.0-2 (unneeded since woody)
* Add systemd service (Closes: #1039322)
+ the sysvinit unit starts 0/1/2 programs ad lib
+ this is unrepresentable in systemd
+ instead, mask it, ship template, and enable the appropriate
[email protected] and [email protected]
* Make portsentry-build-ignore-file idempotent
* debian/{po/{de,fr,nb}.po,portsentry.conf.5}: lintian national-encoding
* d/prerm: lintian command-with-path-in-maintainer-script
* d/control: lintian skip-systemd-native-flag-missing-pre-depends
* d/NEWS: mention the new systemd setup
Checksums-Sha1:
164370cfc36ca41928a30d3bb52e4fa60398ace3 1859 portsentry_1.2-15.dsc
1ab59c2ce4acb3e8242d528e4a90091157811ec6 36768 portsentry_1.2-15.debian.tar.xz
a71889ae32ccfa8ad44b35b1eff3abb7e559b884 6167 portsentry_1.2-15_amd64.buildinfo
Checksums-Sha256:
d65ea8f03ec7dea32f9b4286027099e7741819deba3b6ff258582220e6e447cc 1859
portsentry_1.2-15.dsc
a8d8e99f4010fa1b2bb13e4aca509af8db1fdb0b2cf940656856a26467f2ded9 36768
portsentry_1.2-15.debian.tar.xz
eff9c089ea1db9229502c74f9ca6c885968e44c3dca27f1875cb851c3334a8e9 6167
portsentry_1.2-15_amd64.buildinfo
Files:
906fe8bd9b57eb644930aa3c9e680bea 1859 net optional portsentry_1.2-15.dsc
df6abbdaea32f849ff67110ec5d329ef 36768 net optional
portsentry_1.2-15.debian.tar.xz
be6e2cb6278c1723792f24fa3bdf3944 6167 net optional
portsentry_1.2-15_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmcBEYcRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHkXw/8DzHy3azg85iqTDUhdLaKgUMPt8/GUZrk
uOf3yDw4WkHT8wQ9UIqxfMBCXGojceAkBLFCEsEFHN0pGu7oHa2MiaM8LT9galvI
iS4kTaMQNpo7QWzvn7Ycsp7+1yadeg9IlgdaO9Axm2rbK0JTsYVMrEwTuSvum0Uf
OiQyhOiTR9ErLSqc97KMHhJwUF5zYwgrVMo2yal+SDrlH7o5hlR8bAFicTq1dooE
iFhn0wYVc50+0nyc1K4icVaSoGfxn1+s7HeI7W6PrxI35RiTdhepcciSbT0aD90m
eNIaKQn5XarG6KXvHrbJpE5oN/SDZYR61UCwRG6ek12XjCdeeLdNdUXse1i+CG93
Bgg6YfnwTRdRHBFFHwiaeRdS69CBZU5ZmEyky0ipWIKPeUgMdHRyilNNkui9KuWN
zl3WmeOmZnjnxd99h0vVkerB0kMm4uYtLXjdjbzbe0Z2fjDwY9v/+S4QpfwLV7Ti
6nUP/70Uj5XUmaTiSTTunm0/AW2JTtHmcaGpQf2mVj8wAdXdb4yoaqanSV8gAhaS
3RmHX4kkQf3T+4ZdwtWssEtNa6hv/tFEqyT0M5JqfOMrecgY6zVvvMN3Mk4OzbVh
T5jqPH163D+oX/1255VpQFdgwbnNKP2WuxMwgKqENh2YZK5PepVHMkajaWg8kq7T
ZbreJ/MYSyw=
=qTRf
-----END PGP SIGNATURE-----
pgpV7eiexB9NL.pgp
Description: PGP signature
--- End Message ---
