Debian Patches
Status for corosync/3.1.9-2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| Fix-various-typos-in-ChangeLog.patch | Fix various typos in ChangeLog This file isn't present in the upstream VCS, but generated from the Git commit messages during the release process. Thus fixing typos in it isn't upstreamable. |
=?utf-8?q?Ferenc_W=C3=A1gner?= <wferi@niif.hu> | no | 2016-08-29 | ||
| Enable-PrivateTmp-in-the-systemd-service-files.patch | Enable PrivateTmp in the systemd service files | =?utf-8?q?Ferenc_W=C3=A1gner?= <wferi@debian.org> | no | 2018-12-10 | ||
| Make-the-example-config-valid.patch | Make the example config valid | =?utf-8?q?Ferenc_W=C3=A1gner?= <wferi@debian.org> | no | 2018-12-16 | ||
| Revert-logrotate-Use-copytruncate-method-by-default.patch | Revert "logrotate: Use copytruncate method by default" This reverts commit 04362046c4a9d7307feb5b68341d567b7d0b94d6. The copytruncate documentation says that it should not be used to avoid losing logging data. The drawbacks mentioned in the reverted commit are not relevant, because they involve hiding problems which should be fixed at their respective origins instead. |
=?utf-8?q?Ferenc_W=C3=A1gner?= <ferenc.wagner@balabit.com> | no | 2023-01-15 | ||
| totemsrp-Check-size-of-orf_token-msg.patch | totemsrp: Check size of orf_token msg orf_token message is stored into preallocated array on endian convert so carefully crafted malicious message can lead to crash of corosync. Solution is to check message size beforehand. |
Jan Friesse <jfriesse@redhat.com> | no | 2025-03-24 |
All known versions for source package 'corosync'
- 3.1.9-2 (trixie, forky, sid)
- 3.1.7-1+deb12u1 (bookworm)