Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > muc.lists.qmail > #3302 > unrolled thread

qmail-dkim segmentation fault

Back to article view | Back to muc.lists.qmail

Contents

  qmail-dkim segmentation fault Michael Brunnbauer <brunni@netestate.de> - 2024-12-17 11:30 +0100
    Re: qmail-dkim segmentation fault Erwin Hoffmann <feh@fehcom.de> - 2024-12-17 12:25 +0100
      Re: qmail-dkim segmentation fault Michael Brunnbauer <brunni@netestate.de> - 2024-12-17 13:10 +0100

#3302 — qmail-dkim segmentation fault

[Multipart message — attachments visible in raw view] — view raw

hi all,

first time this happened - I dunno what was special with that message. This
sytem is configured to sign for netestate.de, but not for [DOMAINREDACTED] - 
which was probably used in the From: sender. But the envelope-sender decides 
what gets signed, as I understand it.

Dec 15 23:42:21 roja qmail: 1734302541.157353 new msg 36772888
Dec 15 23:42:21 roja qmail: 1734302541.157370 info msg 36772888: bytes 1121 from <anonymous@netestate.de> qp 4215 uid 4313
Dec 15 23:42:21 roja qmail: 1734302541.157375 starting delivery 7905: msg 36772888 to remote info@DOMAINREDACTED
Dec 15 23:42:21 roja qmail: 1734302541.157378 status: local 0/10 remote 1/10
Dec 15 23:42:21 roja kernel: qmail-dkim[4217]: segfault at 0 ip 00007f53e7c9ae52 sp 00007ffd70920be8 error 4 in libc.so.6[7f53e7b64000+14c000]
Dec 15 23:42:21 roja kernel: Code: ff 31 c0 c3 44 31 c0 44 29 c0 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 89 f0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 7e 02 00 00 <62> e1 fe 28 6f 06 48 89 f8 62 b2 7e 20 26 c0 c5 fb 93 c8 85 c9 74
Dec 15 23:42:21 roja qmail: 1734302541.229515 delivery 7905: success: 81.209.177.97_TLS_transmitted_message_accepted./Remote_host_said:_250_ok_1734302541_qp_2001/
Dec 15 23:42:21 roja qmail: 1734302541.229589 status: local 0/10 remote 0/10
Dec 15 23:42:21 roja qmail: 1734302541.229608 end msg 36772888

So what happens when qmail-dkim segfaults? And how can I help to fix this bug?

Regards,

Michael Brunnbauer

-- 
++  Michael Brunnbauer
++  netEstate GmbH
++  Geisenhausener Straße 11a
++  81379 München
++  Tel +49 89 32 19 77 80
++  Fax +49 89 32 19 77 89 
++  E-Mail brunni@netestate.de
++  https://www.netestate.de/
++
++  Sitz: München, HRB Nr.142452 (Handelsregister B München)
++  USt-IdNr. DE221033342
++  Geschäftsführer: Michael Brunnbauer
++  Prokurist: Dipl. Kfm. (Univ.) Markus Hendel

[toc] | [next] | [standalone]

#3303

Hi Michael,

too bad ...


First: Which s/qmail version you are using? 

Second: Can you supply the HEADER of the message which is causing the
segfault?

Background: Oddly structured DKIM header may result in this behavior
(parsing bug); therefore, it is really very rare. This has been fixed
in s/qmail 4.3.14. See the list of defects (closed). Version 4.2 are
subject of the bug.

Workaround: Download qmail-dkverify.c from the latestet sqmail tar file
and use in in-situ in your currrent version. This should be possible.


Regards.
--eh. 
 
Am Dienstag, dem 17.12.2024 um 11:30 +0100 schrieb Michael Brunnbauer:
> 
> hi all,
> 
> first time this happened - I dunno what was special with that
> message. This
> sytem is configured to sign for netestate.de, but not for
> [DOMAINREDACTED] - 
> which was probably used in the From: sender. But the envelope-sender
> decides 
> what gets signed, as I understand it.
> 
> Dec 15 23:42:21 roja qmail: 1734302541.157353 new msg 36772888
> Dec 15 23:42:21 roja qmail: 1734302541.157370 info msg 36772888:
> bytes 1121 from <anonymous@netestate.de> qp 4215 uid 4313
> Dec 15 23:42:21 roja qmail: 1734302541.157375 starting delivery 7905:
> msg 36772888 to remote info@DOMAINREDACTED
> Dec 15 23:42:21 roja qmail: 1734302541.157378 status: local 0/10
> remote 1/10
> Dec 15 23:42:21 roja kernel: qmail-dkim[4217]: segfault at 0 ip
> 00007f53e7c9ae52 sp 00007ffd70920be8 error 4 in
> libc.so.6[7f53e7b64000+14c000]
> Dec 15 23:42:21 roja kernel: Code: ff 31 c0 c3 44 31 c0 44 29 c0 c3
> 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 89 f0 25 ff 0f 00 00 3d e0 0f
> 00 00 0f 87 7e 02 00 00 <62> e1 fe 28 6f 06 48 89 f8 62 b2 7e 20 26
> c0 c5 fb 93 c8 85 c9 74
> Dec 15 23:42:21 roja qmail: 1734302541.229515 delivery 7905: success:
> 81.209.177.97_TLS_transmitted_message_accepted./Remote_host_said:_250
> _ok_1734302541_qp_2001/
> Dec 15 23:42:21 roja qmail: 1734302541.229589 status: local 0/10
> remote 0/10
> Dec 15 23:42:21 roja qmail: 1734302541.229608 end msg 36772888
> 
> So what happens when qmail-dkim segfaults? And how can I help to fix
> this bug?
> 
> Regards,
> 
> Michael Brunnbauer
> 

-- 
Dr. Erwin Hoffmann | www.fehcom.de
PGP key-id: 20FD6E671A94DC1E
PGP key-fingerprint:  8C6B 155B 0FDA 64F1 BCCE A6B9 20FD 6E67 1A94 DC1E


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de

[toc] | [prev] | [next] | [standalone]

#3304

[Multipart message — attachments visible in raw view] — view raw

Hello Erwin,

On Tue, Dec 17, 2024 at 12:25:19PM +0100, Erwin Hoffmann wrote:
> First: Which s/qmail version you are using? 

sqmail-4.2.29a.

> Second: Can you supply the HEADER of the message which is causing the
> segfault?

Unfortunately not.

> Background: Oddly structured DKIM header may result in this behavior
> (parsing bug);

Ohhhhh! I have confused qmail-dksign with qmail-dkim. Verification is something
I have not configured on this system and I do not want it.

So how did qmail-dkim get called? I have not set QMAILQUEUE=bin/qmail-dkverify
anywhere. That mail that caused the segfault was injected with 
/var/qmail/bin/sendmail.

Regards,

Michael Brunnbauer

-- 
++  Michael Brunnbauer
++  netEstate GmbH
++  Geisenhausener Straße 11a
++  81379 München
++  Tel +49 89 32 19 77 80
++  Fax +49 89 32 19 77 89 
++  E-Mail brunni@netestate.de
++  https://www.netestate.de/
++
++  Sitz: München, HRB Nr.142452 (Handelsregister B München)
++  USt-IdNr. DE221033342
++  Geschäftsführer: Michael Brunnbauer
++  Prokurist: Dipl. Kfm. (Univ.) Markus Hendel

[toc] | [prev] | [standalone]

Back to top | Article view | muc.lists.qmail

csiph-web