ChangeLog | 16 8 + 8 - 0 !
1 file changed, 8 insertions(+), 8 deletions(-)

 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.

init/corosync-notifyd.service.in | 1 1 + 0 - 0 !
init/corosync.service.in | 1 1 + 0 - 0 !
2 files changed, 2 insertions(+)

 enable privatetmp in the systemd service files

conf/corosync.conf.example | 22 7 + 15 - 0 !
1 file changed, 7 insertions(+), 15 deletions(-)

 make the example config valid

conf/logrotate/Makefile.am | 7 7 + 0 - 0 !
conf/logrotate/corosync-reopen.in | 5 0 + 5 - 0 !
2 files changed, 7 insertions(+), 5 deletions(-)

 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.

exec/totemsrp.c | 18 17 + 1 - 0 !
1 file changed, 17 insertions(+), 1 deletion(-)

 [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.

Signed-off-by: Jan Friesse <jfriesse@redhat.com>