SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I need to debug encrypted WebDAV communication over HTTPS because windows 7/8 built-in webdav client for unknown reasons doesn't work with our webdav share.
Wireshark can decrypt SSL/TLS, but relies on gnutls library for that. Unfortunately it doesn't support gnutls 3.x (shipped in Slackware) yet and only way to get things working is to compile gnutls 2.x and rebuild wireshark again.
So far it works like a charm, but is it safe to have two different versions of same library installed in system? Lets say I would compile something that use gnutls. Which library/version will configure script choose if there are two libraries of the same name (in /usr/lib and /usr/local/lib)?
I believe Wireshark only has issues with GnuTLS 3.0.0 through 3.1.9. The good news is GnuTLS 3.1.x is source & binary
compatible with GnuTLS 3.0.x. In fact, Pat recently bumped current to 3.1.x without issues.
So, I recommend you use Slackware-current's slackbuild to build GnuTLS 3.1.15 on your system (which I assume is 14.0).
You should not have to bother with multiple versions if you do that.
I believe Wireshark only has issues with GnuTLS 3.0.0 through 3.1.9. The good news is GnuTLS 3.1.x is source & binary
compatible with GnuTLS 3.0.x. In fact, Pat recently bumped current to 3.1.x without issues.
So, I recommend you use Slackware-current's slackbuild to build GnuTLS 3.1.15 on your system (which I assume is 14.0).
You should not have to bother with multiple versions if you do that.
I'm running current and I guess I must have built wireshark before GnuTLS version bump or missed something, because wireshark then didn't recognized GnuTLS as available. I'm rebuilding it right now and it already successfully picked up GnuTLS 3.1.x
Thanks!
Last edited by yenn; 10-27-2013 at 07:21 PM.
Reason: typo
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.