Peter Stuge wrote: > Daniel Stenberg wrote: > > It returns an allocated string, but there's no way for an > > application to free that memory (without making assumptions on how > > the memory is allocated)... > > > > I mentioned this in the man page now since I have no plan of > > actually correcting this mistake in the near-term. > > We should really fix that before 1.0. I can have a look.
Why is there even a base64_decode() in libssh2? OpenSSL does b64. Do we have our own because libgcrypt doesn't have it? Hm. It's in GNU crypto stuff for Java, maybe libgcrypt should add it? Also it isn't heavily used in libssh2 so we could even change it to let the caller alloc, or to always use malloc, or.. I think letting the caller alloc would be the simplest change, it does change how the function works though. Patch welcome? //Peter ------------------------------------------------------------------------------ _______________________________________________ libssh2-devel mailing list libssh2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libssh2-devel
