GNUTLS handshake errors and memory leaks (ECDHE related?)

[Yaroslav]

Great! After applying the patch handshake leaks seem to be gone. Logs
attached.

One more note about errors. gnutls handshake errors -24 appear one by one
and seem to correspond to ab errors. Errors -10 and -110 appear in a bunch
right after ab finishes. It might be specific to how ab works. It could
have opened more connections than it should for example. I will further
investigate with log level 2.

On Tue, Jan 10, 2012 at 6:14 PM, Nikos Mavrogiannopoulos <nmav at gnutls.org>wrote:

> On Tue, Jan 10, 2012 at 3:03 PM, Yaroslav <yarosla at gmail.com> wrote:
>
> >> btw. from the logs I see that the version of libtasn1 you have doesn't
> >> compile well with
> >> the gcc you have. You can use the included libtasn1 to avoid the
> >> valgrind warnings.
> > libtasn1 is installed in my Ubuntu and there seems to be quite a lot of
> > software that depends on it. Is there a way to configure gnutls to use
> > included libtasn1 when I already have libtasn1 on my system?
>
> Use --with-included-libtasn1 when configuring gnutls. That way it will
> ignore the installed version.
>
> > Not sure about this. I have Intel Q6700 processor. The spec
> > (
> http://ark.intel.com/products/30790/Intel-Core2-Quad-Processor-Q6700-(8M-Cache-2_66-GHz-1066-MHz-FSB)
> )
> > says: "AES New Instructions: No".
>
> It doesn't seem to have them. You can always check in realtime with
> "cat /proc/cpuinfo". If aes is in your flags.
>
> regards,
> Nikos
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20120110/10d5e123/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: valgrind_log_120110-5.log
Type: text/x-log
Size: 27164 bytes
Desc: not available
URL: </pipermail/attachments/20120110/10d5e123/attachment.bin>