Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#65050 - [mailman] add systemd hardening options
Attached to Project:
Community Packages
Opened by Jelle van der Waa (jelly) - Saturday, 04 January 2020, 21:07 GMT
Last edited by Sébastien Luttringer (seblu) - Monday, 09 November 2020, 09:24 GMT
Opened by Jelle van der Waa (jelly) - Saturday, 04 January 2020, 21:07 GMT
Last edited by Sébastien Luttringer (seblu) - Monday, 09 November 2020, 09:24 GMT
|
DetailsDescription:
Since python2 is going away and we still require mailman for our infrastructure I think it would be nice to apply at least some hardenings. Note: this patch has not been tested extensively. |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Monday, 09 November 2020, 09:24 GMT
Reason for closing: Implemented
Monday, 09 November 2020, 09:24 GMT
Reason for closing: Implemented
hardening.patch
@loqs: Given that migration must be done ingesting old data into the new mailan following a step by step guide[1] and there is no packet name conflict, I would rather suggest to leave the package mailman die without replace or renaming.
I remember David Runge was interested in working on Mailman3 suite.
[1] https://docs.mailman3.org/en/latest/migration.html