Your message dated Sat, 25 Feb 2023 15:28:56 +0100 with message-id <Y/[email protected]> and subject line opendkim crash has caused the Debian Bug report #1013277, regarding opendkim crash 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.) -- 1013277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013277 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: opendkim Version: 2.11.0~beta2-4 Debian stable (11.3) i386 with 5.10.0-15-cloud-amd64 kernel. Hello. We have some crashes of opendkim. In unstable changelog i found: opendkim (2.11.0~beta2-5) unstable; urgency=medium * Add new patches: - cve-2020-12272.patch: Mitigation for CVE-2020-12272. ... - mlfi_close.patch: Fix segfault due to use-after-free in mlfi_close. Is there a plan to patch / rebuild for stable? Thanks. Regards, J.K.
--- End Message ---
--- Begin Message ---There is not enough actionable information here, so I’m closing the bug. To be useful, the bug report needs at least steps to reproduce, or some indication of the input that triggers the bug. Ideally, it should include a stack trace with debug information (= including file names and line numbers). If the issue persists on the current unstable/testing version feel free to open a new bug with complete information.
--- End Message ---
