Subject: Re: [libssh2] Memory leak in payload

Re: [libssh2] Memory leak in payload

From: Daniel Stenberg <>
Date: Thu, 15 Mar 2007 21:52:02 +0100 (CET)

On Wed, 14 Mar 2007, Dan Fandrich wrote:

> After a bit more poking around, I discovered that at the end of fullpacket()
> is a call to libssh2_packet_add() which passes in p->payload. The packet in
> most cases gets added to a list which is freed later, or freed within that
> function. However, there are a couple of error paths where it isn't freed.
> This patch fixes those:

Thanks, applied!

> There's one more leak that valgrind complains about, but it's within
> libcrypto so it's not clear that it's a libssh2 problem:

Unfortunately OpenSSL is full of valgrind warnings so you never know when to
take them seriously or not... :-(

Take Surveys. Earn Cash. Influence the Future of IT
Join's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
libssh2-devel mailing list
Received on 2007-03-15