Bug#1010619: rsyslog: CVE-2022-24903: Potential heap buffer overflow in TCP syslog server (receiver) components

note: 8.2204.1 is 8..2204.0 with just the fix cherry-picked. No other changes. Rainer El sáb, 7 may 2022 a las 14:48, Salvatore Bonaccorso () escribió: > > Hi Michael, > > [looping in the sec-team for completeness] > > On Thu, May 05, 2022 at 10:19:38PM +0200, Michael Biebl wrote: > > Am

Bug#935300: rsyslog: FTBFS on s390x

I had a look but to me it seems we actually run out file handles. No failure indication. Is this run in parallel? If so, how many tasks? Sent from phone, thus brief. Michael Biebl schrieb am Mi., 21. Aug. 2019, 19:10: > Am 21.08.19 um 17:43 schrieb Sven Joachim: > > On 2019-08-21 15:43 +0200,

Bug#844914: rsyslog: FTBFS: Tests failures

2016-11-20 17:45 GMT+01:00 Michael Biebl <bi...@debian.org>: > Am 20.11.2016 um 16:17 schrieb Rainer Gerhards: >> Lucas found the right root cause: It looks like the preload lib is not >> loaded on that platform. See >> https://github.com/rsyslog/rsyslog/issues/126

Bug#844914: rsyslog: FTBFS: Tests failures

Lucas found the right root cause: It looks like the preload lib is not loaded on that platform. See https://github.com/rsyslog/rsyslog/issues/1268 I can modify the test so that it is skipped if the preload fails, but I wonder why this happens in the first place (and if there is a better solution

Bug#800873: rsyslog: FTBFS due to failing tests

2015-10-05 0:38 GMT+02:00 Michael Biebl : > Am 04.10.2015 um 14:43 schrieb Hilko Bengen: >> Source: rsyslog >> Version: 8.12.0-3 >> Severity: grave >> >> Building rsyslog on a freshly created sid chroot on barriere.debian.org >> fails with two tests failing: >> >> FAIL:

Bug#703429: FTBFS on !Linux: debug.c:309:22: error: 'SYS_gettid' undeclared

On Tue, 2013-03-19 at 15:28 +0100, Michael Biebl wrote: Source: rsyslog Version: 7.3.8-1 Severity: serious Current version of rsyslog from experimental FTBFS on kfreebsd [1] debug.c: In function 'dbgOutputTID': debug.c:309:22: error: 'SYS_gettid' undeclared (first use in this function)

Bug#703429: FTBFS on !Linux: debug.c:309:22: error: 'SYS_gettid' undeclared

Michael, On Tue, 2013-03-19 at 14:35 +, Rainer Gerhards wrote: I think it is rsyslog's fault here. I probably do no correctly check for the availablity of gettid. Will look into that soon (it's minor debug-aid functionality which can be disabled without any issues, even during debugging

Bug#543505: rsyslog: Wrong priority format for remote action

On Tue, 2009-09-01 at 23:48 +0200, Michael Biebl wrote: Andreas Barth wrote: Rainer asked me, to block rsyslog 4.4.0 as it apparently also had other issues (iirc there was also a segfault during udp reception, but Rainer knows the details), so it was not this specific bug report which alone

Bug#543505: rsyslog: Wrong priority format for remote action

Quick answer: I feel much better about 4.4.x right now. I will probably release 4.4.1 today. FYI: 4.4.1 has been released: http://www.rsyslog.com/Article399.phtml Rainer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#509292: rsyslog: random crashes with remote logging

/?p=rsyslog.git;a=commit;h=35673b12c42429786f6229f f9fcef7001a6b21ab No other branch has been patched so far. Rainer -Original Message- From: Michael Biebl [mailto:bi...@debian.org] Sent: Tuesday, January 27, 2009 3:03 PM To: Rainer Gerhards Cc: Juha Koho; 509...@bugs.debian.org

Bug#509292: rsyslog: random crashes with remote logging

Sorry, there was a copypaste error in the commit. It is corrected now. Please pull the latest version from that git branch. -Original Message- From: Rainer Gerhards [mailto:rgerha...@hq.adiscon.com] Sent: Wednesday, January 28, 2009 1:00 PM To: Michael Biebl Cc: Juha Koho; 509

Bug#509292: rsyslog: random crashes with remote logging

...@gmail.com] Sent: Sunday, January 25, 2009 10:32 AM To: Michael Biebl Cc: 509...@bugs.debian.org; Rainer Gerhards Subject: Re: Bug#509292: rsyslog: random crashes with remote logging On Sat, Jan 24, 2009 at 3:06 PM, Michael Biebl bi...@debian.org wrote: Rainer suspected atomic operations

Bug#509292: rsyslog: random crashes with remote logging

-Original Message- From: Juha Koho [mailto:jmcs...@gmail.com] Sent: Sunday, January 25, 2009 10:32 AM To: Michael Biebl Cc: 509...@bugs.debian.org; Rainer Gerhards Subject: Re: Bug#509292: rsyslog: random crashes with remote logging On Sat, Jan 24, 2009 at 3:06 PM, Michael Biebl bi

Bug#511562: rsyslog: segfault on reload when using $AllowedSender

On Thu, 2009-01-15 at 10:03 +0200, Juha Koho wrote: On Tue, Jan 13, 2009 at 2:02 AM, Michael Biebl bi...@debian.org wrote: Rainer Gerhards wrote: In my lab, I could reproduce the issue (well, without an abort, unfortunately, but valgrind showed problems). The valgrind run was clean after

Bug#509292: rsyslog: random crashes with remote logging

On Wed, 2009-01-14 at 08:40 +0100, Michael Biebl wrote: I don't think the $AllowedSender directive has any influence on the crashes Juho experiences on his rsyslog clients (as he only used those directive on the rsyslog server). Why do you suspect that the $AllowedSender fix might have an

Bug#511562: rsyslog: segfault on reload when using $AllowedSender

Hi Michael, Rainer, I'd like (you) to take a look a #509292 first, before making a new release. I am looking at it, but this looks like the dangling issue we have on 4+ core systems from time to time. I am not sure if there will be a quick fix for that. One problem is that I can not reproduce

Bug#509292: rsyslog: random crashes with remote logging

Juha, I have finally been able to review the material that came with this bug report. Thanks for all the good info, but it looks everything was related to the $AllowedSender bug, not to the race condition (which I, too, think exists). ... more inline below... On Sat, 2009-01-10 at 20:12 +0200,

Bug#511562: rsyslog: segfault on reload when using $AllowedSender

Hi all, thanks for the bug report and your help in narrowing it down. I was on vacation and returned today. I have created a patch for this issue (as usual, a dumb mistake...). I'd appreciate if you could give it a try. Available from rsyslog git (debian_lenny branch):