Sync fail2ban 1.1.0-1 (universe) from Debian unstable (main)
Bug #2065796 reported by
Sylvestre Ledru
This bug affects 9 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| fail2ban (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Bug Description
Please sync fail2ban 1.1.0-1 (universe) from Debian unstable (main)
Changelog entries since current noble version 1.0.2-3:
fail2ban (1.1.0-1) unstable; urgency=medium
* New upstream release
(LP: #2055114)
* Block ssh invalid keys too (Closes: #1038779)
* Follow upstream advice
https:/
to only have sshd as enabled = true in jail.d_
* Update lintian override info format in d/source/
* Update standards version to 4.6.2, no changes needed.
-- Sylvestre Ledru <email address hidden> Thu, 02 May 2024 13:57:06 +0200
| Changed in fail2ban (Ubuntu): | |
| importance: | Undecided → Wishlist |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in fail2ban (Ubuntu): | |
| status: | New → Confirmed |
Revision history for this message
| Simon Quigley (tsimonq2) wrote | #2 |
| Changed in fail2ban (Ubuntu): | |
| status: | Confirmed → Fix Released |
| Changed in fail2ban (Ubuntu): | |
| status: | Fix Released → Confirmed |
| importance: | Wishlist → Critical |
| milestone: | none → mantic-updates |
| Changed in fail2ban (Ubuntu): | |
| milestone: | mantic-updates → ubuntu-24.05 |
| Changed in fail2ban (Ubuntu): | |
| status: | Confirmed → Fix Released |
| milestone: | ubuntu-24.05 → none |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.