From: omar-polo <omar-polo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] opensmtpd-filter-rspamd: update to 0.1.8
Date: Wed, 04 Oct 2023 12:27:54 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46426@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
There is a new pull request by omar-polo against master on the void-packages repository
https://github.com/omar-polo/void-packages opensmtdp-filter-rspamd-0.1.8
https://github.com/void-linux/void-packages/pull/46426
opensmtpd-filter-rspamd: update to 0.1.8
- I tested the changes in this PR: **NO**
- I built this PR locally for my native architecture, (amd64-musl)
This brings in a rather important IMHO security fix: it's possible to crash filter-rspamd by attempting to log in as a user with a "|" character in it. Doing so will also quit opensmtpd since it dies once a filter exits.
Furthermore, this update will also be needed for the next opensmtpd version since it'll bump the protocol version.
I haven't actually run this on void linux, but I'm using it on other systems and the [diff is quite small](https://github.com/poolpOrg/filter-rspamd/compare/v0.1.7...v0.1.8), I don't expect actual breakages.
A patch file from https://github.com/void-linux/void-packages/pull/46426.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-opensmtdp-filter-rspamd-0.1.8-46426.patch --]
[-- Type: text/x-diff, Size: 1236 bytes --]
From 72ed2305883d091b6e9b530686a215b204df6d5e Mon Sep 17 00:00:00 2001
From: Omar Polo <op@omarpolo.com>
Date: Wed, 4 Oct 2023 11:31:35 +0200
Subject: [PATCH] opensmtpd-filter-rspamd: update to 0.1.8
---
srcpkgs/opensmtpd-filter-rspamd/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/opensmtpd-filter-rspamd/template b/srcpkgs/opensmtpd-filter-rspamd/template
index 16d5fe58650d5..df700085bed4f 100644
--- a/srcpkgs/opensmtpd-filter-rspamd/template
+++ b/srcpkgs/opensmtpd-filter-rspamd/template
@@ -1,7 +1,7 @@
# Template file for 'opensmtpd-filter-rspamd'
pkgname=opensmtpd-filter-rspamd
-version=0.1.7
-revision=3
+version=0.1.8
+revision=1
build_style=go
go_import_path="github.com/poolpOrg/filter-rspamd"
short_desc="Filter incoming mail based on sender reputation"
@@ -9,7 +9,7 @@ maintainer="Lucas L. Treffenstädt <lucas@treffenstaedt.de>"
license="ISC"
homepage="https://github.com/poolpOrg/filter-rspamd"
distfiles="https://github.com/poolpOrg/filter-rspamd/archive/v${version}.tar.gz"
-checksum=734733c3b672b660bcfe8f0008b09c84469f051f7381230d332265981af6f287
+checksum=42b3e8d35feac813e695245b55c552126728de1a3219fb4dc64c62935f831f29
do_install() {
vlicense LICENSE
next reply other threads:[~2023-10-04 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 10:27 omar-polo [this message]
2023-10-04 20:28 ` mithodin
2023-10-25 7:45 ` omar-polo
2023-10-25 8:10 ` mithodin
2023-11-07 16:44 ` [PR PATCH] [Merged]: " leahneukirchen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46426@inbox.vuxu.org \
--to=omar-polo@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).