[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <loom.20101205T214528-591@post.gmane.org>
Date: Sun, 5 Dec 2010 20:52:46 +0000 (UTC)
From: Bhadrinath <bitstrat@...il.com>
To: oss-security@...ts.openwall.com
Subject: Re: Interesting behavior with struct initiailization
There was a specific concern in the previous posts.
"Even if the memset is not removed, a compiler could implement 'x.b = 2' by
-setting the low byte of a 32-bit register to 2, leaving the high bytes unchanged
-storing all 32 bits of the register into memory which would store
nonzero data in the high bytes, possibly containing sensitive information. "
In this case,even after doing a memset the compiler could copy some sensitive
information from the 32 bit register into the padding bytes.
So, I feel it is necessary to implement it by copying it to a new equivalent
struct.
Regards
Bhadrinath
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
