public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjon at hortensius dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/29536] syslog fail to create large messages (CVE-2022-39046) Date: Tue, 06 Sep 2022 14:52:40 +0000 [thread overview] Message-ID: <bug-29536-131-pyLyQZtbMf@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29536-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29536 sjon at hortensius dot net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sjon at hortensius dot net --- Comment #6 from sjon at hortensius dot net --- it seems glibc 2.36 is completely unable to syslog messages longer than 1024 chars which is very likely related to this issue. This seems like a pretty major bug and possible reason to release a glibc update quicker then in 6 months -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-09-06 14:52 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-29 12:26 [Bug libc/29536] New: syslog fail to create large messages adhemerval.zanella at linaro dot org 2022-08-29 13:16 ` [Bug libc/29536] " carlos at redhat dot com 2022-08-29 16:51 ` siddhesh at sourceware dot org 2022-08-29 19:36 ` siddhesh at sourceware dot org 2022-08-30 12:02 ` adhemerval.zanella at linaro dot org 2022-08-31 11:13 ` [Bug libc/29536] syslog fail to create large messages (CVE-2022-39046) siddhesh at sourceware dot org 2022-08-31 13:19 ` adhemerval.zanella at linaro dot org 2022-09-06 13:27 ` fweimer at redhat dot com 2022-09-06 14:52 ` sjon at hortensius dot net [this message] 2022-09-06 14:58 ` siddhesh at sourceware dot org 2022-09-08 17:59 ` brunni at netestate dot de 2022-09-08 18:51 ` siddhesh at sourceware dot org 2022-09-08 18:53 ` brunni at netestate dot de 2022-09-08 18:59 ` siddhesh at sourceware dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-29536-131-pyLyQZtbMf@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).