From: toluschr <toluschr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] opendkim,libmilter: Crash on signing email (musl), solution included
Date: Tue, 08 Dec 2020 13:04:10 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27031@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
New issue by toluschr on void-packages repository
https://github.com/void-linux/void-packages/issues/27031
Description:
### System
* xuname:
* Void 5.9.12_2 x86_64-musl GenuineIntel/KVM uptodate rFF
* package:
* libmilter>=0 opendkim>=0
### Expected behavior
Emails get signed
### Actual behavior
opendkim segfaults due to a stack overflow in [`opendkim.c:4931:dkimf_add_signrequest`](https://github.com/trusteddomainproject/OpenDKIM/blob/master/opendkim/opendkim.c#L4927).
### Steps to reproduce the behavior
Setup an email server using opendkim to sign emails and notice that emails are not signed.
### Solution
Since this being a rare issue and the first time I setup an Email server, it didn't occur to me that there might be something wrong with the stacksize of musl. After Googling 'alpine opendkim crash', I found the relevant patch.
https://git.alpinelinux.org/aports/commit/?id=95724d1bd53ae87f72e6388cb7323dbd8f84be9d
I already pushed my changes to https://github.com/toluschr/void-packages/tree/update-opendkim. This branch includes the newest commit from the opendkim development branch.
I suggest updating to the opendkim pre-releases. Although void-linux tries to ship stable software, a version from 2015 is a little dated.
next reply other threads:[~2020-12-08 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 12:04 toluschr [this message]
2020-12-14 13:50 ` ericonr
2021-01-22 1:15 ` ericonr
2021-01-22 1:15 ` [ISSUE] [CLOSED] " ericonr
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-27031@inbox.vuxu.org \
--to=toluschr@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).