diff options
author | Michael Biebl <biebl@debian.org> | 2013-07-23 01:01:14 +0200 |
---|---|---|
committer | Michael Biebl <biebl@debian.org> | 2013-07-23 01:01:14 +0200 |
commit | a400789c367fd3cd8d0f9588ca2af72dcac47c9c (patch) | |
tree | 8c1caa6308f9e720e1e461da321107e6dc29f256 /ChangeLog | |
parent | f5638ea86a8626b7e0e471d720359cb4e3d8cb1c (diff) | |
download | rsyslog-a400789c367fd3cd8d0f9588ca2af72dcac47c9c.tar.gz |
Imported Upstream version 7.4.3upstream/7.4.3
Diffstat (limited to 'ChangeLog')
-rw-r--r-- | ChangeLog | 17 |
1 files changed, 17 insertions, 0 deletions
@@ -1,4 +1,20 @@ --------------------------------------------------------------------------- +Version 7.4.3 [v7.4-stable] 2013-07-18 +- bugfix: memory leak if disk queues were used and json data present +- bugfix: CEE/json data was lost during disk queue operation +- bugfix: potential segfault during startup on invalid config + could happen if invalid actions were present, which could lead + to improper handling in optimizer. +- bugfix: 100% CPU utilization when DA queue became full +- bugfix: omlibdbi did not properly close connection on some errors + This happened to errors occuring in Begin/End Transaction entry + points. +- cosmetic bugfix: file name buffer was not freed on disk queue destruction + This was an extremely small one-time per run memleak, so nothing of + concern. However, it bugs under valgrind and similar memory debuggers. +- fix build on FreeBSD + Thanks to Christiano Rolim for the patch +--------------------------------------------------------------------------- Version 7.4.2 [v7.4-stable] 2013-07-04 - bugfix: in RFC5425 TLS, multiple wildcards in auth could cause segfault - bugfix: RainerScript object required parameters were not properly @@ -8,6 +24,7 @@ Version 7.4.2 [v7.4-stable] 2013-07-04 closes: http://bugzilla.adiscon.com/show_bug.cgi?id=461 a security advisory for this bug is available at: http://www.lsexperts.de/advisories/lse-2013-07-03.txt + CVE: CVE-2013-4758 PLEASE NOTE: This issue only existed if omelasticsearch was used in a non-default configuration, where the "errorfile" parameter was specified. Without that parameter set, the bug could not |