[gnutls-devel] GnuTLS | Fix gnutls_pkcs11_token_get_info for short output buffers and fix a memleak (!827)
Development of GNU's TLS library
gnutls-devel at lists.gnutls.org
Thu Dec 13 15:14:12 CET 2018
Nikos Mavrogiannopoulos commented on a discussion on lib/pkcs11.c:
> goto cleanup;
> }
>
> - snprintf(output, *output_size, "%s", tn.modname);
> - *output_size = strlen(output);
> - ret = 0;
> - goto cleanup;
> + modname = tn.modname;
> + if (modname == NULL) {
> + gnutls_assert();
Yes, with glibc applications printed `(null)` but did not get an error. What I worry with the error code is that if the application would now receive an error it may exercise a code path that leads to a fatal error for the user.
--
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/merge_requests/827#note_124719704
You're receiving this email because of your account on gitlab.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20181213/f67d8da6/attachment-0001.html>
More information about the Gnutls-devel
mailing list