On St, 2014-12-10 at 18:35 +0100, Andy Polyakov via RT wrote:
Excellent. My summary is:
- valgrind complaints about 1.0.1 OpenSLL are extremely unlikely to affect
my program in operation (you will probably say will not affect)
Well, as there is suggestion of what I would say, I would
...@yahoo.com.au
Cc: openssl-dev@openssl.org
Sent: Tuesday, 9 December 2014, 21:02
Subject: Re: [openssl-dev] [openssl.org #3622] bug: crypto, valgrind reports
improper memory access with AES128 cbc and longer plaintext
The demo program actually allocates a whole extra block for the output
Excellent. My summary is:
- valgrind complaints about 1.0.1 OpenSLL are extremely unlikely to affect
my program in operation (you will probably say will not affect)
Well, as there is suggestion of what I would say, I would only say that
it's false positive.
- when OpenSLL 1.0.2 eventually
The demo program actually allocates a whole extra block for the output, so
there should always be extra space available.
Yes, which is why I said as for alleged buffer overruns in *your*
program. I mean you said I discovered this [suspected buffer overrun]
in my real code and as you didn't
Thanks for the response, Andy, it's good to know that the demo program does
actually work for someone. Sorry for the delay, I'm kinda busy with other
things right now. Also, I realised the link was truncated, but it looks as
though you found the demo anyway.
