| commit | 2e6297ff1b025e2a6c9878febe2574d3dea110da | |
| author | Cyrill Gorcunov <gorcunov@gmail.com> | |
| Sun, 19 Jul 2015 11:12:44 +0000 (19 14:12 +0300) | ||
| committer | Cyrill Gorcunov <gorcunov@gmail.com> | |
| Sun, 19 Jul 2015 11:24:26 +0000 (19 14:24 +0300) | ||
| tree | 7235f0282a8e8651e3588ae787c0bef9ad5063f3 | treesnapshot (tar.gz zip) |
| parent | ce28db6b688480cb46a33c29da857e1959abbd8d | commitdiff |
out: Zeroify temp buffer before use
This is a a buffer on stack big enough to hold
bigger object we might need (address, number and
etc) but it's defined as an array of bytes and
we treat it as different types depending on context,
which may lead to situation where data from stack
been treated as meaningful.
In particular in commit 5b730a197 we've fixed such
problem simply using a "big" write to zeroify stack
data before use.
Lets simply zeroify this buffer explicitly to escape
such problems in future.
Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
This is a a buffer on stack big enough to hold
bigger object we might need (address, number and
etc) but it's defined as an array of bytes and
we treat it as different types depending on context,
which may lead to situation where data from stack
been treated as meaningful.
In particular in commit 5b730a197 we've fixed such
problem simply using a "big" write to zeroify stack
data before use.
Lets simply zeroify this buffer explicitly to escape
such problems in future.
Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>