I have built and tested several vanilla libssh2 versions with the mentioned
example: versions from 1.4.3 to 1.6.0 produces many "uninitialized data"
warnings. Release 1.7.0 does not produce warnings or errors (just this one
example).
It appears that distros have patched most of these issues in their
maintained versions so I could report it for releases that haven't yet
upgraded to 1.7.
- Jarkko
On Wed, Sep 6, 2017 at 11:54 AM Daniel Stenberg <daniel_at_haxx.se> wrote:
> On Wed, 6 Sep 2017, Jarkko Palviainen via libssh2-devel wrote:
>
> > Can you comment whether this is a bug in the example, in libssh2 1.4.3 or
> > false positive report? Please, note that Debian 8 as well as RHEL/Centos
> 7
> > ship a (security) patched 1.4.3 libssh2.
>
> libssh2 1.4.3 was released almost 5 years ago and we've fixed NUMEROUS bugs
> since.
>
> I don't know about this specific error, but I've seen several other
> valgrind
> errors in older versions that are already fixed in the current version, so
> I
> would ask you to at least first test with a modern libssh2 version first
> before spending a lot of time on hunting down problems.
>
> --
>
> / daniel.haxx.se
>
_______________________________________________
libssh2-devel https://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2017-09-06