public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bryanmcsp at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/10149] stack guard should lead with zero byte to gain protections from str* writes Date: Wed, 10 Nov 2021 14:12:36 +0000 [thread overview] Message-ID: <bug-10149-131-fJoHx0PJB3@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-10149-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=10149 Takkelink <bryanmcsp at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bryanmcsp at gmail dot com --- Comment #10 from Takkelink <bryanmcsp at gmail dot com> --- When building the stack guard, it has been traditionally important to have the value start (in memory) with a zero byte to protect the guard value (and the rest of the stack past it) from being read via strcpy, etc. This patch reduces the number of random bytes by one, leaving the leading zero byte. https://www.kildarehousebuilders.ie -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-11-10 14:12 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-10149-131@http.sourceware.org/bugzilla/> 2011-05-15 15:01 ` drepper.fsp at gmail dot com 2014-07-01 20:34 ` fweimer at redhat dot com 2021-09-05 7:39 ` kimolsun2020 at yahoo dot com 2021-09-10 19:36 ` mehmetgelisin at aol dot com 2021-09-10 19:51 ` mark at klomp dot org 2021-10-09 11:00 ` gulsenenginar at aol dot com 2021-10-19 7:15 ` progonsaytu at gmail dot com 2021-10-21 6:45 ` bap.fayol at gmail dot com 2021-10-21 10:43 ` adhemerval.zanella at linaro dot org 2021-10-24 10:03 ` glassmtech at ukr dot net 2021-11-10 14:12 ` bryanmcsp at gmail dot com [this message] 2009-05-12 18:05 [Bug libc/10149] New: stack guard should lead with zero byte to gain protections from str* reads kees at outflux dot net 2009-05-14 21:50 ` [Bug libc/10149] stack guard should lead with zero byte to gain protections from str* writes kees at outflux dot net
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-10149-131-fJoHx0PJB3@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).