From mboxrd@z Thu Jan  1 00:00:00 1970
From: dewar@gnat.com
To: dewar@gnat.com, fw@deneb.enyo.de
Cc: carlo@alinoe.com, fp@fpx.de, gcc@gcc.gnu.org
Subject: Re: Buffer Overflow Attacks
Date: Sun, 14 Oct 2001 12:25:00 -0000
Message-id: <20011014192442.56A14F28BA@nile.gnat.com>
X-SW-Source: 2001-10/msg00823.html

<<According to the language standard, buffer overflow detection for
character pointer types is possible only for buffers which are not
nested in other objects (in struct or union objects).  Overflowing
character buffers has a well-defined effect if the buffer is contained
in an object (and other objects follow the buffer inside this object),
so a C implementation is not free to detect such errors (which is only
possible if the buffer overflow triggers undefined behavior). ;-)
>>

Well there is room for argument on the above analysis (since the standard
does not fully specify how composite types are layed out), but in any case,
it is always just fine to have a switch that requires sensible restrictions
on behavior, regardless of the standard, subsetting is always allowed, and
it is also just fine to compile sensitive code with such a switch and insist
that it conforms to some safe subset.