r be fixed? Also, who is doing the correct thing
here, JSSE or OpenSSL?
Sincerely,
Kevin Regan
Kevin Regan
Technical Lead
Houston UNIX Team
Office: 2200
Phone: 713-548-1767
__
OpenSSL Project
EAD: SSL v3.1 Application Data, length = 21
Plaintext after DECRYPTION: len = 21
: 6C FF C7 5B 71 3F 71 BF 02 1A 64 DF F4 6D AC A3 l..[q?q...d..m..
0010: 93 43 00 73 1C .C.s.
main, READ: SSL v3.1 Application Data, length = 21
Plaintext after DECRYPTI
ions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
As a workaround, I changed the above line to:
GCCVER=3.1
--Kevin
Kevin Regan
NetIQ Corporation (www.netiq.com)
Technical Lead
Houston UNIX Team
Office: 2200
P
to have someone on the openssl team look at
each RAND_add() call and determine if any additional memsets are needed with
the "PURIFY" flag (with an eye towards structures that may not be fully
initialized).
Sincerely,
Kevin Regan
F5 Networks
>> You're missing the point -- your comment is the height of irony, in a
>> way.
>>
>> Use a suppression to make Valgrind shut up.
>>
>> /r$
>
> I think you misunderstand his issue. His issue is not "valgrind reports a
> spurious error/warning". His issue is "-DPURIFY does not do what I thi
.
--Kevin
From: Kevin Regan
Sent: Friday, January 08, 2010 10:53 AM
To: 'openssl-dev@openssl.org'
Subject: RE: Change needed for "-DPURIFY" builds.
>> You're missing the point -- your comment is the height of irony, in a
>> way.
>>
>> Use a suppression
mp;sb,sizeof(sb),0.0);
if (bytes == 0) return(ret);
From: Kevin Regan
Sent: Friday, January 08, 2010 11:01 AM
To: Kevin Regan; 'openssl-dev@openssl.org'
Subject: RE: RE: Change needed for "-DPURIFY" builds.
I also wanted to mention that the -DPURIFY flag should not weake
Sent: Monday, January 11, 2010 4:35 PM
To: openssl-dev@openssl.org
Subject: Re: [PATCH] Change needed for "-DPURIFY" builds.
On Mon, Jan 11, 2010, Kevin Regan wrote:
> Any further thoughts on this patch? I'd love to get these -DPURIFY builds
> working properly.
>
Plea
"-DPURIFY"
builds.
On Tue, Jan 26, 2010, Kevin Regan via RT wrote:
> Is there somewhere that I can check to verify this? I want to make sure that
> this patch is in the latest build.
>
You can either wait until tomorrow snapshots or pull the latest CVS using the
in
This patch fixes a bug with the -DPURIFY flag. The stat structure contains
padding and unused fields that are not initialized with the stat call. This
causes applications such as Valgrind to be unable to analyze OpenSSL
executables that are compiled with the -DPURIFY flag.
This is for OpenSSL
Is there somewhere that I can check to verify this? I want to make sure that
this patch is in the latest build.
Thanks,
Kevin
-Original Message-
From: Stephen Henson via RT [mailto:r...@openssl.org]
Sent: Tuesday, January 26, 2010 10:09 AM
To: Kevin Regan
Subject
11 matches
Mail list logo