bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: "Pádraig Brady" <P@draigbrady.com>
Cc: James Youngman <james@youngman.org>,
	Bernhard Voelker <mail@bernhard-voelker.de>,
	bug-gnulib@gnu.org
Subject: Re: VLA and alloca
Date: Sun, 20 Jan 2019 16:36:29 +0100	[thread overview]
Message-ID: <4425313.A21oZ5zyQ0@omega> (raw)
In-Reply-To: <2f26e4a4-c899-686c-473c-2c7773fff14b@draigBrady.com>

Pádraig Brady wrote:
> I've not analyzed the security concerns in detail, but in general
> large allocations on the stack are bad for security

Indeed. Just reading this CVE [1] from a week ago, makes me want to
disable all large allocations on the stack.

Bruno

[1] https://www.openwall.com/lists/oss-security/2019/01/09/3



  parent reply	other threads:[~2019-01-20 15:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-09 22:32 Correct but unhelpful VLA warning vs. gnulib's gettext.h; can we eliminate the false positive? James Youngman
2011-07-10  4:47 ` Paul Eggert
2011-07-10  9:16   ` James Youngman
2011-07-11  0:11     ` Paul Eggert
2011-07-11  1:02       ` James Youngman
2011-07-11  1:13         ` Paul Eggert
2011-07-10  9:48 ` Simon Josefsson
2019-01-14  6:10 ` Pádraig Brady
2019-01-15  1:57   ` VLA and alloca Bruno Haible
2019-01-20  4:46     ` Pádraig Brady
2019-01-20 10:19       ` Bruno Haible
2019-01-20 21:03         ` Pádraig Brady
2019-02-02 22:44         ` Paul Eggert
2019-01-20 15:36       ` Bruno Haible [this message]
2019-01-24 11:51         ` Tim Rühsen
2019-02-02 22:58           ` Paul Eggert

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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4425313.A21oZ5zyQ0@omega \
    --to=bruno@clisp.org \
    --cc=P@draigbrady.com \
    --cc=bug-gnulib@gnu.org \
    --cc=james@youngman.org \
    --cc=mail@bernhard-voelker.de \
    /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: link
Be 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).