Created attachment 324940 [details, diff] wireshark-1.8.2-gnutls3.patch net-analyzer/wireshark blocks net-libs/gnutls-3. I know it's because upstream explicitly denies support for gnutls-3, but there is no technical reason to do so. Their reasoning is that they don't want to use gnutls-3 because to be able to legally redistribute wireshark binaries along with gnutls-3 binaries, it must be distributed as gpl-3(+)[1] (think win32/osx binaries). But everyone can compile wireshark with gnutls-3, only the resulting binaries will be gpl-3(+) instead of gpl-2(+). Can wireshark be really compiled with gnutls-3? Yes, gnutls-3 is mostly source compatible with gnutls-2.12[2]. Incompatibilities come down to some functions that were removed, but wireshark uses none of these. I checked and it compiles fine. Isn't wireshark source code gpl-2-only? No, the source code is gpl-2+, as can deduced from [1]. I checked it to be sure, and there are no gpl-2-only files (there are though some files dual-licenced under either gpl-2-only or 3-clause bsd but we can choose bsd here). What is upstream status of this? Nothing has changed so far. They don't want to use gnutls-3 because they don't want to switch to gpl-3. They would probably accept quality patches to replace gnutls dependency with nss, but there's no progress on it so far. Maybe it would be a good idea to have a patch upstreamed that could at least add some configure-time switch to allow gnutls-3? [1] https://wireshark.org/lists/wireshark-dev/201203/msg00171.html [2] http://www.gnu.org/software/gnutls/manual/html_node/Upgrading-from-previous-versions.html#Upgrading-from-previous-versions
Should be fixed in 1.8.3-r1. Please test and confirm.
I tested whether it works, and unfortunately it doesn't. But it seems to be caused not by gnutls-3 itself, but by gnutls not using libgcrypt, as it doesn't work with gnutls-2[nettle] as well[1]. So IMHO the patch is still valid, as I expect the SSL dissector to work with gnutls-3 when it is made compatible with gnutls-2[nettle]. [1] See bug #412219.
As I expected, it works correctly with my patch from bug #412219.
